How Developers Copy
Authors:
- 1 January 2006
- conference paper
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- p. 56-68
Abstract
Copy-paste programming is dangerous as it may lead to hidden dependencies between different parts of the system. Modifying clones is not always straight forward, because we might not know all the places that need modification. This is even more of a problem when several developers need to know about how to change the clones. In this paper, we correlate the code clones with the time of the modification and with the developer that performed the modification to detect patterns of how developers copy from one another. We develop a visualization, named Clone Evolution View, to represent the evolution of the duplicated code. We show the relevance of our approach on several large case studies and we distill our experience in forms of interesting copy patternsKeywords
This publication has 13 references indexed in Scilit:
- CVSscan2005
- Insights into system-wide code duplication2005
- Archeology of code duplication: recovering duplication chains from small duplication fragments2005
- Hipikat: recommending pertinent software development artifacts2003
- Clone detection using abstract syntax trees2002
- CCFinder: a multilinguistic token-based code clone detection system for large scale source codeIEEE Transactions on Software Engineering, 2002
- Visualizing software changesIEEE Transactions on Software Engineering, 2002
- Assessing the benefits of incorporating function clone detection in a development process1997
- Experiment on the automatic detection of function clones in a software system using metrics1996
- Substring matching for clone detection and change tracking1994