15-719 Course Policies

Cheating policy

Each exam and project must be the sole work of the student turning it in. Like the University as a whole, we take cheating very seriously. See ECE's statement on student integrity for more information, including a link to the University's policy. The usual penalty for cheating is to be removed from the course with a failing grade. The University also places a record of the incident in the student's permanent record. No collaboration on exams is allowed. Be sure to store your project work in protected directories, and log off when you leave an open cluster, to prevent others from copying your work without your explicit assistance. Unless otherwise notified, the following guidelines dictate what non-exam collaboration is authorized and what is not:

What is Cheating?

Sharing code or other electronic files: either by copying, retyping, looking at, or supplying a copy of a file from this or a previous semester. Also not allowed is verbal or other description of one person's code to another. Be sure to store your work in protected locations, and log off when you leave an open cluster, to prevent others from copying your work without your explicit assistance. Sharing written assignments or exams: Looking at, copying, or supplying an assignment or exam. Using other's code. Using code from this or previous offerings of 15-719/18-847B, from other courses at CMU or other institutions, or from any other non-719/847B source (e.g., software found on the Internet). Looking at other's code. Although mentioned above, it bears repeating. Looking at other students' code or allowing others to look at yours is cheating. There is no notion of looking "too much," since no looking is allowed at all.

What is NOT Cheating?

Clarifying ambiguities or vague points in class handouts or readings. Helping others use the computer systems, networks, compilers, debuggers, profilers, or other system facilities. Helping others with high-level design issues only. Algorithm implementations and other such details are not "high-level design issues". Helping others with high-level (not code-based) debugging.

Last updated: Mon Sep 01 19:22:23 -0400 2014 [validate xhtml]