Academic Papers

• T. L. Graves, A. F. Karr, J. S. Marron and H. Siy, “Predicting fault incidence using software change history,” in IEEE Transactions on Software Engineering, vol. 26, no. 7, pp. 653-661, July 2000, doi: 10.1109/32.859533.
• Keisuke Hotta, Yui Sasaki, Yukiko Sano, Yoshiki Higo, and Shinji Kusumoto. 2012. An empirical study on the impact of duplicate code. Adv. Soft. Eng. 2012, Article 5 (January 2012), 1 pages. https://doi.org/10.1155/2012/938296
• Thomas J. Ostrand, Elaine J. Weyuker, and Robert M. Bell. 2004. Where the bugs are. In Proceedings of the 2004 ACM SIGSOFT international symposium on Software testing and analysis (ISSTA ‘04). Association for Computing Machinery, New York, NY, USA, 86–96. https://doi.org/10.1145/1007512.1007524
• M. D’Ambros, M. Lanza and R. Robbes, “On the Relationship Between Change Coupling and Software Defects,” 2009 16th Working Conference on Reverse Engineering, 2009, pp. 135-144, doi: 10.1109/WCRE.2009.19.
• Christian Bird, Nachiappan Nagappan, Brendan Murphy, Harald Gall, and Premkumar Devanbu. 2011. Don’t touch my code! examining the effects of ownership on software quality. In Proceedings of the 19th ACM SIGSOFT symposium and the 13th European conference on Foundations of software engineering(ESEC/FSE ‘11). Association for Computing Machinery, New York, NY, USA, 4–14. https://doi.org/10.1145/2025113.2025119