No Copying Policy

IMPORTANT: DO NOT Copy/Share Any Portion Of THE PROJECT.

The project is a continuous cumulative project with a series of checkpoints. Copying any portion (even from your own project from a prior semester) means you cheated on the whole project. Cheating is copying or sharing solutions. All work must be done by you. A tutor must not help you with project content. You are not allowed to use (look at, copy) any online source that is specifically related to this project beyond those explicitly provided by us. Once the project is over, your repository must remain private, and must not be shared publicly on the internet.

Cheating results in a range of penalties:

from at least a course grade cap of 50% to 0% on the project

Note: since the project is worth 40% of the course grade, 0% on the project means a likely failing grade.

All cheating results in a report to the dean, and possible referral to the President's Committee.

Cases will be referred to the Dean of Science who can then elect to send the case to the President's Advisory Committee. After meeting with that committee, students have been suspended or given a 0 in the course for copying in past terms.

You are NOT allowed to:

look at prior solutions to this project, or current students' code for the project.
use, look at, etc any aspects of your own prior solution, if you have taken the course previously.
copy code or algorithms from others or the web without appropriate attribution.
discuss code-level details or pseudo-code level algorithms with students past or present and you are not allowed to take other students' help in any detailed way.
share or discuss details of code or algorithms with students past, present or future or with tutors.
post code to the web during the course, or after completing this course: Project bootstrap code is covered under our internal use license and cannot be shared. Posting code publicly is a copyright violation.

Make sure every line of code you commit is either provided by us, or written by you (or your partner). If you see snippets of code on stack overflow or some *general* resource, you can use them but you must cite your source, and indicate the extent of the code used. Similairly, for AI-based tools you must cite your source and the extent of any generated code block that you are adding to your repository. As in a corporate environment, you are resposible for every line of code you commit to your repository. While you can use AI-based tools to help you with your project, they are *yours* when you commit them. TAs cannot help with any code you did not write yourself and plagiarism detection will still be run on all repositories whether AI tools were used or not.

This policy is bidirectional: whether you copied some other code, or your code was copied, the penalties are the same.

It is straightforward to avoid violating this policy:

- Always make sure your work is your own.
- Never look at or copy another team's solution, either from this term or past terms.
- If you have a tutor, don't ask them project-specific questions - use them to help you generally on skill building.
- Do not share your code with other teams or post your solution online (see the License section below).

After the final checkpoint, we carefully examine all commits using automated analyses and the course staff carefully manually examine every case of derivative code. We will contact you if we have any questions about whether you violated the policy at some point during the semester.

Even if no copied code is retained in your final solution, if you have a commit with copied code, you have still committed academic misconduct.

Academic Misconduct at UBC

The official policies for Academic Misconduct can be found at the following links:

License for Course Materials and Project Sources

The readings and slides for this course are licensed using CC-by-SA. However, it is important to note that the videos, deliverable descriptions, code implementing the deliverables, exams, and exam solutions are considered private materials and all licensing rights are held by the course creators. We go to considerable lengths to make the project an interesting and useful learning experience for this course. This is a great deal of work, and while future students may be tempted by your solutions, posting them does not do them any real favours. Please be considerate with these private materials and not pass them along to others, make your repos public, or post them to other sites online.

Page updated

Google Sites

Report abuse