Princeton University Computer Science Department

Computer Science 217 Introduction to Programming Systems Randy Wang

Fall 2004

Lectures

Precepts

Assignments: Late Submission

• 95% for work submitted up to 3 hours late,
• 90% for work submitted up to 6 hours late,
• 85% for work submitted up to 12 hours late,
• 75% for work submitted up to 24 hours late,
• 50% for work submitted up to 48 hours late,
• 0% for work submitted more than 48 hours late.

You have one "late pass" that allows you to submit any one assignment up to three days late without penalty. If you wish to use your "late pass" on an assignment, you must explicitly tell us, in writing, before the assignment's due date.

The final assignment is due on the Dean's Date, and we are not permitted to accept work after that date. Thus you may not submit the final assignment late.

Assignments: Collaboration

Programming in an individual creative process much like composition. You must reach your own understanding of the problem and discover a path to its solution. During this time, discussions with friends are encouraged. However, when the time comes to write code that solves the problem, such discussions are no longer appropriate - the program must be your own work. If you have a question about how to use some feature of C, UNIX, etc., you can certainly ask your friends or the teaching assistants, but do not, under any circumstances, copy another person's program. Writing code for use by another or using someone else's code in any form is a violation of academic regulations. "Using someone else's code" includes using solutions or partial solutions to assignments provided by commercial web sites, instructors, preceptors, teaching assistants, friends, or students from any previous offering of this course or any other course.

You may, however, use any code from the COS 217 lectures, precepts, or course texts, providing that you explain what code you use, and cite its source in your "readme" file or in comments. For each assignment, you must also specifically describe whatever help (if any) that you received from others in your "readme" file, and write the names of any individuals with whom you collaborated. This includes help from friends, classmates, lab TAs, and COS 217 staff members.

If you have a question about what is fair and what is not, please consult a staff member. Violators will be referred to the disciplinary committee for review. Princeton's Rights, Rules, Responsibilities document asserts:

The only adequate defense for a student accused of an academic violation is that the work in question does not, in fact, constitute a violation. Neither the defense that the student was ignorant of the regulations concerning academic violations nor the defense that the student was under pressure at the time the violation was committed is considered an adequate defense.

You are responsible for keeping your solutions to the COS 217 programming assignments away from prying eyes. If someone else copies your program, we have no way to determine who's the owner and who's the copier; the Discipline Committee gets to decide. If you are working on a public cluster machine, be sure to delete your local source files and logout before leaving.

You should store all of your assignment files in a private directory. You can create a private directory using commands similar to these:

% mkdir cos217
% chmod 700 cos217

Communication

Alternatively, you may send email to all of the course's instructors (cos217@cs.princeton.edu) or to your preceptor. In general, if your question/comment will be helpful to other students, then you should e-mail it to the listserv; if your question/comment is specific to your work, or if you must reveal portions of your work to express your question/comment adequately, then you should e-mail it to your preceptor.

Grading