Academic MIsconduct Policy


•Don't cheat. Cheating on anything will be dealt with as academic misconduct and handled accordingly. I won't just give a grade of zero. By the University's rules, I am obligated to hand over all suspected cases of academic misconduct to the University's Academic Misconduct Committee.


•You may discuss assignments at a high level amongst yourselves to overcome problems in understanding the problem or discussing a possible solution to a sub-problem. You may help a student with programming language or technical issues or to overcome a nasty bug in their code, but you must not use any code from that student’s solution in your submission if you look at their code. Please do not show another student your code in any manner (visually, an electronic copy file of your source code, a print-out, etc.). If that person uses it in their solution, you will be found culpable also if your solutions are found to be too similar.


•You are to write YOUR OWN code when you sit down and implement your solution. Do not work with another student while writing your solution. Do not share code, i.e. do not transmit your code to another student or receive code from another student and use it in your assignment. Do not use code from a student who took the course in a previous quarter. Archive copies of previous quarter assignments are maintained and I can easily spot if your results match work from a previous quarter. Near duplicate assignments will be considered cheating unless the assignment was restrictive enough to justify such similarities in independent work.


•Refer to the University's procedures on Academic Misconduct, especially sections 1 and 4.