This guide covers the cheating policy for this class, as well as the attribution, commit, and AI policies which are often related to the discussion on cheating.

TABLE OF CONTENTS

Attribution Policy

Students must attribute all discussions and external resources utilized for their assignment submissions except for those provided by the instructor as part of lecture or code review. This includes but is not limited to:

• All discussions with TAs, tutors, and classmates. Failure to attribute discussions may be considered a violation of academic integrity, even if the discussion itself was not problematic.
• All prompts and responses from using AI tools. Students should save their prompt history if using AI tools so that the instructor can compare the prompt responses to your code. This prompt history should be submitted alongside the associated assignment. Review the AI Policy section for details.
• All non-class non-reference web resources. This includes websites such as StackOverflow (even if the resources are not in English). Students do not need to attribute reference resources such as the Java API or the MDN Web Docs.

If attribution becomes too arduous, then students are relying too heavily on these resources and should reach out to the instructor for an advising appointment.

Commit Policy

Students must maintain an incremental commit history of all code submitted as part of this class. This is how students "show their work" when it comes to code and standard practice in industry. For example, students should commit anytime:

• Something is created (such as a new class, method, or member)
• Something is changed (such as a method signature, or variable or class name)
• Something is fixed (such as passing a unit test, or fixing a bug)
• Something is shared (such as asking for help at the CS Tutoring Center)

This includes committing before seeking help (regardless of whether it compiles or passes tests) so that the original code written by the student is preserved in the commit history.

Students should always include informative commit messages. For example, "added skeleton Driver class" or "made counter variable non-static" or "fixed off-by-one error" or "getting help from Sophie on the parse method" are reasonable commit messages.

Students facing technical difficulties with git must resolve those problems before continuing to work on homework or projects to avoid the consequences of violating the academic integrity honor code.

AI Policy