This page contains the syllabus for Networking for
Spring 2014. "The course syllabus contains important information regarding course requirements and the grading system
utilized. It is the responsibility of the students to read the syllabus and consult the instructor if they have
questions."(from UNC 2013-2014 Undergraduate Catalog)
CS 442 002 - Networking - 3 credits Spring 2014 Class meeting time and location:Monday and Wednesday, 9:05am - 10:20am in Ross Hall 2230G (Linux Lab) All class material is accessible through Blackboard.
Required textbook: The required textbook is Computer Networking: A Top-Down Approach, 6th Edition, by James F. Kurose, and Keith W. Ross. There will be assigned readings to complement the lectures. These readings will come from handouts and/or material in the textbook.
Catalog course description: Study data communications; network structure, design and architectures; network services and
standardization; and respective networks all in the framework of the OSI model.
As a result of successfully completing this course, students will:
Become familiar with layered communication architectures (OSI and TCP/IP).
Understand the client/server model and key application layer protocols.
Learn sockets programming and how to implement client/server programs.
Understand the concepts of reliable data transfer and how TCP implements these concepts.
Know the principles of congestion control and trade-offs in fairness and efficiency.
Learn the principles of routing and the semantics and syntax of IP.
Understand the basics of error detection including parity, checksums, and CRC.
CS 440 -- Operating Systems
This course will cover the following topics:
Week 1 (Jan 13 – 19, 2014): Protocol layers and service models. OSI and Internet protocols.
Week 2 (Jan 20 – 26, 2014): History of the Internet. Concepts of delay, security, and Quality of Service (QoS).
Week 3 (Jan 27 – Feb 2, 2014): Application layer protocols and client-server model
Week 4 (Feb 3 – 9, 2014): Application layer protocols and client-server model
Week 5 (Feb 10 – 16, 2014): Sockets programming in C (client-server and web server programs).
Week 6 (Feb 17 – 23, 2014): Sockets programming in C (client-server and web server programs).
Week 7 (Feb 24 – Mar 2, 2014): Application layer protocols and client-server model
Week 8 (Mar 3 – 9, 2014): Reliable data transfer. Semantics and syntax of TCP.
Week 9 (Mar 10 – 16, 2014): Reliable data transfer. Semantics and syntax of TCP.
Week 10 (Mar 17 – 23, 2014): Spring Break (No Classes)
Week 11 (Mar 24 – 30, 2014): Principles of congestion control: reactive and proactive, efficiency and fairness. Midterm Exam
Week 12 (Mar 31 – Apr 6, 2014): Principles of routing: link-state and distance vector. Semantics and syntax of IP.
Week 13 (Apr 7 – 13, 2014): Principles of routing: link-state and distance vector. Semantics and syntax of IP.
Week 14 (Apr 14 – 20, 2014): Error detection including checksums and CRC. Multiple access protocols including IEEE 802.3 Ethernet.
Week 15 (Apr 21 – Apr 27, 2014): Switching and bridging. Media, signal strength, and data encoding.
Week 16 (Apr 28 – May 4, 2014): Wrap-up and Review for Final Exam
Week 17 (May 5 – 11, 2014): No classes, comprehensive final exam, project due
Detailed course outline: A detailed course outline that includes readings, assignment and project deadlines, and exam dates is
Grading: Students will earn a grade based on assignments, a project, mid-term exam, and a comprehensive final exam. The grade breakdown is:
Assignments: 25% (five assignments, assigned roughly every third week)
Project: 25% (due on Sunday, May 11, 2014 by 11:59pm - early submission is very highly recommended, late submissions will not be accepted)
Midterm exam: 20% (take-home exam, due on Mar. 30, 2014 at 11:59pm)
Comprehensive final exam: 30% (held in class on Monday, May 5, 2014, 10:45am – 1:15pm)
The grading scale is "no worse than" ("+" or "-" grades MAY be given to marginal performance, but do not expect them):
A = 90% through 100% and above
B = 80% through 89.99%
C = 70% through 79.99%
D = 60% through 69.99%
F = Less than 59.99%
If you must submit work late you need to talk to me at least one-week
before the due date in question. Otherwise, late work cannot be
accepted except in cases of verifiable emergencies.
It is highly recommended that you attend class. I may choose to track
We will be observing all university policies regarding
religious holidays and disability policies. Any student requesting disability accommodation for this class must inform the instructor giving appropriate notice. Students are encouraged to contact Disability Support Services (www.unco.edu/dss) at (970) 351-2289 to certify documentation of disability and to ensure appropriate accommodations are implemented in a timely manner.
Incomplete ("I") grades will only be given in the case of severe hardship
including verifiable medical emergencies or legal troubles. Simply being
"overloaded" and unable to complete your work is not grounds for an "I"
Out of courtesy to other students please make sure that you turn off, or
place in silent mode, your cell phone.
Academic Integrity/Academic Dishonesty: I expect students to be honest
and not cheat on their assignments, project, and exams. Students may work
together on the project with one other person in the class. Both students will earn the same grade. The exams must be completed
without giving or accepting assistance from other students. Any source code
copied from another source must be credited as such. Open source software used
must maintain all headers and other information as required by the open source
license used. I expect you to know the University's policies on student conduct,
academic dishonesty, etc. UNC's policies and recommendations for academic misconduct will be followed. For additional information, please see the Dean of Student's website, Student Handbook link and current catalog.
Every part of this syllabus is subject to adjustment as the semester progresses. Please contact me as soon as
possible if you have particular interest in material that is relevant to the class topic but not covered in enough
detail; I will be happy to accommodate reasonable requests for modifications.