CS 160 - Programming Concepts and ApplicationsSummer II 2018 - Working Together in CS 160Quick Links: Canvas | John Cabot | Piazza | zyBooks |
|
| Home | Contact | Syllabus | Assignments | Schedule | Resources | | |
But you don't want to go into the specific details, and you certainly don't want to share." - Professor Pascal Van Hentenryck, Brown University, 1997 The purpose of this policy is to (1) protect the integrity of your hard
work and (2) ensure everyone has the opportunity to learn the course material.
The following policy exists
Be aware! Any suspected case of plagiarism (copying) will
be investigated in this class. Violations of this policy
will involve the Associate Dean of Students and
may result in an F course grade for all students involved.
1 Unless otherwise specified in writing, all CS 160 homework
assignments must be individual efforts.
How Cases of Plagiarism are FoundDeveloping a program is a creative exercise; just like in art, no two programs will
look exactly the same (unless the 'canvas' has been copied). To ensure copying does not exist, homework
assignments are checked via an automated system that generates similarity metrics between your work and that of
all other students and previous student work in this class. When a high-level of similarity is detected, the
course coordinator is notified and investigates the similarity. If plagiarism is evident, the course coordinator
begins the process of submitting an Academic Misconduct.
Examples of Academic MisconductThe following are provided to illustrate examples of academic misconduct.
These scenarios will always be considered as academic misconduct except
when involving an assigned project partner.
Simple Ways to Abide by this Policy
Citation ExamplesSimply add a comment in your program listing. Here are two examples:
// Collaborators: Fran Allen and Steven Hawking // Code taken from http://stackoverflow.com/foo/bar/baz ASK if any confusion on this policy. | |
Last Updated: 06/24/18 04:02
|