Learning from defect removals

Author

Ayewah, Nathaniel ; Pugh, William

Author_Institution

Dept. of Comput. Sci., Univ. of Maryland, College Park, MD

fYear

2009

fDate

16-17 May 2009

Firstpage

179

Lastpage

182

Abstract

Recent research has tried to identify changes in source code repositories that fix bugs by linking these changes to reports in issue tracking systems. These changes have been traced back to the point in time when they were previously modified as a way of identifying bug introducing changes. But we observe that not all changes linked to bug tracking systems are fixing bugs; some are enhancing the code. Furthermore, not all fixes are applied at the point in the code where the bug was originally introduced. We flesh out these observations with a manual review of several software projects, and use this opportunity to see how many defects are in the scope of static analysis tools.

Keywords

program debugging; program diagnostics; project management; software development management; software reviews; bug tracking system; fixing bug; software defect removal; software project review; source code repository; static analysis; Computer bugs; Computer science; Detectors; Educational institutions; Java; Joining processes; Security; Software tools; Spatial databases; Testing;

fLanguage

English

Publisher

ieee

Conference_Titel

Mining Software Repositories, 2009. MSR '09. 6th IEEE International Working Conference on

Conference_Location

Vancouver, BC

Print_ISBN

978-1-4244-3493-0

Type

conf

DOI

10.1109/MSR.2009.5069500

Filename

5069500