CSc 352: Academic Integrity

It is permissible to discuss problems with others in broad terms, e.g., the structure or approach of a program. It is not permissible to discuss concrete details of solutions to a particular assignment before the due date/time for that assignment. A simple way to distinguish between these two situation is to use Stuart Reges' characterization: you can talk to each other in English, but not in C/Unix.

Any work that you turn in for credit is assumed to be your own, unless you explicitly indicate otherwise. Collaboration on programming assignemnst is not permitted. It is permissible to use "publicly visible" code -- code that is available in books or magazines, or which has been distributed in class -- in programming assignments, as long as the authorship of such code is adequately and explicitly acknowledged. It is not permissible to solicit code from others, e.g., by posting requests to Usenet newsgroups. It is also not permissible to use code written by CSc 352 students in previous terms.

For the purposes of this course, cheating is considered to be any attempt to pass off someone else's work as your own. (See also UofA Code of Academic Integrity.) Cheating will not be tolerated: any student caught cheating or helping another student cheat in homeworks, exams, or programming assignments, will be given a failing grade in the course. I intend to interpret the phrase ``helping another student cheat'' broadly: for example, if another student gains access to your code because you forgot to logout, or were careless about listings that were dumped into the recycling bin, you have helped that student cheat.