A probabilistic model of information retrieval: development and comparative experiments
Information Processing and Management: an International Journal
Modern Information Retrieval
Populating a Release History Database from Version Control and Bug Tracking Systems
ICSM '03 Proceedings of the International Conference on Software Maintenance
Impact Analysis by Mining Software and Change Request Repositories
METRICS '05 Proceedings of the 11th IEEE International Software Metrics Symposium
Jimpa: An Eclipse Plug-in for Impact Analysis
CSMR '06 Proceedings of the Conference on Software Maintenance and Reengineering
Recovering traceability links between source code and fixed bugs via patch analysis
Proceedings of the 6th International Workshop on Traceability in Emerging Forms of Software Engineering
Hi-index | 0.00 |
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.