EE633/733 Experiments in Computer Networking. Detailed exploration of particular issues in network protocols and network application models. Development of series of programs to explore the details of network protocols and network application models. Prerequisite: EE432/532 or permission of Instructor.
The purpose of this course is to provide the student an opportunity to explore the client server computing using a particular suite of protocols. Upon completion, the student should be familiar with the principles, standards, trends, and present practices in the chosen computer network protocol suite. The student will also have examined the data as it appears on the network after processing is completed in the computer.
| Component | Weight |
| Quizzes, Programmettes & Class participation | 35% |
| Tests (20% each) | 40% |
| Project Program (Team) | 25% |
| 100% |
| Event | Date |
| Test 1 | Oct 8, class time |
| Test 2 | Nov 19, class time |
| Project presentations
(all students required to attend) |
Dec 3, class time |
Programmettes are due as shown on the syllabus. Programmettes must be demonstrated to the Instructor or TA and documented code listing submitted before they are considered submitted. Code listings should reflect good design and presentation principles. The code listing that is submitted must be of the code that is demonstated. Late submissions will incur a letter grade penalty per class meeting (except for class meetings where demonstrations are not allowed - such as test dates.)
Programmettes are individual work items. You must write and debug your own code.
Projects are to be done in groups of 2-4 students and should have enough ``meat to them'' to warrant a group. Possible projects include implementing various clients or servers to more completely demonstrate concepts, security token server, explore which machines are on-line at anytime within the LAN, explore Multicast application, explore cryptographic classes, SOAP or CORBA demo, etc. Emphasis should be on writing code to demonstrate a concept or system rather than a) complete a finished product or b) bringing up an already written program. Your group will need to implement a demonstration in Java.
Students may propose their group memberships in order to align schedule and interests. Those students who can not identify a group to work with will be placed in groups on the sixth class. Class sessions throughout the semester are set aside for the groups to meet to plan, and execute their projects. It is expected that there will be need to be significant out of class work on these projects as well.
Be aware that resource issues can be a problem. Anticipate them and try to resolve them before committing to a particular project. Demos will be need to be made from the BEC classroom or lab so use of remote resources and accessibility problems related to them (such as the CIS firewall) must be addressed and solved as part of the project.
Disclosure required. All ``connections'' to prior work must be disclosed preferrably before use. Projects that have been done for other classes are NOT legitimate projects. It is academic misconduct not to disclose prior work. It is possible, to use the project as a concept exploration for later project/thesis use; to build upon other work, etc. provided this is disclosed and approved by the instructor prior to submission.
The project presentations will be made on the last classes. All group members are expected to be present and each speak during the presentation, and all students are expected to attend ALL presentations (neither leaving early nor working on their project during another groups presentation.)
During the semester, your team will be asked to supply project updates and may be asked to make a short presentation related to your project. You should strongly consider placing your project material on a web site to make it available to team members and eventually to the class. Your grade on the project will be based on the level of difficulty of the project as well as how well it was excuted (judged a team level) as well as your efforts and contributions to the project based on both instructor observed metrics and evaluations by your team members.