We have recently developed an automated approach to reduce students' rationalization of programming plagiarism and collusion by informing them about the matter and reporting uncommon similarities to them for each of their submissions. Although the approach has benefits, it does not greatly engage students, which might limit those benefits. To…

All methodologies for detecting plagiarism to date have focused on the final digital "outcome", such as a document or source code. Our novel approach takes the creation process into account using logged events collected by special software or by the macro recorders found in most office applications. We look at an author's interaction…

In programming courses there are various ways in which students attempt to cheat. The most commonly used method is copying source code from other students and making minimal changes in it, like renaming variable names. Several tools like Sherlock, JPlag and Moss have been devised to detect source code plagiarism. However, for larger student…

The problem of Computer Science students' cheating in their homework assignments so far has been handled mainly through administrative punishment of the cheaters. The success of such an approach depends to a large degree on the ability of the instructor to recognize the fact of cheating, which is a complicated task. With a large number of students…

This paper examines student attitudes towards a number of behaviors which range from acceptable means of seeking help on assignments to unacceptable behaviors such as copying from another student or paying someone to complete an assignment. Attitudes regarding such behaviors are compared based on the type of assignment (programming assignment,…