Cited by 222Software Engineering ResearchAdvanced Software Engineering MethodologiesSoftware Engineering Techniques and Practices

Tracking Code Clones in Evolving Software

Duala-Ekoko, Ekwa, Robillard, Martin P.·2007·29th International Conference on Software Engineering (ICSE'07)

Abstract

Code clones are generally considered harmful in software development, and the predominant approach is to try to eliminate them through refactoring. However, recent research has provided evidence that it may not always be practical, feasible, or cost-effective to eliminate certain clone groups. We propose a technique for tracking clones in evolving software. Our technique relies on the concept of abstract clone region descriptors (CRD), which describe clone regions within methods in a robust way that is independent from the exact text of the clone region or its location in a file. We present our definition of CRDs, and describe a complete clone tracking system capable of producing CRDs from the output of a clone detection tool, notify developers of modifications to clone regions, and support the simultaneous editing of clone regions. We report on two experiments and a case study conducted to assess the performance and usefulness of our approach.

Integrity signals

Registry

Crossref · 10.1109/icse.2007.90

Cites

25 of 25 references verified0 citation errors · 0 not checkable

Statistics

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

Claims the paper makes

This paper’s full text isn’t openly available, 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?

  • MCIDiff and CloneTracker consider the possible set of clones, show the length and the number of instances of all code clones, not just nearby ones, to help the developer predict E(Cw) of handling any or all of these clones.

    “These two clone-tracking tools consider the possible set of clones, show the length and the number of instances of all code clones, not just nearby ones, to help the developer predict E(C w ) of handing any or all of these clones.”

Cites

Flagged first, then by citations

2 of the 27 references couldn’t be matched to a known paper.

Cited by

Sorted by citations

Authors
Duala-Ekoko, E., & Robillard, M. P.
Affiliations
McGill University (CA)
Venue
29th International Conference on Software Engineering (ICSE'07)
Publisher
IEEE
Published
2007-05
Pages
158-167
ISSN
0270-5257 (ISSN-L)
OpenAlex
W2145544369
Cited by
222
References
27
Citations by year
2026: 1 · 2025: 2 · 2024: 5 · 2023: 6 · 2022: 3 · 2021: 9 · 2020: 9 · 2019: 12 · 2018: 10 · 2017: 6 · 2016: 14 · 2015: 16 · 2014: 13 · 2013: 18 · 2012: 14
FWCI
16.47
Type
conference paper
Language
en
Open access
closed
Locations
ACM/IEEE International Conference on Software Engineering: Companion Proceedings (ICSE-Companion) (publishedVersion)
Funders
Natural Sciences and Engineering Research Council of Canada
Topics
  • Physical Sciences › Computer Science › Information Systems › Software Engineering Research
  • Physical Sciences › Computer Science › Artificial Intelligence › Advanced Software Engineering Methodologies
  • Physical Sciences › Computer Science › Information Systems › Software Engineering Techniques and Practices
Keywords
code clones, clone detection, evolving software, software maintenance, refactoring

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