CS 68, Winter 2006: Policies

Dartmouth's honor code applies to this course, and academic misconduct policies will be strictly enforced. If you have questions, ask. Thanks to Prof. Chris Hawblitzel for a succinct description of homework policies for previous terms, used here with slight modifications.

Homework assignments will be distributed and are to be turned in via Blackboard. Solutions must be submitted electronically before class on the due date, and must be accompanied by a hard copy turned in at the start of class. Ample time is provided for each assignment, so in general, late submissions will not be accepted. Under extenuating circumstances (prolonged illness, death in the family, etc.), arrangements must be made with the instructor before the due date. Due to tight scheduling, presentations must be given on the assigned dates.

You may discuss the homework with other current CS68 students, but your submitted homework must be entirely your own. As part of a discussion, you may show (in person) another student your work. However, you may not copy anything directly from another student's work. For example, copying a portion of someone else's solution onto a piece of paper would violate the honor code, even if you eventually turn in a different answer. Similarly, e-mailing a portion of your code to another student, or posting it on an on-line forum, would violate the honor code. Although all students must create and type in their own code, you may help other students debug their programs once their programs are written.

We encourage discussion of homework assignments between students, subject to the rules above. Note that discussion between two students will be most useful when both students have already made serious attempts to solve the problem on their own. You do not need to acknowledge discussion with other students on your submitted work.

You may not look at the solutions to problems from previous CS68 classes, or discuss homeworks with students who took the class in previous terms.

The project will be conducted in groups approved by the instructor. Each team will focus on a separate programming language, to be approved in advance by the instructor. Free discussion with anyone anywhere is permitted; credit must be appropriately given with citations and references. It is generally up to the group to ensure a fair balance of work among the group members. Each student must separately submit a paragraph outlining the contributions of each member (including him/herself).

There will be a midterm exam and a final exam, each worth 15% of the grade. The exams are open-book, open-note. Communication during an exam is allowed only with the instructor and TA, in order to clarify questions.