Predicting re-opened bugs

A case study on the Eclipse project

Emad Shihab, Akinori Ihara, Yasutaka Kamei, Walid M. Ibrahim, Masao Ohira, Bram Adams, Ahmed E. Hassan, Ken Ichi Matsumoto

Research output: Chapter in Book/Report/Conference proceedingConference contribution

61 Citations (Scopus)

Abstract

Bug fixing accounts for a large amount of the software maintenance resources. Generally, bugs are reported, fixed, verified and closed. However, in some cases bugs have to be re-opened. Re-opened bugs increase maintenance costs, degrade the overall user-perceived quality of the software and lead to unnecessary rework by busy practitioners. In this paper, we study and predict re-opened bugs through a case study on the Eclipse project. We structure our study along 4 dimensions: 1) the work habits dimension (e.g., the weekday on which the bug was initially closed on), 2) the bug report dimension (e.g., the component in which the bug was found) 3) the bug fix dimension (e.g., the amount of time it took to perform the initial fix) and 4) the team dimension (e.g., the experience of the bug fixer). Our case study on the Eclipse Platform 3.0 project shows that the comment and description text, the time it took to fix the bug, and the component the bug was found in are the most important factors in determining whether a bug will be re-opened. Based on these dimensions we create decision trees that predict whether a bug will be re-opened after its closure. Using a combination of our dimensions, we can build explainable prediction models that can achieve 62.9% precision and 84.5% recall when predicting whether a bug will be re-opened.

Original languageEnglish
Title of host publicationProceedings - 17th Working Conference on Reverse Engineering, WCRE 2010
Pages249-258
Number of pages10
DOIs
Publication statusPublished - Dec 1 2010
Event17th Working Conference on Reverse Engineering, WCRE 2010 - Beverly, MA, United States
Duration: Oct 13 2010Oct 16 2010

Publication series

NameProceedings - Working Conference on Reverse Engineering, WCRE
ISSN (Print)1095-1350

Other

Other17th Working Conference on Reverse Engineering, WCRE 2010
CountryUnited States
CityBeverly, MA
Period10/13/1010/16/10

Fingerprint

Computer software maintenance
Decision trees
Costs

All Science Journal Classification (ASJC) codes

  • Software

Cite this

Shihab, E., Ihara, A., Kamei, Y., Ibrahim, W. M., Ohira, M., Adams, B., ... Matsumoto, K. I. (2010). Predicting re-opened bugs: A case study on the Eclipse project. In Proceedings - 17th Working Conference on Reverse Engineering, WCRE 2010 (pp. 249-258). [5645566] (Proceedings - Working Conference on Reverse Engineering, WCRE). https://doi.org/10.1109/WCRE.2010.36

Predicting re-opened bugs : A case study on the Eclipse project. / Shihab, Emad; Ihara, Akinori; Kamei, Yasutaka; Ibrahim, Walid M.; Ohira, Masao; Adams, Bram; Hassan, Ahmed E.; Matsumoto, Ken Ichi.

Proceedings - 17th Working Conference on Reverse Engineering, WCRE 2010. 2010. p. 249-258 5645566 (Proceedings - Working Conference on Reverse Engineering, WCRE).

Research output: Chapter in Book/Report/Conference proceedingConference contribution

Shihab, E, Ihara, A, Kamei, Y, Ibrahim, WM, Ohira, M, Adams, B, Hassan, AE & Matsumoto, KI 2010, Predicting re-opened bugs: A case study on the Eclipse project. in Proceedings - 17th Working Conference on Reverse Engineering, WCRE 2010., 5645566, Proceedings - Working Conference on Reverse Engineering, WCRE, pp. 249-258, 17th Working Conference on Reverse Engineering, WCRE 2010, Beverly, MA, United States, 10/13/10. https://doi.org/10.1109/WCRE.2010.36
Shihab E, Ihara A, Kamei Y, Ibrahim WM, Ohira M, Adams B et al. Predicting re-opened bugs: A case study on the Eclipse project. In Proceedings - 17th Working Conference on Reverse Engineering, WCRE 2010. 2010. p. 249-258. 5645566. (Proceedings - Working Conference on Reverse Engineering, WCRE). https://doi.org/10.1109/WCRE.2010.36
Shihab, Emad ; Ihara, Akinori ; Kamei, Yasutaka ; Ibrahim, Walid M. ; Ohira, Masao ; Adams, Bram ; Hassan, Ahmed E. ; Matsumoto, Ken Ichi. / Predicting re-opened bugs : A case study on the Eclipse project. Proceedings - 17th Working Conference on Reverse Engineering, WCRE 2010. 2010. pp. 249-258 (Proceedings - Working Conference on Reverse Engineering, WCRE).
@inproceedings{7ad8265a12f449ba9797e0294759ab45,
title = "Predicting re-opened bugs: A case study on the Eclipse project",
abstract = "Bug fixing accounts for a large amount of the software maintenance resources. Generally, bugs are reported, fixed, verified and closed. However, in some cases bugs have to be re-opened. Re-opened bugs increase maintenance costs, degrade the overall user-perceived quality of the software and lead to unnecessary rework by busy practitioners. In this paper, we study and predict re-opened bugs through a case study on the Eclipse project. We structure our study along 4 dimensions: 1) the work habits dimension (e.g., the weekday on which the bug was initially closed on), 2) the bug report dimension (e.g., the component in which the bug was found) 3) the bug fix dimension (e.g., the amount of time it took to perform the initial fix) and 4) the team dimension (e.g., the experience of the bug fixer). Our case study on the Eclipse Platform 3.0 project shows that the comment and description text, the time it took to fix the bug, and the component the bug was found in are the most important factors in determining whether a bug will be re-opened. Based on these dimensions we create decision trees that predict whether a bug will be re-opened after its closure. Using a combination of our dimensions, we can build explainable prediction models that can achieve 62.9{\%} precision and 84.5{\%} recall when predicting whether a bug will be re-opened.",
author = "Emad Shihab and Akinori Ihara and Yasutaka Kamei and Ibrahim, {Walid M.} and Masao Ohira and Bram Adams and Hassan, {Ahmed E.} and Matsumoto, {Ken Ichi}",
year = "2010",
month = "12",
day = "1",
doi = "10.1109/WCRE.2010.36",
language = "English",
isbn = "9780769541235",
series = "Proceedings - Working Conference on Reverse Engineering, WCRE",
pages = "249--258",
booktitle = "Proceedings - 17th Working Conference on Reverse Engineering, WCRE 2010",

}

TY - GEN

T1 - Predicting re-opened bugs

T2 - A case study on the Eclipse project

AU - Shihab, Emad

AU - Ihara, Akinori

AU - Kamei, Yasutaka

AU - Ibrahim, Walid M.

AU - Ohira, Masao

AU - Adams, Bram

AU - Hassan, Ahmed E.

AU - Matsumoto, Ken Ichi

PY - 2010/12/1

Y1 - 2010/12/1

N2 - Bug fixing accounts for a large amount of the software maintenance resources. Generally, bugs are reported, fixed, verified and closed. However, in some cases bugs have to be re-opened. Re-opened bugs increase maintenance costs, degrade the overall user-perceived quality of the software and lead to unnecessary rework by busy practitioners. In this paper, we study and predict re-opened bugs through a case study on the Eclipse project. We structure our study along 4 dimensions: 1) the work habits dimension (e.g., the weekday on which the bug was initially closed on), 2) the bug report dimension (e.g., the component in which the bug was found) 3) the bug fix dimension (e.g., the amount of time it took to perform the initial fix) and 4) the team dimension (e.g., the experience of the bug fixer). Our case study on the Eclipse Platform 3.0 project shows that the comment and description text, the time it took to fix the bug, and the component the bug was found in are the most important factors in determining whether a bug will be re-opened. Based on these dimensions we create decision trees that predict whether a bug will be re-opened after its closure. Using a combination of our dimensions, we can build explainable prediction models that can achieve 62.9% precision and 84.5% recall when predicting whether a bug will be re-opened.

AB - Bug fixing accounts for a large amount of the software maintenance resources. Generally, bugs are reported, fixed, verified and closed. However, in some cases bugs have to be re-opened. Re-opened bugs increase maintenance costs, degrade the overall user-perceived quality of the software and lead to unnecessary rework by busy practitioners. In this paper, we study and predict re-opened bugs through a case study on the Eclipse project. We structure our study along 4 dimensions: 1) the work habits dimension (e.g., the weekday on which the bug was initially closed on), 2) the bug report dimension (e.g., the component in which the bug was found) 3) the bug fix dimension (e.g., the amount of time it took to perform the initial fix) and 4) the team dimension (e.g., the experience of the bug fixer). Our case study on the Eclipse Platform 3.0 project shows that the comment and description text, the time it took to fix the bug, and the component the bug was found in are the most important factors in determining whether a bug will be re-opened. Based on these dimensions we create decision trees that predict whether a bug will be re-opened after its closure. Using a combination of our dimensions, we can build explainable prediction models that can achieve 62.9% precision and 84.5% recall when predicting whether a bug will be re-opened.

UR - http://www.scopus.com/inward/record.url?scp=78650665730&partnerID=8YFLogxK

UR - http://www.scopus.com/inward/citedby.url?scp=78650665730&partnerID=8YFLogxK

U2 - 10.1109/WCRE.2010.36

DO - 10.1109/WCRE.2010.36

M3 - Conference contribution

SN - 9780769541235

T3 - Proceedings - Working Conference on Reverse Engineering, WCRE

SP - 249

EP - 258

BT - Proceedings - 17th Working Conference on Reverse Engineering, WCRE 2010

ER -