Cheating Policies

The general academic policies on cheating and plagiarism established by the University apply within this course. The decision as to whether a student has cheated depends on the intent of an assignment, the ground rules specified by the instructor, and the behavior of the student. The following two guidelines help an instructor decide if cheating has occurred:

• Program plagiarism will be suspected if an assignment that calls for independent development and implementation of a program results in two or more solutions so similar that one solution can be converted to the other(s) by a series of simple commands.
• Cheating will be suspected if a student who completed an assignment cannot explain both the intricacies of the solution and the techniques used to generate that solution.

It is unreasonable to expect a complete definition that would cover all cases because each situation is important enough to merit careful, individual scrutiny; however, it is helpful to have guidelines and precedents. As a general rule, if you do not understand what you are handing in, you are probably cheating. If you have given somebody the answer, you are probably cheating. In order to help you draw the line, here are some examples of clear cases of cheating:

Examples of Cheating:

• Turning in someone else's work, in whole or in part, as your own (with or without his/her knowledge).
• Turning in a completely duplicated assignment.
• Allowing another student to turn in your work as his/her own.
• Allowing someone else to examine or copy your code or written assignment, either in draft or final form.
• Reviewing files from another student or source, including retyping their files.
• Several people writing one assignment and turning in multiple copies, all represented (implicitly or explicitly) as individual work.
• Stealing an examination or solution from the instructor or course staff.
• Copying from another student during an exam, quiz, or midterm. This includes receiving exam-related information from a
  student who has already taken the exam, or providing exam-related information to a student who has not yet taken the exam.

On the other hand, we encourage you to discuss the exercises and homework with other students. But the discussion is limited to clarifying the assignments and sketching a general approaches to a solution. You should never look at another person's program to help you write yours, nor allow another student to look at your program. It is
important that you do your own work so as to maximize your learning. Here are some examples of acceptable collaboration:

Examples of Not Cheating:

• Turning in work done alone or with the help of the course's staff.
• Getting or giving help about using the computers.
• Getting or giving help about solving minor syntax errors.
• High level discussions of course material for better understanding.
• Discussing the code that we give out on the assignment.
• Discussing the assignments to better understand them.
• Providing assistance with the Java language, class library,and tools.

We will not condone cheating.When cheating is suspected, instructors will take reasonable action to establish whether it actually occurred. If it has, the instructor will apply appropriate disciplinary policy. The ordinary University penalty for cheating is failure of the course. (See the CMU Student Handbook.) Penalties less severe than the recommended penalty will be imposed when appropriate. A list of possible disciplinary actions is given below.

Actions within the course include:

• Negative credit for the assignment.
• Loss of a letter grade in the final grade for the course.
• Not being able to drop or withdraw the course.
• Not being able to take the course as "pass/fail".
• Failure of the course.

Actions by the University include:

• Warning.
• Academic Probation.
• Academic Suspension from the University for a designated period.
• Expulsion from the University.

The following policies apply to all cases of cheating and plagiarism:

• First Offense - The penalty will always be more severe than the penalty for failing to turn in the assignment (or take the exam) in question.
• Flagrant or Repeated Offense - The instructor shall either refer the incident directly to the University for action or assign a penalty no less severe than failure of the course.

STUDENT RIGHTS

In the event that a faculty member accuses a student of cheating and imposes a penalty, the student who believes that the accusation is unjust has the right to request that the charge of cheating be heard before the University Committee on Discipline.

STUDENT RESPONSIBILITIES

Certain constraints on behavior must be followed in any community of Individuals who share space and limited resources (with our apologies to the vast majority of responsible students). Please be aware of the following standards of behavior. Violations will not be tolerated. Appropriate disciplinary actions include loss of computing privileges, course failure, ineligibility for subsequent courses offered by the Computer Science Department, dismissal from the University and/or criminal prosecution. At minimum, any student who violates these rules can expect to find his/her access to facilities revoked.

Prohibited behavior includes but is not limited to

• Theft, tampering, or other abuse of the system/network software.
• Theft or tampering of other users' files.
• Disabling or damaging computers, drives, or other facilities/equipment.
• Any action that compromises system/network performance.
• Subjecting other students to harassment, or otherwise negatively affecting other students' work.
• Smoking in the cluster room.

COMPUTER CLUSTERS

Please refrain from behavior that is unduly loud and boisterous when using the clusters. The clusters aren't a library and we want you to feel comfortable when you're there, but please respect the rights of your fellow students who are trying to concentrate. Since you are required to work with computers in this course, you must remember that computers frequently break. Also remember that the clusters are shared with students from other courses, so it is clearly to your advantage to complete labs and program assignments in advance of the due date. We will do everything reasonable to ensure a high level of support, but remember that occasions arise when the computers are simply not available, so we solicit your patience. If you notice a machine that is inoperable, please inform us.