ACM Home Page
Please provide us with feedback. Feedback
Where is bug resolution knowledge stored?
Full text PdfPdf (246 KB)
Source International Conference on Software Engineering archive
Proceedings of the 2006 international workshop on Mining software repositories table of contents
Shanghai, China
SESSION: MSR-challenge report table of contents
Pages: 183 - 184  
Year of Publication: 2006
ISBN:1-59593-397-2
Authors
Gerardo Canfora  University of Sannio, Benevento, Italy
Luigi Cerulo  University of Sannio, Benevento, Italy
Sponsors
ACM: Association for Computing Machinery
SIGSOFT: ACM Special Interest Group on Software Engineering
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 7,   Downloads (12 Months): 60,   Citation Count: 0
Additional Information:

abstract   references   index terms   collaborative colleagues  

Tools and Actions: Review this Article  
Save this Article to a Binder    Display Formats: BibTex  EndNote ACM Ref   
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/1137983.1138032
What is a DOI?

ABSTRACT

ArgoUML uses both CVS and Bugzilla to keep track of bug-fixing activities since 1998. A common practice is to reference source code changes resolving a bug stored in Bugzilla by inserting the id number of the bug in the CVS commit notes. This relationship reveals useful to predict code entities impacted by a new bug report.In this paper we analyze ArgoUML software repositories with a tool, we have implemented, showing what are Bugzilla fields that better predict such impact relationship, that is where knowledge about bug resolution is stored.



Collaborative Colleagues:
Gerardo Canfora: colleagues
Luigi Cerulo: colleagues