It is the responsibility of every student to make sure their work is not available to others. Thus do not leave your work behind on a disk or on the computer screen or even a hard copy of your work (even in the garbage or if you forgot to pick up your print out). All of the above consitute negligence on the student's behalf and are potential breaches of academic honesty.

One way to help adjudicate possible cases of forgery is to analyze the level of understanding each student has in their own work. Since this understanding is at the center of the course goals, each student must strive to have a complete understanding of every exercise.

The assignments and all extra credit exercises assigned for this course are not team projects unless the instructor explicitly tells you so. You should not develop a single solution working together as a team. Even developing it "part way" can cause problems. Two identical or nearly identical solutions to the same problem will be regarded as evidence of over-collaboration and will be dealt with as cheating. The borderline where simply consulting with others becomes working as a team or copying is a gray area. If you have any doubts, you probably are working too closely and should stop - go off and work by yourself.

• Do not develop an assignment "together".
• Do not develop an assignment "side by side" while looking at each other's code.
• Do not show or give your assignment to anyone. 
• Do not leave your program on any computer. On CIRCA computers, when you log out from a PC, a message from the machine that indicates that the hard disk is being purged does not guarantee that your files have all been deleted. Delete them yourself. If someone steals your program that way, you can still be found guilty of Academic Dishonesty for facilitating their dishonest act.
• If you let someone use your computer, make sure all copies of your work are either protected or deleted. If they take your work, even if it's without your knowledge, you can still be found guilty of an act of Academic Dishonesty. Bottom line: it is your responsibility to protect your own work.
• Helping someone find a bug in their code is a gray area. Many bugs will stump people for many hours, and it's only humane to let people know the pitfall they've fallen into. We encourage students to help each other in this regard, but be careful: if you find all of someone's bugs, you've deprived them of the process of learning how to find bugs themselves. Here's good rule of thumb: the person you're helping must be actively engaged in the process of searching for the error. Beware of those who merely stand aside and let you fix their program: they're willing to let you make significant contributions to their program, and then turn it in as their own. This activity is unlikely to produce evidence of over-collaboration, but it is unethical nevertheless.

Please check  http://www.dso.ufl.edu/Academic_Honesty.html