|
Overview
This course will provide students with a thorough understanding of the
basic principles of computer networks, the design philosophy of the Internet,
and the details of Internet protocols, and the engineering and scientific
principles needed to understand computer networks. Students who complete this
course will be able to describe in detail the operations of Internet
protocols and develop their own Internet applications. Students will also
develop an understanding of the design and construction of network programs
via a semester long class project. At the end of the course, you should be
capable of network programming.
The prerequisite for CS 352 is Computer Architecture (CS 211), because
of number representation, as well as Introduction to Discrete Structures II
(CS 206), because students are expected to know basic probability. Students
are expect to know how to program in Java and use
simple data structures such as hash tables and arrays. Students are also
expected to understand the department's facilities and how to use the cereal cluster, handin, and
the FAS gradebook.
James F. Kurose and
Keith W. Ross, Computer Networking, 3rd edition.
Discussion: newsgroup-like discussion board and chat room are available through WebCT . Use the discussion board on WebCT for questions and discussions.
Include [CS352] on the subject line of all emails sent to the list or to instructor/TA. If you don't follow this protocol, your email will likely be discarded.
Students are expected to attend all lectures and perform all reading
assignments prior to lecture. Students are also expected to attend all
recitation section meetings. Students will be evaluated according to their
performance on a semester long programming project, 1 mid-term examinations,
and the final examination.
WARNING: This is a project course, which means that this course should
give you more than a passing knowledge of what writing working network
programs entails. The project will be a major undertaking. If you complete
the projects, you will have learned a lot. However, assess your commitment to
this course realistically. If you don't have the time or the inclination to
work hard on the project, you would be better off not taking the course.
Fortunately, the project will be programmed in Java, so you will not have to
learn a new programming language. You will have to learn how to build and
debug a reasonably size Java program and make it robust to outside errors.
You will also have to describe how your program work
in both a written document as well as an oral exam.
This one large project will be assigned, as two sub-projects. Up to two students can work as a group for each sub-project and you can change group
members for each project . Students
are required to complete the parts by the scheduled deadlines. Failure to
turn in the project by the deadline using the "handin"
program will result in a zero for all team members. No exceptions!
- Working
Together and Academic Honesty
Cheating on projects and exams will not be
tolerated. We want to protect the fairness and integrity of the class,
so we run code similarity detectors on the projects and scrutinize exams
for copying. Both parties in the exchange are liable; e.g. if you give
away solutions to friends, you're putting yourself at risk too. If you
get caught, it's a nasty process--- just don't go there! You're better
off dropping the course and trying it again.
The department academic integrity policy can be found at http://www.cs.rutgers.edu/policies/academicintegrity/.
- The
Gilligan's Island Rule
That said, we do encourage you to talk to your
classmates, provided you follow the Gilligan's Island Rule. After a joint
discussion of an assignment or problem, each student should discard all
written material and then go do something mind-numbing for half an hour. For
example, go watch an episode of Gilligan's Island (or
Reality TV in modern terms) , and then recreate the
solutions. The idea of this policy is to ensure that you fully understand the
solutions or ideas that the group came up with.
If you follow the Gilligan's island rule, often best route to follow to get a
question answered is to ask, in order:
1.
A classmate smarter than you.
2.
Your
TA.
3.
The professor.
We will schedule one mid-term during regular lecture hours. A cumulative final examination will be
held at the end of the semester.
Written homeworks are for your practice only,
we won’t grade them. It will be up to you to do them and ask the TAs and
instructors about problems that you don't understand. We highly suggest doing
the homeworks before getting/looking at the
solutions. This will be critical for the exams. We will also post previous
year’s mid-terms and finals so you can get an idea about the kinds of
questions that we might ask.
Midterms: 20 %
Final: 35 %
Project: 35% (part 1: 15%, part 2: 20%)
Class Participation: 10%
The programming part of the projects are typically
graded on how close they are to the functional requirements. The written
portion is graded on how well the TAs can figure out how your project is
constructed only from the written description. Exams are typically graded on
a curve. As a rule of thumb, the mean is a "C'" and each standard deviation
is one letter grade. This rule can be altered, however, if the class does
exceptionally well or poorly.
|