A Note On Academic Misconduct

Please take a minute and read this document in its entirety!

Just a note to remind everyone what is OK and what is not OK in terms of talking to other students about assignments and projects.


  • discuss the assignment in general terms (what do they mean by a copy constructor?)
  • discuss how different C++ standard library functions work (different ways to insert an element in a std::vector)
  • discuss strategies for successful implementation (our data-structure format is simple)
  • help others debug their code and find problems
  • ask the instructo for as much help as you need!

It is NOT OK to:

  • bug someone else for a lot of help (particularly if they are already done!)
  • share your code directly with other people/project groups (oh, you want to now how to sort a vector of strings, well here is my code and it works so you can just use/copy that)

Discovery of any inappropriate code sharing will lead to harsh penalties for all involved parties. This draconian policy is in place to protect the bulk of you who have put in the hard work on the assignments and projects.

We expect that all students will conduct themselves with honesty and integrity. Academic misconduct is not acceptable. You are responsible for doing your own work as well as securing your work so that it is not available in any form to students other than your registered partner. Failure to do so can result in an academic misconduct investigation. Any investigation of academic misconduct is reported to the Dean's Office. If you are unsure if something is allowed or not allowed, ask your instructor BEFORE you do it. Additional information about policies specific to CS 368 can be found on the CS 368 course web page. Information about University Academic Integrity policies and procedures can be found at: https://www.students.wisc.edu/doso/academic-integrity/

Of course, if any code sharing is discovered, harsh penalties will be applied. Now I know that most or even all of you will not do this (and I know this all sounds quite unpleasant), but I just wanted to make it clear what the guidelines are.

If you have any further questions on the gray area between what is OK and what is NOT OK, please feel free to ask.

Reference: Most of these policies are adapted from Remzi's CS537 and modified for CS 368 (C++) by Gerald.