An automatic framework for extracting and classifying near-miss clone genealogies

IEEE International Conference on Software Maintenance, ICSM

Volumn , Issue , 2011, Pages 293-302

  Saha, Ripon K ^a   Roy, Chanchal K ^a   Schneider, Kevin A ^a  

^a UNIVERSITY OF SASKATCHEWAN   (Canada)

Author keywords

clone evolution; clone genealogy extractor; mapping

Indexed keywords

ASSOCIATED TOOL; CHANGE PATTERNS; CLONE DETECTION; CLONE EVOLUTION; CLONE GENEALOGY EXTRACTOR; CODE CLONE; LINUX KERNEL; OPEN SOURCE PROJECTS; PRECISION AND RECALL; SIMILARITY FACTORS;

CODES (SYMBOLS); COMPUTER OPERATING SYSTEMS; COMPUTER SOFTWARE MAINTENANCE; HISTORY; MAPPING;

CLONING;

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

References (24)

1. L. Aversano, L. Cerulo, and M. D. Penta, "How clones are maintained: An empirical study," Proc. CSMR, 2007, pp. 81-90.
2. T. Bakota, R. Ferenc, and T. Gyimothy, "Clone smells in software evolution," Proc. ICSM, 2007, pp. 24-33.
3. N. Bettenburg, W. Shang, W. Ibrahim, B. Adams, Y. Zou, and A. Hassan, "An empirical study on inconsistent changes to code clones at release level," Proc. WCRE, 2009, pp. 85-94.
4. J. Cordy, "The TXL source transformation language," Sci. of Com. Prog., 61(3):190-210, 2006.
5. E. Duala-Ekoko and M. P. Robillard, "Clone Region Descriptors: Representing and Tracking Duplication in Source Code," TOSEM, 20(1)3:1-31, 2010.
6. N. Göde and R. Koschke, "Studying clone evolution using incremental clone detection," JSME, 2010.
7. M. Godfrey and L. Zou, "Using origin analysis to detect merging and splitting of source code," entities. IEEE TSE, 31(2):166-181, 2005. (Pubitemid 40556104)
8. J. Harder and N. Göde, "Efficiently Handling Clone Data: RCF and cyclone," Proc. IWSC, 2011, pp. 81-82.
9. J. Harder and N. Göde, "Modeling clone evolution," Proc. IWSC, 2009, pp. 17-21.
10. M. Kim, V. Sazawal, D. Notkin, and G. C. Murphy, "An empirical study of code clone genealogies," Proc. ESEC-FSE, 2005, pp. 187-196.
11. S. Kim, K. Pan, and J. E. Whitehead, "When functions change their names: Automatic detection of origin relationships," Proc. WCRE, 2005, pp. 143-152.
12. J. Krinke, "A study of consistent and inconsistent changes to code clones," Proc. WCRE, 2007, pp. 170-178.
13. J. Krinke, "Is cloned code more stable than non-cloned code?," Proc. SCAM, 2008, pp. 57-66.
14. A. Lozano and M. Wermelinger, "Tracking clones imprint," Proc. IWSC, 2010, pp. 65-72.
15. T. T. Nguyen, H. A. Nguyen, J. M. Al-Kofahi, N. H. Pham, and T. N. Nguyen, "Scalable and Incremental Clone Detection for Evolving Software," Proc. ICSM, 2009, pp. 491-494.
16. F. Rahman, C. Bird, P. Devanbu, "Clones: What is that smell?," Proc. MSR, 2010, pp. 72-81.
17. C. K. Roy and J. R. Cordy, "A mutation / injection-based automatic framework for evaluating code clone detection tools," Proc. Mutation, 2009, pp. 157-166.
18. C. K. Roy and J. R. Cordy, "NICAD: Accurate Detection of Near-Miss Intentional Clones Using Flexible Pretty-Printing and Code Normalization, "In ICPC, 2008, pp. 172-181.
19. C. K. Roy and J. R. Cordy, "Near-miss Function Clones in Open Source Software: An Empirical Study," JSME, 22(3):165-189, 2010.
20. R. K. Saha, M. Asaduzzaman, M. F. Zibran, C. K. Roy, and K. A. Schneider, "Evaluating code clone genealogies at release level: An empirical study," Proc. SCAM, 2010, pp. 87-96.
21. Software Clones. http://www.softwareclones.org/ (Feb 2011)
22. S. Thummalapenta, L. Cerulo, L. Aversano, and M. D. Penta, "An empirical study on the maintenance of source code clones," ESE, 15(1):1-34, 2009.
23. A. T. T. Ying, G. C. Murphy, R. Ng, and M. C. Chu-Carroll, "Predicting source code changes by mining change history," IEEE TSE, 30(9):574-586, 2004.
24. T. Zimmermann, P. Weigerber, S. Diehl, and A. Zeller, "Mining version histories to guide software changes," IEEE TSE, 31(6):429-445, 2005. (Pubitemid 41245067)