CS 31 Academic Integrity Agreement

Computer Science Department
University of California, Los Angeles

Fall 2007

In order to have any of your CS 31 coursework graded, you must turn in this signed agreement. This is a serious document; do not sign it without reading it.

The Academic Integrity document referred to is printed on the back of this page. It can be reached from the class webpage by following the Academic Integrity link, which takes you to http://www.cs.ucla.edu/classes/fall07/cs31/integrity.html.

I, the undersigned CS 31 student, have read the Academic Integrity document. I understand it and agree to abide by the policy it expresses.

Name (please print)_______________________________________________

Student ID number _______________________________________________

Lecture section (circle one):   1   2   3

Signature _______________________________________________________

Academic Integrity

At http://www.deanofstudents.ucla.edu/conduct.html, the Office of the Dean of Students presents University policy on academic integrity, with special attention to cheating, plagiarism, and student discipline.  The policy summaries don't specifically address programming assignments in detail, so we state our policy here.

Of course, you understand that your work on programming assignments must be your own. But we understand that high-level discussions about approaches to a problem have educational value and are acceptable. So where do we draw the line? We'll decide each case on its merits, but here are some categorizations:

Acceptable:

· Clarifying what an assignment is requiring

· Discussing algorithms for solving a problem, perhaps accompanied by pictures, without writing any code

· Helping someone find a minor problem with their code, provided that offering such assistance doesn't require examining more than a few lines of code

· Turning in someone's work without crediting the author of that work, if the source of that work is the course text, a CS 31 instructor, or a CS 31 TA

Unacceptable:

· Turning in any portion of someone's work without crediting the author of that work, if the source of that work is not the course text, a CS 31 instructor, or a CS 31 TA

· Using project solutions from earlier offerings of this or any other class

· Writing for or with another student a code fragment that solves any portion of a programming assignment

· Receiving from another person (other than a CS 31 instructor or TA) a code fragment that solves any portion of a programming assignment

· Helping the same person find problems with their code more than a few times for a particular assignment

You must abide by this policy in addition to those expressed in the UCLA Student Conduct Code. In accordance with University policy, we will submit cases of suspected cheating to the Dean.