How long did it take to fix bugs?

Subscribe (Full Service)


	Search: The ACM Digital Library The Guide

	Feedback

How long did it take to fix bugs?

Full text

Pdf (225 KB)

Source

International Conference on Software Engineering archive
Proceedings of the 2006 international workshop on Mining software repositories table of contents

Shanghai, China

SESSION: MSR-challenge report table of contents

Pages: 173 - 174

Year of Publication: 2006

ISBN:1-59593-397-2

Authors

Sunghun Kim	University of California, Santa Cruz, CA
E. James Whitehead, Jr.	University of California, Santa Cruz, CA

Sponsors

ACM: Association for Computing Machinery
SIGSOFT: ACM Special Interest Group on Software Engineering

Publisher

ACM New York, NY, USA

Bibliometrics

Downloads (6 Weeks): 9, Downloads (12 Months): 65, Citation Count: 3

Additional Information:

abstract references cited by index terms collaborative colleagues

Tools and Actions:	Review this Article Save this Article to a Binder Display Formats: BibTeX EndNote ACM Ref

DOI Bookmark:	Use this link to bookmark this Article: http://doi.acm.org/10.1145/1137983.1138027 What is a DOI?

ABSTRACT

The number of bugs (or fixes) is a common factor used to measure the quality of software and assist bug related analysis. For example, if software files have many bugs, they may be unstable. In comparison, the bug-fix time--the time to fix a bug after the bug was introduced--is neglected. We believe that the bug-fix time is an important factor for bug related analysis, such as measuring software quality. For example, if bugs in a file take a relatively long time to be fixed, the file may have some structural problems that make it difficult to make changes. In this report, we compute the bug-fix time of files in ArgoUML and PostgreSQL by identifying when bugs are introduced and when the bugs are fixed. This report includes bug-fix time statistics such as average bug-fix time, and distributions of bug-fix time. We also list the top 20 bug-fix time files of two projects.

REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

	1	Jennifer Bevan , E. James Whitehead, Jr. , Sunghun Kim , Michael Godfrey, Facilitating software evolution research with kenyon, Proceedings of the 10th European software engineering conference held jointly with 13th ACM SIGSOFT international symposium on Foundations of software engineering, September 05-09, 2005, Lisbon, Portugal
	2	Davor Čubranić , Gail C. Murphy, Hipikat: recommending pertinent software development artifacts, Proceedings of the 25th International Conference on Software Engineering, May 03-10, 2003, Portland, Oregon
	3	Michael Fischer , Martin Pinzger , Harald Gall, Populating a Release History Database from Version Control and Bug Tracking Systems, Proceedings of the International Conference on Software Maintenance, p.23, September 22-26, 2003
	4	Audris Mockus , Lawrence G. Votta, Identifying Reasons for Software Changes Using Historic Databases, Proceedings of the International Conference on Software Maintenance (ICSM'00), p.120, October 11-14, 2000
	5	Jacek Śliwerski , Thomas Zimmermann , Andreas Zeller, When do changes induce fixes?, Proceedings of the 2005 international workshop on Mining software repositories, p.1-5, May 17-17, 2005, St. Louis, Missouri

CITED BY 3

	Lucas D. Panjer, Predicting Eclipse Bug Lifetimes, Proceedings of the Fourth International Workshop on Mining Software Repositories, p.29, May 20-26, 2007
	Rudolf Ramler, The impact of product development on the lifecycle of defects, Proceedings of the 2008 workshop on Defects in large software systems, July 20-20, 2008, Seattle, Washington
	Pieter Hooimeijer , Westley Weimer, Modeling bug report quality, Proceedings of the twenty-second IEEE/ACM international conference on Automated software engineering, November 05-09, 2007, Atlanta, Georgia, USA