Skip over primary navigation
Computer Science Department
Cheating Policy
 Adopted September 1983
Definition of Cheating

Any work submitted by a student which is not the student's own will be considered cheating.

The Penalty
  1. The student shall receive an E for the course.
  2. A letter notifying the student of the reason for the E will be sent to him/her, with the copies sent to the Dean of the College of Arts and Sciences and to the student's advisor, to be placed in the student's file.
  3. Should this not be the first instance of cheating, formal proceedings leading to suspension will be initiated.

Further,

  1. In the case of group projects, all members of the group are responsible individually and collectively for the work submitted by the group. As such, all members will share any penalty imposed, if any of the work submitted is not solely the group's work.
  2. In the case of a student not in the course submitting work in the name of another (for example, taking an exam for a student in the course, writing a program for a student ident in the course, etc.), formal proceedings leading to suspension from school will be initiated.
Concerning Help

Helping others and being helped is part of our lives. In the case of CSC courses, there is a fine line between helping others and doing work for others. Care must be taken. Helping another to understand the concepts involved is fine. Helping another to write the code has crossed the line. When in doubt, refer the student requesting help to their instructor. If you are in doubt about the extent of help that is acceptable, see your instructor.

N.B.
  1. Maintain complete records of all of your work. Do not dispose of any computer runs or notes. These will help document the progress of your ideas and work,
  2. Unless explicitly stated by your Instructor, all assignments in computer science courses are individual assignments, not group projects.
  3. Debugging another's program should be limited to finding the particular bug, and only after extensive effort made by the author. Fixing the bug is the responsibility of the author of the program.
  4. The use of publicly available algorithms must be accompanied by a correct and a complete reference to the source, containing all data necessary for identification.
 Last Updated: 7/9/07