CS 5651 - Computer Networks - Fall 2006

Course Syllabus

Location: HH 306 (Lecture), HH 338 (Lab)
Time: 3:30pm - 4:45pm TTh (Lecture), 6:00pm - 6:50pm Th (Lab)
Instructor: Pete Willemsen, TA: Ankur Nepalia
Office Hours: 12:30pm - 2:00pm TTh, 1:00pm - 2:30pm W
TA Office Hours:

Class WebDrop

Recent Updates and Information...

Important notices, dates, and other information will be posted here.

Java Info - Professor Shute maintains an excellent page of Java references. See his page if you need additional information on programming with Java.

FINAL EXAM IS SATURDAY, DECEMBER 16, 2006 at 2:00PM!

Course Description

This course introduces computer networking and associated software communication protocols. Includes network reference models, layered architectures, network services, and network applications. Design of computer networking software and quality of service concepts are also covered. The goals of this course are: (1) to provide students with a solid understanding of computer network hardware and software;
and (2) to provide students with a practical and theoretical knowledge of network architecture and network performance analysis.

You may also want to look over the Computer Networks (CS 5651) Course Description and Computer Networks (CS 5651) Course Outcomes documents on the CS webserver.

Reading (Required)

Computer Networking: A Top-Down Approach Featuring the Internet, 3rd ed. , by James F. Kurose and Keith W. Ross

We will definitely cover Chapters 1, 2, 3, 4, and 5. After that, we will likely go through Chapters 6 (Wireless Networks), 7 (Multimedia Networking), and/or 8 (Network Security).

Class Requirements and Grading

There will be both weekly homeworks as well as programming assignments in the course. There is also a weekly lab and three exams (2 mid-terms and final exam).

1. Homework Assignments (10%) - Weekly homework problems will be assigned. These assignments must be turned in before class on the assigned due date.

2. Lab (10%) - Labs will provides hands-on experience with computer network analysis, tool usage, and programming. Labs may also be used to validate your programming assignments or discuss problems with the TA.

3. Programming Assignments (20%) - There will be at most 5 (4 is more likely) programming assignments over the course of the semester.

4. Exams (20% each) - There will be three exams over the course of the semester, each worth 20% of your grade. The final exam is one of these exams. The date of the final exam is December 21, 2006 from 4:00pm-5:55pm.

The following provides a guide for how the grades will be distributed once a final percentage is computed:

• 90% results in an A-
• 80% results in a B-
• 70% results in a C-
• 60% results in a D

Policies (by taking the class, it is understood that you have read this section!)

Missed Classes
Students are responsible for what goes on in class, including lecture material, handouts, and turning in assignments. If you are unable to attend class it is your responsibility to obtain copies of class notes and any materials distributed in class. You may turn in copies of assignments early.

Missed Exams
No exam will be given early. Exams can be made up only in the case of emergencies such as severe illness or death in the immediate family. You must contact the instructor 24 hours in advance in order to arrange a makeup.

Assignments
All assignments will be due by email/web drop before the beginning of class on the due date. Late assignments will be penalized 20% of the grade for each working day the assignment is late. To turn in an assignment, send an email with attachments to the instructor, or submit via a web drop (ASCII text, PDF, or Word documents will be accepted).

No Incompletes
I do not give incompletes! All work must be done during this semester.

Cheating
Don't do it! It doesn't provide any benefit to you. Programming and homework assignments must be your own work. You may discuss general, high-level, or conceptual issues with other students, but should not discuss actual code with others. Cheating is considered to be sharing code either by copying, retyping, looking at, or supplying a copy of a file. Cheating is also considered to include the use of code supplied off the Internet. If you use Google or other search engines to look for code to help you with a programming assignment, don't do it! I do expect you to be honest and I will respect you as a colleague until I am proven to be wrong. If you are having problems with an assignment, please come talk to me or send me email.

Equal Opportunity
As instructor I shall make every attempt to treat all students equally, without regard to race, religion, color, sex, handicap, age, veteran status, or sexual orientation. I encourage you to talk to me about your concerns of equal opportunity in the classroom. To inquire further about the University's policy on equal opportunity, contact the Office of Equal Opportunity (6827), 269-273 DAdB.

Students With Disabilities
If you have any disability (either permanent or temporary) that might affect your ability to perform in this class, please inform me at the start of the semester. I may adapt methods, materials, or testing so that you can participate equitably. To learn about the services that UMD provides to students with disabilities, contact the Access Center (8727), 138 Kirby Plaza, or the Office of Equal Opportunity (8217), 269-273 DAdB.

Course Calendar