Exploration of data communications and computer networks. Topics include network architecture, TCP/IP protocols, wireless and mobile networks, and network security. Includes hands-on lab activities and an introduction to network programming. Prerequisites: CSC 220.
My office is in Carnegie Hall 310 B. You can stop by in person, or call my office at 630-637-5174. If I am not at the office and you need immediate attention, you can call me at home at 630-759-2110. You can email me at email@example.com. Spring term office hours are Mondays and Wednesdays 4:30-6:30 pm and Thursdays 2:30-3:30. I can also see you by appointment.
James F. Kurose and Keith W. Ross Computer Networking: A Top-Down Approach , Sixth edition, Addison Wesley.
Schedule of Meetings
We will meet a minimum of two hours a week, Thursdays 3:30-4:30 pm.
Schedule of Topics
We will cover the following chapters of the class textbook, in the order given.
|Chapter 1:||Computer Networks and the Internet|
|Chapter 2:||The Application Layer|
|Chapter 3:||The Transport Layer|
|Chapter 4:||The Network Layer|
|Chapter 5:||The Link Layer and Local Area Networks|
|Chapter 6:||Wireless and Mobile Networks|
Schedule of Tests
There will be a quiz in Week 3 (5%), a midterm in Week 5 (12.5%), a test in Week 8 (12.5 %), and a final exam (20 %). Assigned homework and projects will will account for the remaining 50%. All homework assignments/projects will be equally weighted.
All assignments and projects must be submitted via email using your College email account.
and must have a subject that begins with
All assignments and projects should be turned in by midnight on the day due. A 10% penalty will be assessed on projects turned in late, but in general this penalty will not be levied if the assignment is turned in before I have completed grading the batch of assignments to which it belongs. No assignment/project turned in after the due date for the next assignment/project will be graded. I will make an exception to this rule for students who have been coming to see me for help, where I judge that the student is reasonably close to getting the assignment or project done.
Ethics Policy / Academic Dishonesty.
Students may discuss the assignments and projects with other students, as long as such discussions result in a transfer of understanding rather than a transfer of code. Except on the designated team project, students should not write their code together. I reserve the right to require a conference with any group of students whenever I notice suspicious similarities in their code. Code is suspiciously similar when it is the same except for renaming of identifiers and/or trivial rearrangements of code. Under these circumstances, I will ask students to explain the meaning of the code, and to write code to solve a different but similar problem in my presence. Unethical collaboration will be established if such a student fails to explain the submitted code, or to solve the similar problem. If unethical collaboration is established, the students involved will receive a mark of zero for the assignment or project, and will be reported to the dean.