The Office of the Dean of Students has summarized University policy on academic
integrity. Here is the relevant link:
-
Student Guides to Academic Integrity, Cheating, Plagiarism, and Discipline
These 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 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 both by this policy and the policies expressed
in the UCLA Student
Conduct Code.
In accordance with University policy, we will submit cases of suspected
cheating to the Dean.