Characterizing and predicting which bugs get reopened

Proceedings - International Conference on Software Engineering

Volumn , Issue , 2012, Pages 1074-1083

  Zimmermann, Thomas ^a   Nagappan, Nachiappan ^a   Guo, Philip J ^b   Murphy, Brendan ^a  

^a MICROSOFT RESEARCH   (United States)

^b STANFORD UNIVERSITY   (United States)

Author keywords

bug reopen; bug report; bug triage

Indexed keywords

BUG REOPEN; BUG REPORTS; BUG TRIAGE; EMPIRICAL CASE STUDIES; MICROSOFT; MICROSOFT WINDOWS; QUANTITATIVE STUDY; SOFTWARE DEVELOPMENT PROCESS; SOFTWARE SYSTEMS; STATISTICAL MODELS;

WINDOWS OPERATING SYSTEM;

SOFTWARE ENGINEERING;

EID: 84864228604     PISSN: 02705257     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1109/ICSE.2012.6227112     Document Type: Conference Paper

References (32)

1. Shihab, E., Ihara, A., Kamei, Y., Ibrahim, W.M., Ohira, M., Adams, B., Hassan, A.E., and Matsumoto, K.-i. Predicting Re-opened Bugs: A Case Study on the Eclipse Project. In Proceedings of the 17th Working Conference on Reverse Engineering (2010), 249-258.
2. Hooimeijer, P. and Weimer, W. Modeling bug report quality. In Proceedings of the 22nd IEEE/ACM International Conference on Automated Software Engineering (2007), 34-43.
3. Panjer, L.D. Predicting Eclipse Bug Lifetimes. In MSR '07: Proceedings of the Fourth International Workshop on Mining Software Repositories (2007).
4. Bettenburg, N., Just, S., Schröter, A., Weiss, C., Premraj, R., and Zimmermann, T. What Makes a Good Bug Report? In FSE '08: Proceedings of the 16th International Symposium on Foundations of Software Engineering (November 2008).
5. Anbalagan, P. and Vouk, M. On Predicting the Time taken to Correct Bugs in Open Source Projects (short paper). In ICSM '09: Proceedings of the International Conference on Software Maintenance (September 2009).
6. Mockus, A., Fielding, R.T., and Herbsleb, J.D. Two case studies of open source software development: Apache and Mozilla. ACM Trans. Softw. Eng. Methodol., 11 (2002), 309-346.
7. Herbsleb, J.D. and Mockus, A. An Empirical Study of Speed and Communication in Globally Distributed Software Development. IEEE Trans. Software Eng., 29 (2003), 481-494.
8. Cataldo, M., Herbsleb, J.D., and Carley, K.M. Socio-technical congruence: a framework for assessing the impact of technical and work dependencies on software development productivity. In ESEM '08: Proceedings of the Second ACM-IEEE international symposium on Empirical software engineering and measurement (2008), ACM, 2-11.
9. Aranda, J. and Venolia, G. The Secret Life of Bugs: Going Past the Errors and Omissions in Software Repositories. In ICSE' 09: Proceedings of the 31st International Conference on Software Engineering (2009).
10. Breu, S., Premraj, R., Sillito, J., and Zimmermann, T. Investigating Information Needs to Improve Cooperation Between Developers and Bug Reporters. In CSCW '10: Proceedings of the ACM Conference on Computer Supported Cooperative Work (February 2010).
11. Bettenburg, N., Premraj, R., Zimmermann, T., and Kim, S. Duplicate Bug Reports Considered Harmful. Really? In ICSM '08: Proceedings of the 24th IEEE International Conference on Software Maintenance (September 2008), 337-345.
12. Jeong, G., Kim, S., and Zimmermann, T. Improving Bug Triage with Bug Tossing Graphs. In ESEC-FSE '09: Proceedings of the European Software Engineering Conference and ACM SIGSOFT Symposium on Foundations of Software Engineering (2009).
13. Ko, A.J., Myers, B.A., and Chau, D.H. A Linguistic Analysis of How People Describe Software Problems. In VL/HCC '06: Proceedings of the 2006 IEEE Symposium on Visual Languages and Human-Centric Computing (2006), 127-134.
14. Bertram, D., Voida, A., Greenberg, S., and Walker, R. Communication, collaboration, and bugs: the social nature of issue tracking in small, collocated teams. In CSCW '10: Proceedings of the 2010 ACM Conference on Computer Supported Cooperative Work (2010), 291-300.
15. Ko, A.J. and Chilana, P.K. How power users help and hinder open bug reporting.. In CHI '10: Proceedings of the 28th International Conference on Human Factors in Computing Systems (2010), 1665-1674.
16. Guo, P.J., Zimmermann, T., Nagappan, N., and Murphy, B. Characterizing and predicting which bugs get fixed: an empirical study of Microsoft Windows. In Proceedings of the 32nd ACM/IEEE International Conference on Software Engineering (2010), 495-504.
17. Guo, P.J., Zimmermann, T., Nagappan, N., and Murphy, B. "Not my bug!" and other reasons for software bug report reassignments. In CSCW '11: Proceedings of the 2011 ACM Conference on Computer Supported Cooperative Work (2011), 395-404.
18. Anvik, J., Hiew, L., and Murphy, G.C. Who should fix this bug? In ICSE '06: Proceedings of the 28th International Conference on Software Engineering (2006), 361-370.
19. Anvik, J. and Murphy, G. Reducing the Effort of Bug Report Triage: Recommenders for Development-oriented Decisions. ACM Transactions on Software Engineering and Methodology (TOSEM).
20. Canfora, G. and Cerulo, L. Supporting change request assignment in open source development. In SAC '06: Proceedings of the 2006 ACM Symposium on Applied Computing (2006), 1767-1772.
21. Canfora, G. and Cerulo, L. Fine grained indexing of software repositories to support impact analysis. In MSR '06: Proceedings of the International Workshop on Mining Software Repositories (2006), 105-111.
22. Hiew, L. Assisted detection of duplicate bug reports. , 2006. The University of British Columbia.
23. Runeson, P., Alexandersson, M., and Nyholm, O. Detection of Duplicate Defect Reports Using Natural Language Processing. In ICSE '07: Proceedings of the 29th International Conference on Software Engineering (2007), 499-510.
24. Jalbert, N. and Weimer, W. Automated duplicate detection for bug tracking systems. In DSN '08: Proceedings of the Annual IEEE/IFIP International Conference on Dependable Systems and Networks (2008), 52-61.
25. Wang, X., Zhang, L., Xie, T., Anvik, J., and Sun, J. An Approach to Detecting Duplicate Bug Reports using Natural Language and Execution Information. In ICSE '08: Proceedings of the 30th International Conference on Software Engineering (May 2008).
26. Menzies, T. and Marcus, A. Automated severity assessment of software defect reports. In ICSM '08: Proceedings of the 24th IEEE International Conference on Software Maintenance (September 2008), 346-355.
27. Weiss, C., Premraj, R., Zimmermann, T., and Zeller, A. How Long Will It Take to Fix This Bug? In MSR '07: Proceedings of the Fourth International Workshop on Mining Software Repositories (2007).
28. Basili, V.R., Shull, F., and Lanubile, F. Building Knowledge through Families of Experiments. IEEE Trans. Software Eng., 25 (1999), 456-473.
29. Barker, I. What is information architecture? , 2005. KM Column, http://www.steptwo.com.au.
30. Bird, C., Nagappan, N., Devanbu, P.T., Gall, H., and Murphy, B. Does distributed development affect software quality? An empirical case study of Windows Vista. In Proceedings of the 31st International Conference on Software Engineering (2009), 518-528.
31. Glerum, K., Kinshumann, K., Greenberg, S., Aul, G., Orgovan, V., Nichols, G., Grant, D., Loihle, G., and Hunt, G. Debugging in the (Very) Large: Ten Years of Implementation and Experience. In SOSP '09: Proceedings of the Symposium on Operating Systems Principles (2009).
32. Cheshire, J. Image or ImageButton without ImageUrl Causes HTTP GET for Default Document.. http://blogs.msdn.com/b/jamesche/archive/2009/01/28/image-or- imagebutton-without-imageurl-causes-http-get-for-default-document.aspx.