Locating bug IDs and development logs in open source software (OSS) projects: An experience report

Bilyaminu Auwal Romo; Andrea Capiluppi; Ajaz Ali

doi:10.1109/3ICT.2018.8855769

Locating bug IDs and development logs in open source software (OSS) projects: An experience report

Bilyaminu Auwal Romo, Andrea Capiluppi^*, Ajaz Ali

^*Corresponding author for this work

Research output: Chapter in Book/Report/Conference proceeding › Chapter › Academic › peer-review

1 Citation (Scopus)

Abstract

The development logs of software projects, contained in Version Control (VC) systems can be severely incomplete when tracking bugs, especially in open source projects, resulting in a reduced traceability of defects. Other times, such logs can contain bug information that is not available in bug tracking system (BT system) repositories, and vice-versa: if the development logs and bug related-data (i.e., BT system data) were used together, researchers and practitioners often would have a larger set of bug IDs for a software project, and a better picture of a bug life cycle, its evolution and maintenance.Considering a sample of 10 OSS projects and their development logs and BT systems data, the two objectives of this paper are (i) to determine which of the keywords 'Fix', 'Bug' or the '#' identifier provide better precision; and (ii) to analyse their respective precision and recall at locating the larger amount possible of bug IDs manually.Overall, our results suggest that the use of the '#' identifier in conjunction with the bug ID digits (e.g., #1234) is more precise for locating bugs in development logs, than the use of the 'Bug' and 'Fix' keywords. Such keywords are indeed present in the development logs, but they are less useful when trying to connect the development actions with the bug traces in software project.

Original language	English
Title of host publication	2018 International Conference on Innovation and Intelligence for Informatics, Computing, and Technologies, 3ICT 2018
Publisher	Institute of Electrical and Electronics Engineers Inc.
ISBN (Print)	9781538692073
DOIs	https://doi.org/10.1109/3ICT.2018.8855769
Publication status	Published - 1-Nov-2018
Externally published	Yes
Event	2018 International Conference on Innovation and Intelligence for Informatics, Computing, and Technologies (3ICT) - Bahrain, Bahrain Duration: 18-Nov-2018 → 19-Nov-2018

Conference

Conference	2018 International Conference on Innovation and Intelligence for Informatics, Computing, and Technologies (3ICT)
Country/Territory	Bahrain
City	Bahrain
Period	18/11/2018 → 19/11/2018

Keywords

Bug data
Bug traceability
Bug-fixing commits
Development logs
SZZ algorithm

Access to Document

10.1109/3ICT.2018.8855769

Handle.net

Persistent link

Cite this

@inbook{80307e2686634c549b64dc34c684a62a,

title = "Locating bug IDs and development logs in open source software (OSS) projects: An experience report",

abstract = "The development logs of software projects, contained in Version Control (VC) systems can be severely incomplete when tracking bugs, especially in open source projects, resulting in a reduced traceability of defects. Other times, such logs can contain bug information that is not available in bug tracking system (BT system) repositories, and vice-versa: if the development logs and bug related-data (i.e., BT system data) were used together, researchers and practitioners often would have a larger set of bug IDs for a software project, and a better picture of a bug life cycle, its evolution and maintenance.Considering a sample of 10 OSS projects and their development logs and BT systems data, the two objectives of this paper are (i) to determine which of the keywords 'Fix', 'Bug' or the '#' identifier provide better precision; and (ii) to analyse their respective precision and recall at locating the larger amount possible of bug IDs manually.Overall, our results suggest that the use of the '#' identifier in conjunction with the bug ID digits (e.g., #1234) is more precise for locating bugs in development logs, than the use of the 'Bug' and 'Fix' keywords. Such keywords are indeed present in the development logs, but they are less useful when trying to connect the development actions with the bug traces in software project.",

keywords = "Bug data, Bug traceability, Bug-fixing commits, Development logs, SZZ algorithm",

author = "Romo, {Bilyaminu Auwal} and Andrea Capiluppi and Ajaz Ali",

year = "2018",

month = nov,

day = "1",

doi = "10.1109/3ICT.2018.8855769",

language = "English",

isbn = "9781538692073",

booktitle = "2018 International Conference on Innovation and Intelligence for Informatics, Computing, and Technologies, 3ICT 2018",

publisher = "Institute of Electrical and Electronics Engineers Inc.",

note = "2018 International Conference on Innovation and Intelligence for Informatics, Computing, and Technologies (3ICT) ; Conference date: 18-11-2018 Through 19-11-2018",

}

Romo, BA, Capiluppi, A & Ali, A 2018, Locating bug IDs and development logs in open source software (OSS) projects: An experience report. in 2018 International Conference on Innovation and Intelligence for Informatics, Computing, and Technologies, 3ICT 2018. Institute of Electrical and Electronics Engineers Inc., 2018 International Conference on Innovation and Intelligence for Informatics, Computing, and Technologies (3ICT), Bahrain, Bahrain, 18/11/2018. https://doi.org/10.1109/3ICT.2018.8855769

Locating bug IDs and development logs in open source software (OSS) projects: An experience report. / Romo, Bilyaminu Auwal; Capiluppi, Andrea; Ali, Ajaz.
2018 International Conference on Innovation and Intelligence for Informatics, Computing, and Technologies, 3ICT 2018. Institute of Electrical and Electronics Engineers Inc., 2018.

Research output: Chapter in Book/Report/Conference proceeding › Chapter › Academic › peer-review

TY - CHAP

T1 - Locating bug IDs and development logs in open source software (OSS) projects: An experience report

AU - Romo, Bilyaminu Auwal

AU - Capiluppi, Andrea

AU - Ali, Ajaz

PY - 2018/11/1

Y1 - 2018/11/1

N2 - The development logs of software projects, contained in Version Control (VC) systems can be severely incomplete when tracking bugs, especially in open source projects, resulting in a reduced traceability of defects. Other times, such logs can contain bug information that is not available in bug tracking system (BT system) repositories, and vice-versa: if the development logs and bug related-data (i.e., BT system data) were used together, researchers and practitioners often would have a larger set of bug IDs for a software project, and a better picture of a bug life cycle, its evolution and maintenance.Considering a sample of 10 OSS projects and their development logs and BT systems data, the two objectives of this paper are (i) to determine which of the keywords 'Fix', 'Bug' or the '#' identifier provide better precision; and (ii) to analyse their respective precision and recall at locating the larger amount possible of bug IDs manually.Overall, our results suggest that the use of the '#' identifier in conjunction with the bug ID digits (e.g., #1234) is more precise for locating bugs in development logs, than the use of the 'Bug' and 'Fix' keywords. Such keywords are indeed present in the development logs, but they are less useful when trying to connect the development actions with the bug traces in software project.

AB - The development logs of software projects, contained in Version Control (VC) systems can be severely incomplete when tracking bugs, especially in open source projects, resulting in a reduced traceability of defects. Other times, such logs can contain bug information that is not available in bug tracking system (BT system) repositories, and vice-versa: if the development logs and bug related-data (i.e., BT system data) were used together, researchers and practitioners often would have a larger set of bug IDs for a software project, and a better picture of a bug life cycle, its evolution and maintenance.Considering a sample of 10 OSS projects and their development logs and BT systems data, the two objectives of this paper are (i) to determine which of the keywords 'Fix', 'Bug' or the '#' identifier provide better precision; and (ii) to analyse their respective precision and recall at locating the larger amount possible of bug IDs manually.Overall, our results suggest that the use of the '#' identifier in conjunction with the bug ID digits (e.g., #1234) is more precise for locating bugs in development logs, than the use of the 'Bug' and 'Fix' keywords. Such keywords are indeed present in the development logs, but they are less useful when trying to connect the development actions with the bug traces in software project.

KW - Bug data

KW - Bug traceability

KW - Bug-fixing commits

KW - Development logs

KW - SZZ algorithm

UR - https://www.mendeley.com/catalogue/f08846bf-853c-3eff-a245-97de55c41f06/

U2 - 10.1109/3ICT.2018.8855769

DO - 10.1109/3ICT.2018.8855769

M3 - Chapter

SN - 9781538692073

BT - 2018 International Conference on Innovation and Intelligence for Informatics, Computing, and Technologies, 3ICT 2018

PB - Institute of Electrical and Electronics Engineers Inc.

T2 - 2018 International Conference on Innovation and Intelligence for Informatics, Computing, and Technologies (3ICT)

Y2 - 18 November 2018 through 19 November 2018

ER -

Locating bug IDs and development logs in open source software (OSS) projects: An experience report

Abstract

Conference

Keywords

Access to Document

Handle.net

Other files and links

Embargoed Document

Fingerprint

Cite this