CS 10 Collaboration Policies - Spring 2005

-In-lab and in-lecture exercises:
	
	  Collaboration is strongly ENCOURAGED. Whether giving help or getting
	  help, you will learn more when working with others. In lab, you will
	  be "paired up" with 1 or 2 other students by the TA. In lecture, I 
	  recommend working with your neighbors as much as possible. You will
	  still be turning in your own solution that should not be identical
	  to your partners, but we will not penalize you for similar code. Of
	  course, if you rely too much on others and do not learn from these
	  exercises, you will struggle on the big-point assessment items
	  (exams, practicals, and programming assignments).

-CodeLab Homework:

	  We encourage collaboration on this as well. A great way to do these
	  is to get started on your own before your study group meets. Then
	  compare answers and help each other solve the tougher ones together.
	  There are usually many different ways to solve the same problem.
	  If you compare even the answers you got right you will most likely
	  learn much more than just completing these on your own. Again as with
	  in-lab and in-lecture exercises, if you just copy other students' 
	  solutions, you will only hurt your grade when it comes to the 
	  big-point assessment items.

-Quizzes, Midterm, Final, Lab Practicals: 

	  No collaboration is allowed at all.

-Programming Assignments:

	  LIMITED collaboration is ok. You may do the following while writing a
	  programming assignment: discuss general solution ideas with your 
	  study group members or have members observe a run of your program,
	  and offer their ideas on its behavior. You should *never* look 
	  at someone else's code for that assignment to figure out how to do 
	  your own program. It is very hard to write your own unique solution
	  once you have seen someone else's. If you need someone to look at 
	  your code to give advice, you should see a TA or instructor.
	  Of course, copying code from ANY source (any book, current or past 
	  student, past solutions, or the web) is STRICTLY FORBIDDEN.  

	  Unfortunately, every quarter several students choose not to follow 
	  these rules and get caught. We send all student submissions 
	  through a program that matches up similar code. This program ignores 
	  variable and function names and just looks at the structure of the 
	  program. You would have to spend more time trying to fool this 
	  program then actually writing the program yourself, so don't try it.

-Active and Passive Cheating

  	There are two forms of cheating: active and passive. If a student 
	provides a solution to another (active) then both students are guilty 
	of cheating. Likewise, if a student indirectly makes work available to 
	another student (passive), they are both just as guilty as active 
	participants. Indirectly providing solutions includes leaving program 
	print-outs and other work in the lab or in a trash can where other 
	students can find the work or leaving your computer unattended for an 
	extended length of time or giving your cs account password to another
	student. Also, any student who asks another to provide help in 
	violation of these principles is guilty of cheating.

-Violation penalties
	 
	Any student that violates the collaboration policy on a given item will
	at minimum receive a 0 on the item in question up to possibly receiving
	an F in the course and being reported to Student Judicial Affairs.


I have read this form in its entirety and understand the seriousness of 
cheating. I also understand that there are severe consequences including 
possibly receiving an F in the course if I do not follow these policies. If I 
have any questions regarding the contents of this form I will ask the 
instructor for clarification.

Name:
SID: 
Login:

CS 010
Spring 2005