Mental Health and Wellness support

You are here

Home » Undergraduate Students » Forms

Team Cover Page

Instructions

  • The Team leader must type his/her student number in the Team Leader field.
  • Student numbers of Team members are entered in the subsequent fields.
  • Read the Policy on Cheating & Plagiarism.
  • Press the "Generate Cover Page" button.
  • Print the generated cover page with the barcoded student numbers on a laser quality printer.
  • Complete the remainder of the printed cover page. Be sure to print the name of each team member above the appropriate barcoded student number
  • The Team Leader then signs and dates this sheet on behalf of the team.
  • Attach the completed sheet to the outside (if applicable) of your submission.

Because the department uses barcoding to improve the tracking of submissions, it is important that you check to ensure that the student number under the barcode is correct. Submitting a cover page containing a student number other than ones own is unacceptable. Note: The department requires that a signed cover page accompany each submission. Submissions without a completed cover page will not be marked.

Student Number of Team Leader


Student Numbers of Team Members:




Policy on Cheating and Plagiarism

Revision 7/96

"Plagiarism is stealing a ride on someone else's train of thought."

Preamble

Since the Department is a part of the University, the general academic policies on cheating and plagiarism as found in the Undergraduate Calendar (Academic Regulations - Section X) also apply within the Department. These policies suffice for much of the work, including examinations and written assignments. However, they do not deal explicitly with course work involving computers; thus the policies must be extended to cover these cases. Note that the terms "cheating" and "plagiarism" are effectively interchangeable for the purposes of this document. 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. 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 can be converted to another by an algorithmic transformation.
  • Cheating will be suspected if a student who was to complete an assignment independently cannot explain both the intricacies of his or her solution and the techniques used to generate that solution.

It is unreasonable to expect a complete definition of cheating; each case is important enough to be given careful, individual scrutiny. It is, however, helpful to have guidelines and precedents. Here are some examples of cases which are clearly cheating and clearly not cheating.

Cheating

  • Turning in someone else's work, in whole or in part, as your own (with or without his or her knowledge) and without acknowledgment. Turning in a completely duplicated assignment is a flagrant offense.
  • Allowing someone else to turn in your work as their own.
  • Several people writing one program and turning in multiple copies, all represented (implicitly or explicitly) as individual work.
  • Using any part of someone else's work without the proper acknowledgment.
  • Copying code from the web, even if it is an open source site (e.g. Github, StackOverflow), possibly modifying it, and handing it in as your own.
  • Stealing an examination or a solution from the instructor. This is an extremely flagrant offense.

Not Cheating

  • Turning in work done alone or with the help of the course's staff.
  • Submission of one assignment for a group of students if group work is explicitly permitted (or required).
  • Getting or giving help on how to do something on the operating system of the computer.
  • Getting or giving help on how to solve minor syntax errors.
  • High-level discussion of the course material for a better understanding.
  • Discussion of assignments to understand what is required.
  • Acknowledging via a comment in the code the source of the program segment.
    If you fully and correctly attribute the source (e.g. from an open source site) it may not be cheating, but you might not get credit for it.

Disciplinary Actions

The Department faculty will not condone cheating. When cheating is suspected, instructors will take reasonable action to establish whether it actually occurred. Appropriate disciplinary policy will be applied in all proven cases, always subject to the regulations contained in the Faculty Handbook, and described in the University Undergraduate Calendar. The penalty imposed may range from zero for the piece of work to expulsion from the University.