CS565 Policies

Programming is a creative process. Individuals must reach their own understanding of problems and discover paths to their solutions. During this time, discussions with friends and colleagues are encouraged, and they must be acknowledged when you submit your written work. When the time comes to write code, however, such discussions are no longer appropriate. Each program must be entirely your own work.

Do not, under any circumstances, permit any other student to see any part of your program, and do not permit yourself to see any part of another student's program. In particular, you may not test or debug another student's code, nor may you have another student test or debug your code. (If you can't get code to work, consult the teaching assistant.) Using another's code in any form or writing code for use by another violates the University's academic regulations.

The standard penalty for violating these rules on one part of one assignment is to receive a zero for the entire assignment and in addition to receive a reduction of one letter grade for the course. This penalty may be adjusted at the professor's discretion, up to and including the assessment of a failing grade for the course. Repeat offenses will be dealt with harshly. In serious cases, the Dean may choose to take additional action, including possible suspension or expulsion from the University.

You may look in the library (including the Internet, etc.) for ideas on how to solve homework problems, just as you may discuss problems with your classmates. All sources must be acknowledged.

Homework solutions must be neat and well organized. Students are encouraged to use the computer to prepare homework solutions. Any work that cannot easily be read will score zero points. Clear English expression is required.


The above policies were adapted from those of Professor Ramsey (CS 565, Spring 1996).