Bug Report Quality Evaluation Considering the Effect of Submitter Reputation

The quality of a bug report is a very crucial aspect that influences the entire software life cycle. Generally, in many software projects relevant lack of information can be observed when submitting a bug report. Consequently, the time resolution of a software problem is strongly influenced by the quality of the reporting. In this paper, we investigate the quality of bug reports from the perspective of developers. We examined several metrics impacting the quality of bug reports, such as the length of descriptions, presence of stack traces, presence of attachments, completeness, and readability. In addition different definition of submitter reputation are compared and used. Then, a quality model is built for the evaluation of the quality of the bug reports, and a software tool has been implemented for supporting the application of the proposed model. The validation has been conducted on real cases of bug reports from open source software.

[1]  Nicholas Jalbert,et al.  Automated duplicate detection for bug tracking systems , 2008, 2008 IEEE International Conference on Dependable Systems and Networks With FTCS and DCC (DSN).

[2]  Gail C. Murphy,et al.  Who should fix this bug? , 2006, ICSE.

[3]  Gina Venolia,et al.  The secret life of bugs: Going past the errors and omissions in software repositories , 2009, 2009 IEEE 31st International Conference on Software Engineering.

[4]  Brad A. Myers,et al.  A Linguistic Analysis of How People Describe Software Problems , 2006, Visual Languages and Human-Centric Computing (VL/HCC'06).

[5]  Westley Weimer,et al.  Patches as better bug reports , 2006, GPCE '06.

[6]  Tim Menzies,et al.  Automated severity assessment of software defect reports , 2008, 2008 IEEE International Conference on Software Maintenance.

[7]  Thomas Zimmermann,et al.  Information needs in bug reports: improving cooperation between developers and users , 2010, CSCW '10.

[8]  Foutse Khomh,et al.  Is it a bug or an enhancement?: a text-based approach to classify change requests , 2008, CASCON '08.

[9]  Thomas Zimmermann,et al.  What Makes a Good Bug Report? , 2008, IEEE Transactions on Software Engineering.