Code "clones" are similar segments of code that are frequently introduced by "scavenging" existing code, that is, reusing code by copying it and adapting it for a new use. In order to scavenge the code, the developer must be aware of it already, or must find it. Little is known about how tools - particularly search tools - impact the clone construction process, nor how developers use them for this purpose. This paper lists five outstanding research questions in this area and proposes sketches of designs for five empirical studies that might be conducted to help shed light on those questions.
@InProceedings{dean_et_al:DagSemProc.06301.5, author = {Dean, Thomas R. and Di Penta, Massamiliano and Kontogiannis, Kostas and Walenstein, Andrew}, title = {{Clone Detector Use Questions: A List of Desirable Empirical Studies}}, booktitle = {Duplication, Redundancy, and Similarity in Software}, pages = {1--5}, series = {Dagstuhl Seminar Proceedings (DagSemProc)}, ISSN = {1862-4405}, year = {2007}, volume = {6301}, editor = {Rainer Koschke and Ettore Merlo and Andrew Walenstein}, publisher = {Schloss Dagstuhl -- Leibniz-Zentrum f{\"u}r Informatik}, address = {Dagstuhl, Germany}, URL = {https://drops.dagstuhl.de/entities/document/10.4230/DagSemProc.06301.5}, URN = {urn:nbn:de:0030-drops-9695}, doi = {10.4230/DagSemProc.06301.5}, annote = {Keywords: Code clone, clone detector, code search, reuse, code scavenging, empirical study} }
Feedback for Dagstuhl Publishing