The Community for Technology Leaders
2015 IEEE/ACM 12th Working Conference on Mining Software Repositories (MSR) (2015)
Florence, Italy
May 16, 2015 to May 17, 2015
ISBN: 978-0-7695-5594-2
pp: 258-268
Ripon K. Saha , Univ. of Texas at Austin, Austin, TX, USA
Julia Lawall , LIP6, Sorbonne Univ., Paris, France
Sarfraz Khurshid , Univ. of Texas at Austin, Austin, TX, USA
Dewayne E. Perry , Univ. of Texas at Austin, Austin, TX, USA
ABSTRACT
Understanding the severity of reported bugs is important in both research and practice. In particular, a number of recently proposed mining-based software engineering techniques predict bug severity, bug report quality, and bug-fix time, according to this information. Many bug tracking systems provide a field "severity" offering options such as "severe", "normal", and "minor", with "normal" as the default. However, there is a widespread perception that for many bug reports the label "normal" may not reflect the actual severity, because reporters may overlook setting the severity or may not feel confident enough to do so. In many cases, researchers ignore "normal" bug reports, and thus overlook a large percentage of the reports provided. On the other hand, treating them all together risks mixing reports that have very diverse properties. In this study, we investigate the extent to which "normal" bug reports actually have the "normal" severity. We find that many "normal" bug reports in practice are not normal. Furthermore, this misclassification can have a significant impact on the accuracy of mining-based tools and studies that rely on bug report severity information.
INDEX TERMS
Computer bugs, Software, Software engineering, Data mining, Training, Accuracy, Noise,Mining Software Repositories, Bug Severity, Bug Tracking System
CITATION
Ripon K. Saha, Julia Lawall, Sarfraz Khurshid, Dewayne E. Perry, "Are These Bugs Really "Normal"?", 2015 IEEE/ACM 12th Working Conference on Mining Software Repositories (MSR), vol. 00, no. , pp. 258-268, 2015, doi:10.1109/MSR.2015.31
89 ms
(Ver 3.3 (11022016))