Better cross company defect prediction
Authors:
- 1 May 2013
- conference paper
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- No. 21601852,p. 409-418
Abstract
How can we find data for quality prediction? Early in the life cycle, projects may lack the data needed to build such predictors. Prior work assumed that relevant training data was found nearest to the local project. But is this the best approach? This paper introduces the Peters filter which is based on the following conjecture: When local data is scarce, more information exists in other projects. Accordingly, this filter selects training data via the structure of other projects. To assess the performance of the Peters filter, we compare it with two other approaches for quality prediction. Within-company learning and cross-company learning with the Burak filter (the state-of-the-art relevancy filter). This paper finds that: 1) within-company predictors are weak for small data-sets; 2) the Peters filter+cross-company builds better predictors than both within-company and the Burak filter+cross-company; and 3) the Peters filter builds 64% more useful predictors than both within-company and the Burak filter+cross-company approaches. Hence, we recommend the Peters filter for cross-company learning.Keywords
This publication has 29 references indexed in Scilit:
- Balancing Privacy and Utility in Cross-Company Defect PredictionIEEE Transactions on Software Engineering, 2013
- On software engineering repositories and their open problems2012
- When to use data from other projects for effort estimation2010
- Towards identifying software project clusters with regard to defect prediction2010
- Web-scale k-means clustering2010
- Practical considerations in deploying AI for defect prediction2009
- Cross versus Within-Company Cost Estimation Studies: A Systematic ReviewIEEE Transactions on Software Engineering, 2007
- Data Mining Static Code Attributes to Learn Defect PredictorsIEEE Transactions on Software Engineering, 2006
- What we have learned about fighting defects2002
- Understanding and controlling software costsIEEE Transactions on Software Engineering, 1988