CSE 131 / 501N
Attention: The pages for the course this semester should be accessed through Canvas, using this link.Collaboration Policy
Academic integrity is an essential characteristic of any scholar.
- We regularly run programs that detect plagiarism on coding assignments.These tools are very effective and the evidence they produce is difficult to refute. The bottom line is that if you are cheating you will get caught, and the consequences are not worth it: see below.
- Anyone suspected of cheating on any assignment in this course will be referred to the Dean's office in Engineering Student Services (303 Lopata Hall).
- If found to be in violation, a student will receive an F in this course, and the event will be kept on file in the Office of Student Conduct and Community Standards for reporting to prospective employers, graduate schools, government agencies, etc.
- Other consequences imposed may include suspension or explusion from Washington University.
To avoid problems, it is important to understand what forms of collaboration are encouraged and which forms constitute cheating. This page provides both guidance and examples. Please read this carefully and ask questions as needed.
Questions about this material should be directed to an instructor, not to a TA. Do not ask TAs for clarification.
You are encouraged to work with other students on your assignments, and to help other students find and fix problems in their programs, provided that you comply with the following conditions:
|Don't do this||Instead do this|
|Show somebody your code or look at somebody else's code. Even if your intentions are just to learn something, the act of seeing somebody else's code is against our policy. Also there is a good chance some of what you see will end up in your solution, which is plaigiarism.||Talk about your at a conceptual level. You can use a board or paper to diagram ideas. Just don't write code down!|
|Dictate solutions to somebody. Telling somebody what to write down step by step is no different than showing that person your code.||Have a conversation about where the person is stuck. Make suggestions using prose about how to move forward. If there is a programming construct, such as recursion or iteration that you feel is helpful, suggest that the person think along those lines but do not express your advice in code.|
|Look at or copy solutions from the Internet.||Use the Internet to look at other problems or to find resources to help you learn the material. Your searches should be concept-driven, not code-driven.|
|Post your solutions. If a student copies your code, that student and you are each guilty of violating our academic integrity policy.||Keep your solutions to yourself, in the private repository we have provided.|
|Let somebody use your computer. You may have good intentions, but students have been found in violation of academic integrity by loaining a computer to another student, who then plagiarized code from the loaned computer.||Point out that the Urbauer Labs are open 24/7 and offer computers for all students to use.|
|Help a student debug a program by taking control of the debugging process. This causes you to look at another student's code, which is not allowed, and also it is likely you will find or fix the problem without the student learning how to do such things without your help.||
Make suggestions about how to debug, or how to use the debugger.
Point out the many TA hours we offer during which students can be helped past such sticking points.
The infraction can be reported to graduate schools, employers, or government agencies on their request.