Managing code clones using dynamic change tracking and resolution?

IEEE International Conference on Software Maintenance, ICSM

Volumn , Issue , 2009, Pages 169-178

  Wit, Michiel De ^a   Zaidman, Andy ^a   Deursen, Arie Van ^a  

^a DELFT UNIVERSITY OF TECHNOLOGY   (Netherlands)

Author keywords

[No Author keywords available]

Indexed keywords

ADDED VALUES; CLONE DETECTION; CLONE MANAGEMENT; CODE CLONE; CODE CLONING; DYNAMIC CHANGES; PLUG-INS; RESOLUTION STRATEGY; SOURCE CODES; USER STUDY;

COMPUTER SOFTWARE; COMPUTER SOFTWARE MAINTENANCE; MAINTAINABILITY;

CLONING;

EID: 70849100995     PISSN: None     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1109/ICSM.2009.5306336     Document Type: Conference Paper

References (28)

1. L. Aversano, L. Cerulo, and M. Di Penta. How clones are maintained: An empirical study. In Conf. Softw. Maintenance and Reengineering (CSMR), pages 81-90. IEEE, 2007.
2. E. Babbie. The practice of social research. Wadsworth Belmont, 11th edition, 2007.
3. B. Baker. On finding duplication and near-duplication in large software systems. In Proc. Working Conference on Reverse Engineering (WCRE), pages 86-95. IEEE, 1995.
4. M. Balazinska, E. Merlo, M. Dagenais, B. Lague, and K. Kontogiannis. Measuring clone based reengineering opportunities. In Proc. of the Int'l Symposium on Software Metrics (METRICS), page 292. IEEE, 1999.
5. H. A. Basit and S. Jarzabek. Efficient token based clone detection with flexible tokenization. In Proc. of the the joint meeting of the European Software Engineering Conference and the symposium on the Foundations of Software Engineering (ESEC/FSE), pages 513-516. ACM, 2007.
6. I. Baxter, A. Yahin, L. Moura, M. Sant'Anna, and L. Bier. Clone detection using abstract syntax trees. In Int'l Conf. on Software Maintenance (ICSM), pages 368-377. IEEE, 1998.
7. S. Bellon, R. Koschke, G. Antoniol, J. Krinke, and E. Merlo. Comparison and evaluation of clone detection tools. Transactions on Software Engineering, 33(9):577-591, 2007.
8. M. Bruntink, A. van Deursen, R. van Engelen, and T. Tourwè. On the use of clone detection for identifying crosscutting concern code. Transactions on Software Engineering, 31(10):804-818, 2005.
9. D. Campbell, J. Stanley, and N. Gage. Experimental and quasi-experimental designs for research. Rand McNally Chicago, 1963.
10. A. Chiu and D. Hirtle. Beyond clone detection. Technical report, University of Waterloo, 2007.
11. M. de Wit. Managing clones using dynamic change tracking and resolution. Master's thesis, Software Engineering Research Group, Delft University of Technology, 2009.
12. E. Duala-Ekoko and M. Robillard. Clonetracker: Tool support for code clone management. In Proc. Int'l Conf. on Software Engineering (ICSE), pages 843-846. ACM, 2008.
13. R. Fanta and V. Rajlich. Removing clones from the code. Journal of Software Maintenance, 11(4):223-243, 1999.
14. P. Jablonski and D. Hou. CReN: a tool for tracking copy and paste code clones and renaming identifiers consistently in the IDE. In Proc. of the OOPSLA workshop on Eclipse technology eXchange, pages 16-20. ACM, 2007.
15. J. H. Johnson. Identifying redundancy in source code using fingerprints. In Proceedings of the conference of the Centre for Advanced Studies on Collaborative research (CASCON), pages 171-183. IBM Press, 1993.
16. T. Kamiya, S. Kusumoto, and K. Inoue. CCFinder: A multilinguistic token-based code clone detection system for large scale source code. Transactions on Software Engineering, 28(7):654-670, 2002.
17. C. Kapser and M. Godfrey. "Cloning Considered Harmful" considered harmful. In Proc. Working Conference on Reverse Engineering (WCRE), pages 19-28. IEEE, 2006.
18. M. Kim, L. Bergman, T. Lau, and D. Notkin. An ethnographic study of copy and paste programming practices in OOPL. In Proc. of the Int'l Symposium on Empirical Software Engineering (ISESE), pages 83-92. IEEE, 2004.
19. M. Kim, V. Sazawal, D. Notkin, and G. Murphy. An empirical study of code clone genealogies. SIGSOFT Softw. Eng. Notes, 30(5):187-196, 2005.
20. R. Komondoor and S. Horwitz. Using slicing to identify duplication in source code. In Proc. of the Int'l Symposium on Static Analysis (SAS), pages 40-56. Springer-Verlag, 2001.
21. R. Koschke. Identifying and removing software clones. In Software Evolution, chapter 2, pages 15-36. Springer, 2008.
22. J. Krinke. Is cloned code more stable than non-cloned code? In Proc. of the Int'l Working Conf. on Source Code Analysis and Manipulation (SCAM), pages 57-66. IEEE, Sept. 2008.
23. T. LaToza, G. Venolia, and R. DeLine. Maintaining mental models: a study of developer work habits. In Int'l Conf. Softw. Engineering (ICSE), pages 492-501. ACM, 2006.
24. A. Lozano and M. Wermelinger. Assessing the effect of clones on changeability. In Proc. Int'l Conference on Software Maintenance (ICSM), pages 227-236. IEEE, 2008.
25. Z. Mann. Three public enemies: cut, copy, and paste. Computer, 39(7):31-35, 2006.
26. P. Tarr, H. Ossher, W. Harrison, and S. Sutton. N degrees of separation: multi-dimensional separation of concerns. In Int'l Conf. Software Engineering (ICSE), pages 107-119. ACM, 1999.
27. M. Toomim, A. Begel, and S. L. Graham. Managing duplicated code with linked editing. In Proc. of the Symposium on Visual Languages Human Centric Computing (VLHCC), pages 173-180. IEEE, 2004.
28. V.Weckerle. Cpc an eclipse framework for automated clone life cycle tracking and update anomaly detection. Master's thesis, Freie Universität Berlin, January 2008.