Does bug prediction support human developers? Findings from a Google case study
Authors:
- 1 May 2013
- conference paper
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- No. 02705257,p. 372-381
Abstract
While many bug prediction algorithms have been developed by academia, they're often only tested and verified in the lab using automated means. We do not have a strong idea about whether such algorithms are useful to guide human developers. We deployed a bug prediction algorithm across Google, and found no identifiable change in developer behavior. Using our experience, we provide several characteristics that bug prediction algorithms need to meet in order to be accepted by human developers and truly change how developers evaluate their code.Keywords
This publication has 17 references indexed in Scilit:
- The code orb2011
- Using Static Analysis to Find BugsIEEE Software, 2008
- A report on a survey and study of static analysis users2008
- Toward Reducing Fault Fix Time: Understanding Developer Behavior for the Design of Automated Fault Detection Tools2007
- Evaluating static analysis defect warnings on production software2007
- Predicting Faults from Cached History29th International Conference on Software Engineering (ICSE'07), 2007
- Mining metrics to predict component failures2006
- Finding bugs is easy2004
- A validation of object-oriented design metrics as quality indicatorsIEEE Transactions on Software Engineering, 1996
- Usability inspection methods1994