Honor Code Guidelines
|Williams College Honor Code||Williams Computing Policies||CS Honor Code and Computer Usage Policy|
Explanation of the Honor Code as it pertains to this course:
I. Explanation related to help from people (i.e., non-written sources):
Reading responses / paper reviews: These are expected to be your work alone. When assigned a reading for which you are also writing a review, do not discuss the paper or your response with anyone other than one of the co-instructors. This will ensure that our tutorial session discussions will be fresh and interesting.
Regular weekly non-programming assignments other than reading responses or paper reviews: You may work alone or with classmates.
If you choose to work with classmates, you may discuss the problems and work out the general ideas together, but you must write up your detailed, step-by-step solutions individually. You must also clearly cite your partner(s) on the work you turn in. If you work with classmates, please be sure to observe appropriate social distancing rules. If you need help setting up virtual meetings, don't hesitate to ask a co-instructor.
You may consult with a co-instructor.
Consulting any person outside of the class is a violation of the honor code.
Programming assignments: On each programming assignment you will have the option of working either alone or with your tutorial partner. Programs that you turn in (just one if working with a classmate) must contain only: code written solely by your group or code written by yourself or other CS 374 students this semester for previous assignments. Code from previous assignments must be clearly credited where it is used and in a separate written note to me. It may be used only with permission of the students involved.
You are welcome to discuss design, general debugging strategy, and mathematics related to programming projects with other students, but you may not review the code of other students for any current assignment. Note that using previously submitted code and discussing programming projects is a more liberal policy than the default CS department policy.
Recall that in accordance with CS department policies, looking at any other computer user's files without permission is unacceptable, regardless of whether those files are protected on the file system.
II. Explanation related to help from written sources (paper or electronic):
We have provided a number of resources electronically. You are welcome to use those resources when working on your assignments. If you are using a resource not specifically mentioned in an assignment write-up, you must cite it.
Source code for the Weka data mining toolkit is freely available. Do not use this (or any other electronically available code) as a "resource" when doing your own programming. All code you submit should be your own, with the exception of shared code as outlined above. If you have any questions about code resources you can or cannot use, please ask!
III. Explanation related to sharing your solutions:
Do not post your solutions to regular assignments in any public space (e.g. GitHub). Students taking the course should not be looking for solutions, but tempting them by making solutions available is inappropriate. This applies not just to the semester you are taking the course, but to the future as well.
If you wish to make some of your work available (for instance, so that potential employers can review it), you may post the work that you do for your final project, provided it does not substantially include work done for earlier assignnments in the course.