Detecting Plagiarism based on the Creation Process

December 10, 2016 ยท Declared Dead ยท ๐Ÿ› IEEE Transactions on Learning Technologies

๐Ÿ‘ป CAUSE OF DEATH: Ghosted
No code link whatsoever

"No code URL or promise found in abstract"

Evidence collected by the PWNC Scanner

Authors Johannes Schneider, Avi Bernstein, Jan Vom Brocke, Kostadin Damevski, David C. Shepherd arXiv ID 1612.09183 Category cs.OH: Other CS Cross-listed cs.SE Citations 29 Venue IEEE Transactions on Learning Technologies Last Checked 1 month ago
Abstract
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 logs with the software used to create the work. Detection relies on comparing the histograms of multiple logs' command use. A work is classified as plagiarism if its log deviates too much from logs of "honestly created" works or if its log is too similar to another log. The technique supports the detection of plagiarism for digital outcomes that stem from \emph{unique} tasks, such as theses and \emph{equal} tasks such as assignments for which the same problem sets are solved by multiple students. Focusing on the latter case, we evaluate this approach using logs collected by an interactive development environment (IDE) from more than sixty students who completed three programming assignments.
Community shame:
Not yet rated
Community Contributions

Found the code? Know the venue? Think something is wrong? Let us know!

๐Ÿ“œ Similar Papers

In the same crypt โ€” Other CS

Died the same way โ€” ๐Ÿ‘ป Ghosted