Characterizing and predicting which bugs get fixed: An empirical study of Microsoft Windows

Proceedings - International Conference on Software Engineering

Volumn 1, Issue , 2010, Pages 495-504

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

^a STANFORD UNIVERSITY   (United States)

^b MICROSOFT RESEARCH   (United States)

Author keywords

D.2.5 Software Engineering : Testing and Debugging; D.2.7 Software Engineering : Distribution, Maintenance, and Enhancement; Human Factors; Management; Measurement

Indexed keywords

D.2.5 [SOFTWARE ENGINEERING]: TESTING AND DEBUGGING; D.2.7 [SOFTWARE ENGINEERING]: DISTRIBUTION, MAINTENANCE, AND ENHANCEMENT; HUMAN FACTORS; TESTING AND DEBUGGING;

COMPUTER OPERATING SYSTEMS; COMPUTER SOFTWARE MAINTENANCE; ENGINEERING; FORECASTING; HUMAN ENGINEERING; PROBABILITY DENSITY FUNCTION; SOFTWARE ENGINEERING; SURVEYS;

PROGRAM DEBUGGING;

EID: 77954714792     PISSN: 02705257     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1145/1806799.1806871     Document Type: Conference Paper

References (42)

1. P. Anbalagan and M. Vouk. On predicting the time taken to correct bugs in open source projects (short paper). In ICSM '09: Proceedings of the 25th IEEE International Conference on Software Maintenance, September 2009.
2. G. Antoniol, K. Ayari, M. Di Penta, F. Khomh, and Y.-G. Guéhéneuc. Is it a bug or an enhancement?: a text-based approach to classify change requests. In CASCON '08: Proceedings of the 2008 conference of the center for advanced studies on collaborative research, pages 304-318, 2008.
3. J. Anvik, L. Hiew, and G. C. Murphy. Who should fix this bug? In ICSE '06: Proceedings of the 28th International Conference on Software Engineering, pages 361-370, 2006.
4. J. Anvik and G. Murphy. Reducing the effort of bug report triage: Recommenders for development-oriented decisions. ACM Transactions on Software Engineering and Methodology (TOSEM).
5. J. Aranda and G. Venolia. 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.
6. V. R. Basili, F. Shull, and F. Lanubile. Building knowledge through families of experiments. IEEE Trans. Softw. Eng., 25(4), 1999.
7. N. Bettenburg, S. Just, A. Schröter, C. Weiss, R. Premraj, and T. Zimmermann. What makes a good bug report? In FSE '08: Proceedings of the 16th International Symposium on Foundations of Software Engineering, November 2008.
8. N. Bettenburg, R. Premraj, T. Zimmermann, and S. Kim. Duplicate bug reports considered harmful... really? In ICSM '08: Proceedings of the 24th IEEE International Conference on Software Maintenance, pages 337-345, September 2008.
9. C. Bird, A. Bachmann, E. Aune, J. Duffy, A. Bernstein, V. Filkov, and P. Devanbu. Fair and balanced? bias in bug-fix datasets. In ESEC-FSE '09: Proceedings of the European Software Engineering Conference and ACM SIGSOFT Symposium on Foundations of Software Engineering, 2009.
10. C. Bird, N. Nagappan, P. Devanbu, H. Gall, and B. Murphy. Does distributed development affect software quality? an empirical case study of windows vista. In ICSE '09: Proceedings of the 2009 IEEE 31st International Conference on Software Engineering, pages 518-528, Washington, DC, USA, 2009. IEEE Computer Society.
11. S. Breu, R. Premraj, J. Sillito, and T. Zimmermann. 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.
12. G. Canfora and L. Cerulo. Fine grained indexing of software repositories to support impact analysis. In MSR '06: Proceedings of the International Workshop on Mining Software Repositories, pages 105-111, 2006.
13. G. Canfora and L. Cerulo. Supporting change request assignment in open source development. In SAC '06: Proceedings of the 2006 ACM Symposium on Applied Computing, pages 1767-1772, 2006.
14. M. Cataldo, J. D. Herbsleb, and K. M. Carley. 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, pages 2-11. ACM, 2008.
15. CNET News.com Staff. Microsoft tests its own 'dog food'. http://news.zdnet.com/2100-3513-22-130518.html, 2003.
16. S. Dowdy, S. Weardon, and D. Chilko. Statistics for Research, volume 1345 of Wiley Series in Probability and Statistics. John Wiley & Sons, New Jersey, 2004.
17. P. J. Guo and D. Engler. Linux kernel developer responses to static analysis bug reports. In USENIX ATC '09: Proceedings of the 2009 USENIX Annual Technical Conference, pages 285-292, June 2009.
18. B. Hailpern and P. Santhanam. Software debugging, testing, and verification. IBM Systems Journal, 41(1):4-12, 2002.
19. J. D. Herbsleb and R. E. Grinter. Architectures, coordination, and distance: Conway's law and beyond. IEEE Softw., 16(5):63-70, 1999.
20. J. D. Herbsleb and A. Mockus. An empirical study of speed and communication in globally distributed software development. IEEE Trans. Software Eng., 29(6):481-494, 2003.
21. I. Herraiz, D. M. German, J. M. Gonzalez-Barahona, and G. Robles. Towards a simplification of the bug report form in Eclipse. In MSR '08: Proceedings of the 2008 international working conference on Mining software repositories, pages 145-148. ACM, 2008.
22. L. Hiew. Assisted detection of duplicate bug reports. Master's thesis, The University of British Columbia, 2006.
23. P. Hooimeijer and W. Weimer. Modeling bug report quality. In ASE '07: Proceedings of the twenty-second IEEE/ACM International Conference on Automated Software Engineering, pages 34-43, 2007.
24. D. W. Hosmer and S. Lemeshow. Applied Logistic Regression. John Wiley & Sons, 2nd edition, 2000.
25. N. Jalbert and W. Weimer. Automated duplicate detection for bug tracking systems. In DSN '08: Proceedings of the Annual IEEE/IFIP International Conference on Dependable Systems and Networks, pages 52-61, 2008.
26. G. Jeong, S. Kim, and T. Zimmermann. 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.
27. S. Just, R. Premraj, and T. Zimmermann. Towards the next generation of bug tracking systems. In VL/HCC '08: Proceedings of the 2008 IEEE Symposium on Visual Languages and Human-Centric Computing, pages 82-85, September 2008.
28. S. Kim and M. D. Ernst. Which warnings should I fix first? In ESEC-FSE '07: Proc. 6th joint meeting of the European software engineering conference and the ACM SIGSOFT symposium on The foundations of software engineering, pages 45-54. ACM, 2007.
29. A. J. Ko, B. A. Myers, and D. H. Chau. 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, pages 127-134, 2006.
30. D. W. van Liere. How Shallow is a Bug? Open Source Communities as Information Repositories and Solving Software Defects. SSRN eLibrary, 2009. http://ssrn.com/paper=1507233.
31. D. W. van Liere. Improving Bugzilla's bug overview list by predicting which bug will get fixed, June 2009. http://network-labs.org/2009/06/improving- bugzilla's-bug-overview-list-%by-predicting-which-bug-will-get-fixed/.
32. T. Menzies and A. Marcus. Automated severity assessment of software defect reports. In ICSM '08: Proc. 24th IEEE International Conference on Software Maintenance, pages 346-355, Sept 2008.
33. A. Mockus, R. T. Fielding, and J. D. Herbsleb. Two case studies of open source software development: Apache and Mozilla. ACM Trans. Softw. Eng. Methodol., 11(3):309-346, 2002.
34. N. Nagappan, B. Murphy, and V. Basili. The influence of organizational structure on software quality: an empirical case study. In ICSE '08: Proceedings of the 30th international conference on Software engineering, pages 521-530, 2008.
35. J. Neter, M. H. Kutner, C. J. Nachtsheim, and W. Wasserman. Applied Linear Statistical Models. Irwin, 4th edition, 1996.
36. L. D. Panjer. Predicting Eclipse bug lifetimes. In MSR '07: Proceedings of the Fourth International Workshop on Mining Software Repositories, 2007. MSR Challenge Contribution.
37. P. Runeson, M. Alexandersson, and O. Nyholm. Detection of duplicate defect reports using natural language processing. In ICSE '07: Proceedings of the 29th International Conference on Software Engineering, pages 499-510, 2007.
38. J. R. Ruthruff, J. Penix, J. D. Morgenthaler, S. Elbaum, and G. Rothermel. Predicting accurate and actionable static analysis warnings: an experimental approach. In ICSE '08: Proceedings of the 30th international conference on Software engineering, pages 341-350. ACM, 2008.
39. E. Sink. My life as a code economist, November 2005. http://www.ericsink. com/articles/Four-Questions.html.
40. J. Śliwerski, T. Zimmermann, and A. Zeller. When do changes induce fixes? In MSR '05: Proceedings of the 2005 international workshop on Mining software repositories, pages 1-5. ACM, 2005.
41. X. Wang, L. Zhang, T. Xie, J. Anvik, and J. Sun. 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, pages 461-470. ACM, 2008.
42. C. Weiss, R. Premraj, T. Zimmermann, and A. Zeller. How long will it take to fix this bug? In MSR '07: Proceedings of the Fourth International Workshop on Mining Software Repositories, 2007.