• summarize important issues and challenges at all levels of a computer network and
• develop robust client/server applications.

One (perhaps none) of the programming assignments will require working in groups of size two or three. All other work is to be completed individually.

For group assignments, each member of each group MUST turn in a group evaluation form by the date the group programming project is due. If a form is not received from each group member, the group will be penalized.

Graduate students must do all parts of each programming assignment, and all exercises in each homework assignment. Undergraduate students are required to do a portion of each assignment; the portion that can be omitted will be determined at each assignment.

Submit programming assignments by 11:59pm on the date that they are due. Submit paper copies of homework assignments at the start of class on the date that they are due. Always turn in something rather than nothing. Nothing earns you zero points; something earns you partial points.

Each student is allocated five slip days for the programming assignments, which gives students some flexibility in managing their workload. Weekends count two days. (Each group member uses a slip day for each day the assignment is submitted after its due date, if the assignment is completed as a group.)

Programming assignments should be submitted electronically to Blackboard. For Project $N$, you will submit a tar(1) file, e.g., tcamp-projectN.tar, in which the filename is the same as your username and $N$ is the project number. When untarring this file, it should create a directory with the same root name as the tar file, e.g., tcamp-projectN. Inside every tar(1) file will be a file named README with your name, a listing of all the other files in the tar(1) file and what they do, and how to compile and run your code.

1. If the project is an individual effort project, you are not allowed to give code you have developed to another student or use code provided by another student. If the project is a group project, you are only allowed to share code with your group members.
2. You are encouraged to discuss programming projects with other students in the class, as long as the following rules are followed:
   1. You view another student's code only for the purpose of offering/receiving debugging assistance. Students can only give advice on what problems to look for; they cannot debug your code for you. All changes to your code must be made by you.
   2. Your discussion is subject to the empty hands policy, which means you leave the discussion without any record [electronic, mechanical or otherwise] of the discussion.
3. Any material from any outside source such as books, projects, and in particular, from the Web, should be properly referenced and should only be used if specifically allowed for the assignment.
4. If you are aware of students violating this policy, you are encouraged to inform the professor of the course. Violating this policy will be treated as an academic misconduct for all students involved. See the Student Handbook for details on academic dishonesty.

                   All projects for CSCI 471/598 are to be individual
                            efforts unless explicitly stated otherwise.