Detecting Plagiarism in Student Pascale Programs
The DOI matches its Crossref record.
Abstract
Detecting plagiarism in student Pascal programs is normally based on a statistical analysis of particular characteristics of style. We discuss how a ‘template’ can be constructed for each program, enabling us to identify other similar templates; this technique is used to extract similar regions or areas from our set of programs in order to perform the statistical analysis. Several examples are presented to show the power of this technique. We conclude by proposing a means of characterising programming style and suggest its use as a gauge for evaluating the student's assignment.
Overview
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Self-check
Percentages, sums and reported differences re-computed from the paper’s own numbers.
The self-check needs the paper’s full text.
Citations
Cited by
On finding duplication and near-duplication in large software systems
Baker, B. S. (2002) · Proceedings of 2nd Working Conference on Reverse Engineering · doi:10.1109/wcre.1995.514697 · Cited by 717
A language independent approach for detecting duplicated code
Ducasse, S., Rieger, M., & Demeyer, S. (1999) · Proceedings IEEE International Conference on Software Maintenance - 1999 (ICSM'99). 'Software Maintenance for Business Change' (Cat. No.99CB36360) · doi:10.1109/icsm.1999.792593 · Cited by 615
CP-Miner: finding copy-paste and related bugs in large-scale software code
Li, Z., Lu, S., Myagmar, S., & Zhou, Y. (2006) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2006.28 · Cited by 610
Learning to Detect and Classify Malicious Executables in the Wild
Kolter, J. Z., & Maloof, M. A. (2006) · doi:10.5555/1248547.1248646 · Cited by 562
Finding Plagiarisms among a Set of Programs with JPlag
Malpohl, G., Prechelt, L., & Philippsen, M. (2002) · Verlag der Technischen Universität Graz · doi:10.3217/jucs-008-11-1016 · Cited by 56
“Some of these systems are hybrids between structure and metric comparison, e.g. [Donaldson et al., 1981; Jankowitz, 1988], others (such as JPlag) rely on structure comparison alone.”
BackgroundLearning to detect malicious executables in the wild
Kolter, J. Z., & Maloof, M. A. (2004) · Proceedings of the tenth ACM SIGKDD international conference on Knowledge discovery and data mining · doi:10.1145/1014052.1014105 · Cited by 475
Hirschheim, R., Klein, H. K., & Lyytinen, K. (1996) · Accounting, Management and Information Technologies · doi:10.1016/0959-8022(96)00004-5 · Cited by 295
Computer algorithms for plagiarism detection
Parker, A., & Hamblen, J. O. (1989) · IEEE Transactions on Education · doi:10.1109/13.28038 · Cited by 216
JPlag: finding plagiarisms among a set of programs
Prechelt, L., Malpohl, G., & Philippsen, M. (2000) · Karlsruhe · doi:10.5445/ir/542000 · Cited by 144
“[3, 7], others rely on structure comparison alone.”
Source-code Similarity Detection and Detection Tools Used in Academia: A Systematic Review
Novak, M., Joy, M., & Kermek, D. (2019) · ACM Transactions on Computing Education · doi:10.1145/3313290 · Cited by 117
Sim: a utility for detecting similarity in computer programs
Gitchell, D., & Tran, N. (1999) · ACM SIGCSE Bulletin · doi:10.1145/384266.299783 · Cited by 62
Metadata
- Authors
- Jankowitz, H. T.
- Venue
- The Computer Journal
- Publisher
- Oxford University Press (OUP)
- Published
- 1988-01-01
- Volume
- 31
- Issue
- 1
- Pages
- 1-8
- ISSN
- 0010-4620 (ISSN-L)
- 1460-2067
- OpenAlex
- W1997953464
- Cited by
- 89
- References
- 0
- FWCI
- 6.73
- Type
- journal article
- Language
- en
- Open access
- closed
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review
Data sources
Bibliographic data: Semantic Scholar, OpenAlex, Crossref.
Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).
Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.