ACM Home Page
Please provide us with feedback. Feedback
Comparing methods to identify defect reports in a change management database
Full text PdfPdf (146 KB)
Source International Symposium on Software Testing and Analysis archive
Proceedings of the 2008 workshop on Defects in large software systems table of contents
Seattle, Washington
SESSION: Technical papers table of contents
Pages 27-31  
Year of Publication: 2008
ISBN:978-1-60558-051-7
Authors
Elaine J. Weyuker  AT&T Labs - Research, Florham Park, NJ
Thomas J. Ostrand  AT&T Labs - Research, Florham Park, NJ
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 6,   Downloads (12 Months): 56,   Citation Count: 0
Additional Information:

abstract   references   index terms   collaborative colleagues  

Tools and Actions: Request Permissions Request Permissions    Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/1390817.1390825
What is a DOI?

ABSTRACT

A key problem when doing automated fault analysis and fault prediction from information in a software change management database is how to determine which change reports represent software faults. In some change management systems, there is no simple way to distinguish fault reports from changes made to add new functionality or perform routine maintenance. This paper describes a comparison of two methods for classifying change reports for a large software system, and concludes that, for that particular system, the stage of development when the report was initialized is a more accurate indicator of its fault status than the presence of certain keywords in the report's natural language description.



Collaborative Colleagues:
Elaine J. Weyuker: colleagues
Thomas J. Ostrand: colleagues