Merits of using repository metrics in defect prediction for open source projects
Authors:
- 1 May 2009
- conference paper
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- p. 31-36
Abstract
Many corporate code developers are the beta testers of open source software. They continue testing until they are sure that they have a stable version to build their code on. In this respect defect predictors play a critical role to identify defective parts of the software. Performance of a defect predictor is determined by correctly finding defective parts of the software without giving any false alarms. Having high false alarms means testers/developers would inspect bug free code unnecessarily. Therefore in this research we focused on decreasing the false alarm rates by using repository metrics. We conducted experiments on the data sets of Eclipse project. Our results showed that repository metrics decreased the false alarm rates on the average to 23% from 32% corresponding up to 907 less files to inspect.Keywords
This publication has 14 references indexed in Scilit:
- On the relative value of cross-company and within-company data for defect predictionEmpirical Software Engineering, 2009
- Ensemble of software defect predictors2008
- Exploring the effects of SourceForge.net coordination and communication tools on the efficiency of open source projects using data envelopment analysisEmpirical Software Engineering, 2008
- Do too many cooks spoil the broth? Using the number of developers to enhance defect prediction modelsEmpirical Software Engineering, 2008
- A comparative analysis of the efficiency of change metrics and static code attributes for defect prediction2008
- Predicting Defects for Eclipse2007
- A Multivariate Analysis of Static Code Attributes for Defect Prediction2007
- Predicting the location and number of faults in large software systemsIEEE Transactions on Software Engineering, 2005
- Two case studies of open source software developmentACM Transactions on Software Engineering and Methodology, 2002
- Empirical studies of software engineering2000