How long did it take to fix bugs?

TitleHow long did it take to fix bugs?
Publication TypeConference Paper
Year of Publication2006
AuthorsKim, S, Whitehead, Jr., JE
Secondary TitleProceedings of the 2006 international workshop on Mining software repositories
Pagination173–174
PublisherACM
Place PublishedNew York, NY, USA
ISBN Number1-59593-397-2
Keywordsargouml, bug fixing, bugs, mining challenge, msr challenge, postgresql, quality, time
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.

URLhttp://doi.acm.org/10.1145/1137983.1138027
DOI10.1145/1137983.1138027
Full Text
AttachmentSize
PDF icon 173HowLong.pdf263.4 KB