Cited by 198Academic integrity and plagiarismSoftware Engineering ResearchTeaching and Learning Programming

An empirical approach for detecting program similarity and plagiarism within a university programming environment

Faidhi, J.A.W., Robinson, S.K.·1987·Computers & Education

Integrity signals

Registry

Crossref · 10.1016/0360-1315(87)90042-x

Cites

1 of 1 references verified0 citation errors · 0 not checkable

Statistics

Recomputing p-values needs the paper’s full text.

Claims the paper makes

We couldn’t retrieve this paper’s full text, so its claims and self-check weren’t run. The registry and citation checks still apply.

Claims other papers make about this one

Each is checked against this paper’s own text: does it say what the citing paper says it does?

  • Plagiarism-hiding transformations are usually cosmetic: they alter source code appearance and structure while preserving the original program's behaviour.

    “Such source code transformations are typically cosmetic in nature, in that they change the appearance and structure of the source code [6], [7], [10], but retain the original behaviour of the plagiarised assignment.”
  • Faidhi and Robinson's taxonomy classifies plagiarism-hiding source code transformations into six levels.

    “This taxonomy categorises transformations into six levels: L1) Changes to comments and indentation.L2) Changes to identifiers.L3) Changes in declarations (e.g.declaring extra constants, changing the order of functions and variables).L4) Modifying functions (e.g.modifying signature, merging and creating new functions).L5) Changing program statements to semantic equivalents (e.g. for to while, if to”

    From Academic Source Code Plagiarism Detection by Measuring Program Behavioral Similarity (2021) · cites this paper as Faidhi and Robinson [10]

  • Structural transformations alter source code appearance and structure but not behaviour.

    “Such transformations modify the appearance and structure of source code, but not behaviour.”
  • Structural transformations correspond to L3 and higher transformations in Faidhi and Robinson's taxonomy.

    “Structural transformations are equivalent to L3+ transformations from Faidhi and Robinson's [10] taxonomy.”
  • All implemented source code transformations are referenced from prior literature and conform to the first 5 levels of Faidhi and Robinson's transformation taxonomy.

    “To ensure the generated programs are representative of undergraduate plagiarism, all implemented source code transformations (listed in table 4) are referenced from prior literature [7], [10], [50], [51], and conform to the first 5 levels of Faidhi and Robinson's [10] transformation taxonomy.”

Cites

Flagged first, then by citations

Cited by

Sorted by citations

Authors
Faidhi, J. A. W., & Robinson, S. K.
Venue
Computers & Education
Publisher
Elsevier BV
Published
1987-01
Volume
11
Issue
1
Pages
11-19
ISSN
0360-1315 (ISSN-L)
OpenAlex
W1971922616
Cited by
198
References
1
Citations by year
2026: 2 · 2025: 5 · 2024: 6 · 2023: 7 · 2022: 11 · 2021: 16 · 2020: 13 · 2019: 15 · 2018: 11 · 2017: 7 · 2016: 10 · 2015: 6 · 2014: 9 · 2013: 6 · 2012: 17
FWCI
5.76
Type
journal article
Language
en
Open access
closed
Locations
Computers & Education (publishedVersion)
Topics
  • Social Sciences › Safety Research › Academic integrity and plagiarism
  • Physical Sciences › Computer Science › Information Systems › Software Engineering Research
  • Physical Sciences › Computer Science › Computer Science Applications › Teaching and Learning Programming
Keywords
plagiarism detection, code similarity, source code plagiarism, programming education

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