Where Should We Fix This Bug? A Two-Phase Recommendation Model
Authors:
- 21 May 2013
- journal article
- Published by Institute of Electrical and Electronics Engineers (IEEE) in IEEE Transactions on Software Engineering
- Vol. 39 (11) , 1597-1610
Abstract
To support developers in debugging and locating bugs, we propose a two-phase prediction model that uses bug reports' contents to suggest the files likely to be fixed. In the first phase, our model checks whether the given bug report contains sufficient information for prediction. If so, the model proceeds to predict files to be fixed, based on the content of the bug report. In other words, our two-phase model "speaks up" only if it is confident of making a suggestion for the given bug report; otherwise, it remains silent. In the evaluation on the Mozilla "Firefox" and "Core" packages, the two-phase model was able to make predictions for almost half of all bug reports; on average, 70 percent of these predictions pointed to the correct files. In addition, we compared the two-phase model with three other prediction models: the Usual Suspects, the one-phase model, and BugScout. The two-phase model manifests the best prediction performance.Keywords
This publication has 65 references indexed in Scilit:
- The missing links2010
- What Makes a Good Bug Report?IEEE Transactions on Software Engineering, 2010
- Do stack traces help developers fix bugs?2010
- Improving bug triage with bug tossing graphs2009
- Predicting Faults from Cached History29th International Conference on Software Engineering (ICSE'07), 2007
- The top ten list: dynamic fault prediction2005
- The necessity of assuring quality in software measurement data2004
- Detection of software modules with high debug code churn in a very large legacy system2002
- Multiple Comparisons among MeansJournal of the American Statistical Association, 1961
- On a Test of Whether one of Two Random Variables is Stochastically Larger than the OtherThe Annals of Mathematical Statistics, 1947