Computer Science 333
Regular lecture attendance is required and lecture participation helps. Frequent absences are grounds for a failing grade regardless of other performance. This means you.
You will be responsible for the material presented in every lecture. Much of that material will not be in the textbooks.
You should submit your work on an assignment (electronically) before its due time. If you submit your work late, we will give you credit for it on this scale:
If an assignment consists of multiple files, then we will consider the date/time of submission of your work as a whole to be the same as the date/time of submission of the last file that you submit.
We will grant extensions only in the case of illness (with a doctor's note) or extraordinary circumstances. If illness or an extraordinary circumstance will cause you to submit an assignment late, then you should discuss the matter with the Directing TA of that assignment as soon as possible. Please plan your work on the assignments so that travel, religious holidays, etc. do not cause you to submit it late. Heavy workload is not an extraordinary circumstance.
You have one "late pass" that allows you to submit any one assignment up to three days late without penalty. You can apply your late pass to at most one assignment; you cannot split your late pass across multiple assignments. If you wish to use your late pass on an assignment, then you must tell the course instructors via e-mail before the assignment's due date/time.
The assignments involve working in teams of two. You may use your late pass on a team assignment if and only if your teammate uses his/her late pass on that assignment. (The implication is that you may not use your late pass on a team assignment if your teammate has already used his/her late pass.) If you wish to use your late pass on a team assignment, you and your teammate must tell your TA via e-mail before the assignment's due date/time.
The policies described in this section supplement the University's academic regulations, making explicit what constitutes a violation for this course. Princeton's Rights, Rules, Responsibilities handbook 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.
If you have any questions about these matters, please consult a course staff member. Violators will be referred to the Committee on Discipline for review.
The COS 333 assignment collaboration policy is derived from that of Princeton's COS 217 course...
Programming is 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 other people are permitted and encouraged. However, when the time comes to write code that solves the problem, such discussions (except with course staff members) are no longer appropriate: the code must be your own work. If you have a question about how to use some feature of C, Unix, etc., you certainly can ask your friends or the teaching assistants, but specific questions about code you have written must be treated more carefully.
For each assignment you must specifically state, in your
readme file, the names of any individuals from whom you received help, and the nature of the help that you received. That includes help from friends, classmates, lab TAs, course staff members, etc.
Do not, under any circumstances, copy another person's code. Incorporating someone else's code into your code in any form is a violation of academic regulations. This includes adapting solutions or partial solutions to assignments from any offering of this course or any other course. There is one exception to the code-sharing rule: You may adapt code from the COS 333 course materials provided that you explain what code you use, and cite its source in your
Copying and transforming someone else's code (by rearranging independent code, renaming variables, rewording comments, etc.) is plagiarism. Some inexperienced programmers have the misconception that detecting such plagiarism is difficult. Actually, detecting such plagiarism is quite easy. Not only does such plagiarism quickly identify itself during the grading process, but also we can (and do) use software packages, such as Alex Aiken's renowned MOSS software, for automated help.
If we suspect a student of plagiarism on an assignment, then we will refer the case to the Committee on Discipline. If the Committee on Discipline finds the student guilty of plagiarism, then the standard penalty is automatic failure of the COS 333 course. The Committee on Discipline may impose additional penalties.
For each assignment you must specifically state, in your
readme file, the names of any individuals to whom you provided help, and the nature of the help that you provided.
Abetting plagiarism or unauthorized collaboration by "sharing" your code is prohibited. Sharing code in digital form is an especially egregious violation. Do not e-mail your code or make your code available to anyone. Do not share your code with anyone even after the due date/time of the assignment.
You are responsible for keeping your solutions to the COS 333 programming assignments away from prying eyes. If someone else copies your code, we have no way to determine who is the owner and who is the copier; the Committee on Discipline decides. If you are working on a public cluster computer, make sure that you do not leave the computer unattended, and that you delete your local files and logout before leaving.
These are the course's policies concerning electronic communication:
Your final grade will be weighted as follows:
This page was written by Robert M. Dondero, Jr.