Late propagation in software clones

IEEE International Conference on Software Maintenance, ICSM

Volumn , Issue , 2011, Pages 273-282

  Barbour, Liliane ^a   Khomh, Foutse ^a   Zou, Ying ^a  

^a QUEEN S UNIVERSITY   (Canada)

Author keywords

clone genealogies; fault proneness; late propagation

Indexed keywords

CLONE DETECTION; CLONE GENEALOGIES; CODE SEGMENTS; EVOLUTION HISTORY; FAULT-PRONENESS; SOFTWARE CLONES; SOFTWARE SYSTEMS;

CODES (SYMBOLS); COMPUTER SOFTWARE; COMPUTER SOFTWARE MAINTENANCE; CRACK PROPAGATION; SYNCHRONIZATION;

CLONING;

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

References (17)

1. M. Kim, V. Sazawal, D. Notkin, and G. Murphy, "An empirical study of code clone genealogies," in Proceedings of the 10th European software engineering conference held jointly with 13th ACM SIGSOFT international symposium on Foundations of software engineering, ser. ESEC/FSE-13. New York, NY, USA: ACM, 2005, pp. 187-196.
2. L. Aversano, L. Cerulo, and M. Di Penta, "How clones are maintained: An empirical study," in 11th European Conference on Software Maintenance and Reengineering, 2007, pp. 81-90.
3. S. Thummalapenta, L. Cerulo, L. Aversano, and M. Di Penta, "An empirical study on the maintenance of source code clones," Empirical Software Engineering, vol. 15, pp. 1-34, 2010.
4. N. Göde, "Evolution of type-1 clones," in Proceedings of the 9th International Working Conference on Source Code Analysis and Manipulation. IEEE Computer Society, 2009, pp. 77-86.
5. J. Krinke, "A study of consistent and inconsistent changes to code clones," Working Conference on Reverse Engineering, vol. 0, pp. 170-178, 2007.
6. N. Göde and J. Harder, "Clone stability," in 15th European Conference on Software Maintenance and Reengineering, May 2011.
7. J. Krinke, "Is cloned code more stable than non-cloned code?"IEEE International Workshop on Source Code Analysis and Manipulation, pp. 57-66, 2008.
8. N. Göde and R. Koschke, "Frequency and risks of changes to clones," in 33rd International Conference on Software Engineering, May 2011.
9. T. Kamiya, S. Kusumoto, and K. Inoue, "Ccfinder: A multi-linguistic token-based code clone detection system for large scale source code," IEEE Transactions on Software Engineering, vol. 28, pp. 654-670, 2002.
10. W. Shang, Z. M. Jiang, B. Adams, and A. Hassan, "Mapreduce as a general framework to support research in mining software repositories (msr)," in 6th IEEE International Working Conference on Mining Software Repositories, May 2009, pp. 21-30.
11. A. Mockus and L. Votta, "Identifying reasons for software changes using historic databases," in Proceedings. International Conference on Software Maintenance, 2000.
12. E. Shihab, A. Ihara, Y. Kamei, W. Ibrahim, M. Ohira, B. Adams, A. Hassan, and K. Matsumoto, "Predicting reopened bugs: A case study on the eclipse project," in Reverse Engineering (WCRE), 2010 17th Working Conference on, 2010, pp. 249-258.
13. A. Hassan, "Predicting faults using the complexity of code changes," in Software Engineering, 2009. ICSE 2009. IEEE 31st International Conference on, May 2009, pp. 78-88.
14. G. M. Selim, L. Barbour, W. Shang, B. Adams, A. E. Hassan, and Y. Zou, "Studying the impact of clones on software defects," Working Conference on Reverse Engineering, pp. 13-21, 2010.
15. D. Sheskin, Handbook of Parametric and Nonparametric Statistical Procedures (fourth edition). Chapman & All, 2007.
16. R. K. Yin, Case Study Research: Design and Methods - Third Edition, 3rd ed. SAGE Publications, 2002.
17. A. E. Hassan and R. C. Holt, "Studying the evolution of software systems using evolutionary code extractors," in Proceedings of the 7th International Workshop on Principles of Software Evolution. Washington, DC, USA: IEEE Computer Society, 2004, pp. 76-81.