2019
DOI: 10.3390/computers8010011
|View full text |Cite
|
Sign up to set email alerts
|

Automated Hints Generation for Investigating Source Code Plagiarism and Identifying The Culprits on In-Class Individual Programming Assessment

Abstract: Most source code plagiarism detection tools only rely on source code similarity to indicate plagiarism. This can be an issue since not all source code pairs with high similarity are plagiarism. Moreover, the culprits (i.e., the ones who plagiarise) cannot be differentiated from the victims even though they need to be educated further on different ways. This paper proposes a mechanism to generate hints for investigating source code plagiarism and identifying the culprits on in-class individual programming asses… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
11
0

Year Published

2019
2019
2024
2024

Publication Types

Select...
8

Relationship

5
3

Authors

Journals

citations
Cited by 10 publications
(11 citation statements)
references
References 32 publications
0
11
0
Order By: Relevance
“…Our technique is also more practical to be used compared to other techniques that are able to distinguish coincidental and non-coincidental similarity. It requires no specific assessment constraints [37] and IDE [38].…”
Section: Methodsmentioning
confidence: 99%
See 2 more Smart Citations
“…Our technique is also more practical to be used compared to other techniques that are able to distinguish coincidental and non-coincidental similarity. It requires no specific assessment constraints [37] and IDE [38].…”
Section: Methodsmentioning
confidence: 99%
“…We believe few detection techniques can mitigate such an effort for distinguishing even though it was not one of their primary aims. A technique in [37] for instance, can reduce the number of pairs with coincidental similarity during an in-class offline assessment as it limits the suspicion on source code files which authors are adjacently seated. Another example is a work proposed by [38] which timestamps each save actions and embeds it on the code.…”
Section: Related Workmentioning
confidence: 99%
See 1 more Smart Citation
“…These techniques rely on various structures for comparison. Some of the structures are source code token strings [8,29,41], abstract syntax trees [20,30,53], parse trees [48], program dependency graphs [32], and low-level token strings [25,42].…”
Section: Related Workmentioning
confidence: 99%
“…This could lead to several problems, especially those which are related to authorship and creative works. Hence, several automated plagiarism detection tools dedicated to code domain (e.g., JPlag [2], ES-Plag [3], and IC-Plag [4]) have been proposed. Using those tools, such an illegal behaviour can be detected with limited human effort.…”
Section: Introductionmentioning
confidence: 99%