An industrial study on the risk of software changes

Proceedings of the ACM SIGSOFT 20th International Symposium on the Foundations of Software Engineering, FSE 2012

Volumn , Issue , 2012, Pages

  Shihab, Emad ^a   Hassan, Ahmed E ^a   Adams, Bram ^b   Jiang, Zhen Ming ^c  

^a QUEEN S UNIVERSITY   (Canada)

^b ÉCOLE POLYTECHNIQUE DE MONTRÉAL   (Canada)

^c RESEARCH IN MOTION   (Canada)

Author keywords

bug inducing changes; change metrics; change risk; code metrics

Indexed keywords

BUG INDUCING CHANGES; BUG REPORTS; CHANGE METRICS; CODE METRICS; DESIGN CHANGE; DESIGN REVIEWING; PRECISION IMPROVEMENT; RANDOM MODEL; SOFTWARE CHANGE; SOFTWARE PROJECT;

PROGRAM DEBUGGING; RISK MANAGEMENT; SOFTWARE ENGINEERING;

RISKS;

EID: 84871276203     PISSN: None     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1145/2393596.2393670     Document Type: Conference Paper

References (35)

1. Erik Arisholm and Lionel C. Briand. Predicting fault-prone components in a Java legacy system. In ISESE '06: Proceedings of International Symposium on Empirical Software Engineering, pages 8-17, 2006.
2. Victor R. Basili, Lionel C. Briand, and Walcélio L. Melo. A validation of object-oriented design metrics as quality indicators. IEEE Trans. Softw. Eng., 22(10):751-761, 1996.
3. Nicolas Bettenburg and Ahmed E. Hassan. Studying the impact of social structures on software quality. In Proc. Int'l Conf. on Program Comprehension, pages 124-133, 2010.
4. Nicolas Bettenburg, Sascha Just, Adrian Schröter, Cathrin Weiss, Rahul Premraj, and Thomas Zimmermann. What makes a good bug report? In Proceedings of Intĺ Sym. on Foundations of Software Engineering, pages 308-318, 2008.
5. Christian Bird, Nachiappan Nagappan, Brendan Murphy, Harald Gall, and Premkumar Devanbu. Don't touch my code!: examining the effects of ownership on software quality. In Proceedings of Sym. and European Conf. on Foundations of Software Engineering, pages 4-14, 2011.
6. Barry W. Boehm. Software risk management: Principles and practices. IEEE Softw., 8(1):32-41, January 1991.
7. Marcelo Cataldo, Audris Mockus, Jeffrey A. Roberts, and James D. Herbsleb. Software dependencies, work dependencies, and their impact on failures. IEEE Trans. on Softw. Eng., 99(6):864-878, 2009.
8. S. R. Chidamber and C. F. Kemerer. A metrics suite for object oriented design. IEEE Trans. Softw. Eng., 20(6):476-493, 1994.
9. Jacek Czerwonka, Rajiv Das, Nachiappan Nagappan, Alex Tarvo, and Alex Teterev. Crane: Failure prediction, change analysis and test prioritization in practice - experiences from windows. In Proceedings of Intĺ Conf. on Software Testing, Verification and Validation, pages 357-366, 2011.
10. F. M. Dedolph. The neglected management activity: Software risk management. Bell Labs Tech. Journal, 8(3):91-95, 2003.
11. Bradley Efron. Estimating the error rate of a prediction rule: Improvement on Cross-Validation. Journal of the American Statistical Association, 78(382):316-331, 1983.
12. Jon Eyolfson, Lin Tan, and Patrick Lam. Do time of day and developer experience affect commit bugginess. In Proceeding of Working Conf. on Mining Software Repositories, pages 153-162, 2011.
13. Bernd Freimut, Susanne Hartkopf, Peter Kaiser, Jyrki Kontio, and Werner Kobitzsch. An industrial case study of implementing software risk management. In Proc. of European Software Engineering Conf. and Intĺ Sym. on Foundations of Software Engineering, pages 277-287, 2001.
14. Kehan Gao, Taghi M. Khoshgoftaar, Huanjing Wang, and Naeem Seliya. Choosing software metrics for defect prediction: an investigation on feature selection techniques. Softw. Pract. Exper., 41:579-606, April 2011.
15. T. L. Graves, A. F. Karr, J. S. Marron, and H. Siy. Predicting fault incidence using software change history. IEEE Trans. of Softw. Eng., 26(7):653-661, July 2000.
16. M A Hall and L A Smith. Practical feature subset selection for machine learning. Computer Science, 98:181-191, 1998.
17. Tracy Hall, Sarah Beecham, David Bowes, David Gray, and Steve Counsell. A systematic review of fault prediction performance in software engineering. IEEE Trans. on Softw. Eng., 99, 2011.
18. Ahmed E. Hassan. Predicting faults using the complexity of code changes. In Proceedings of Intĺ Conference on Software Engineering, pages 78-88, 2009.
19. Israel Herraiz, Jesus M. Gonzalez-Barahona, and Gregorio Robles. Towards a theoretical model for software growth. In MSR '07: Proceedings of the Fourth International Workshop on Mining Software Repositories, page 21, 2007.
20. Sunghun Kim, E. James Whitehead, Jr., and Yi Zhang. Classifying software changes: Clean or buggy? IEEE Trans. Softw. Eng., 34(2):181-196, 2008.
21. Marek Leszak, Dewayne E. Perry, and Dieter Stoll. Classification and evaluation of defects in a project retrospective. J. Syst. Softw., 61(3):173-187, 2002.
22. Thomas J. McCabe. A complexity measure. In ICSE '76: Proceedings of the 2nd international conference on Software engineering, page 407, 1976.
23. J.A. Miccolis, K. Hively, and B.W. Merkley. Enterprise Risk Management: Trends and Emerging Practices. Institute of Internal Auditors Research Foundation, 2001.
24. Audris Mockus. Organizational volatility and its effects on software defects. In Proceedings of Intĺ Sym. on Foundations of Software Engineering, pages 117-126, 2010.
25. Audris Mockus and David M. Weiss. Predicting risk of software changes. Bell Labs Technical Journal, 5(2):169-180, 2000.
26. Raimund Moser, Witold Pedrycz, and Giancarlo Succi. A comparative analysis of the efficiency of change metrics and static code attributes for defect prediction. In Proceedings of Intĺ Conf. on Software Engineering, pages 181-190, 2008.
27. Nachiappan Nagappan and Thomas Ball. Static analysis tools as early indicators of pre-release defect density. In ICSE '05: Proceedings of the 27th international conference on Software engineering, pages 580-586, 2005.
28. Nachiappan Nagappan and Thomas Ball. Use of relative code churn measures to predict system defect density. In ICSE '05: Proceedings of the 27th international conference on Software engineering, pages 284-292, 2005.
29. Niclas Ohlsson and Hans Alberg. Predicting fault-prone software modules in telephone switches. IEEE Trans. Softw. Eng., 22(12):886-894, 1996.
30. I Ozkaya, P. Kruchten, R. Nord, and N. Brown. Second international workshop on managing technical debt, 2011.
31. Teade Punter, Marcus Ciolkowski, Bernd Freimut, and Isabel John. Conducting on-line surveys in software engineering. In Proceedings of Intĺ Sym. on Empirical Software Engineering, pages 80-88, 2003.
32. Peter C. Rigby, Daniel M. German, and Margaret-Anne Storey. Open source software peer review practices: A case study of the apache server. In Proceedings of Intĺ Conf. on Software Engineering, pages 541-550, 2008.
33. Jacek Śliwerski, Thomas Zimmermann, and Andreas Zeller. When do changes induce fixes? In Proceedings of Intĺ Workshop on Mining Software Repositories, pages 1-5, 2005.
34. Zuoning Yin, Ding Yuan, Yuanyuan Zhou, Shankar Pasupathy, and Lakshmi Bairavasundaram. How do fixes become bugs? In Proceedings of Sym. and European Conf. on Foundations of Software Engineering, pages 26-36, 2011.
35. Thomas Zimmermann, Rahul Premraj, and Andreas Zeller. Predicting defects for Eclipse. In Proceedings of Intĺ Workshop on Predictor Models in Software Engineering, pages 9-15, 2007.