Predicting bug-fixing time: An empirical study of commercial software projects
Authors:
- 1 May 2013
- conference paper
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- No. 02705257,p. 1042-1051
Abstract
For a large and evolving software system, the project team could receive many bug reports over a long period of time. It is important to achieve a quantitative understanding of bug-fixing time. The ability to predict bug-fixing time can help a project team better estimate software maintenance efforts and better manage software projects. In this paper, we perform an empirical study of bug-fixing time for three CA Technologies projects. We propose a Markov-based method for predicting the number of bugs that will be fixed in future. For a given number of defects, we propose a method for estimating the total amount of time required to fix them based on the empirical distribution of bug-fixing time derived from historical data. For a given bug report, we can also construct a classification model to predict slow or quick fix (e.g., below or above a time threshold). We evaluate our methods using real maintenance data from three CA Technologies projects. The results show that the proposed methods are effective.Keywords
This publication has 21 references indexed in Scilit:
- A study of term weighting schemes using class information for text classification2012
- Studying the fix-time for bugs in large open source projects2011
- "Not my bug!" and other reasons for software bug report reassignments2011
- Classifying Software Changes: Clean or Buggy?IEEE Transactions on Software Engineering, 2008
- Predicting Eclipse Bug Lifetimes2007
- Data Mining Static Code Attributes to Learn Defect PredictorsIEEE Transactions on Software Engineering, 2006
- How long did it take to fix bugs?2006
- Life cycle of Defects in Open Source Software Projects2006
- Understanding and predicting effort in software projects2003
- Two case studies of open source software developmentACM Transactions on Software Engineering and Methodology, 2002