For decades many computing departments have deployed systems for the detection of plagiarised student source code submissions. Automated systems to detect free-text student plagiarism are just becoming available and the experience of computing educators is valuable for their successful deployment.This paper describes a Four-Stage Plagiarism Detection Process that attempts to ensure no suspicious similarity is missed and that no student is unfairly accused of plagiarism. Required characteristics of an effective similarity detection engine are proposed and an investigation of a simple engine is described. An innovative prototype tool designed to decrease the workload of tutors investigating undue similarity is also presented.
No takes yet. Share an insight, caveat, or question.
Lancaster et al. (2001) studied this question.
Synapse has enriched one closely related paper. Consider it for comparative context: