Predicting Defects for Eclipse
Published 1 May 2007
Thomas Zimmermann, Rahul Premraj, Andreas Zeller
Citations752
Generate an AI Snapshot to get a quick, structured summary of this paper.
Study Snapshot
ObjectiveStudy objective
MethodsResearch methodology
PopulationPopulation studied
Sample sizeSample sizes
OutcomesStudy outcomes here
ResultsStudy results comes here
LimitationsResearch study limitations comes here
A concise AI-generated summary of the paper will appear here once you click Generate AI Snapshot.
TL;DR
The resulting data set lists the number of pre- and post-release defects for every package and file in the eclipse releases 2.0, 2.1, and 3.0.
Abstract
We have mapped defects from the bug database of eclipse (one of the largest open-source projects) to source code locations. The resulting data set lists the number of pre- and post-release defects for every package and file in the eclipse releases 2.0, 2.1, and 3.0. We additionally annotated the data with common complexity metrics. All data is publicly available and can serve as a benchmark for defect prediction models.
Keywords
Computer Science
IEEE Transactions on Software EngineeringA validation of object-oriented design metrics as quality indicators
1,701 Citations1996Victor R. Basili, Lionel Briand +1 more
Several of Chidamber and Kemerer's 00 metrics appear to be adequate to predict class fault-proneness during the early phases of the life-cycle, and are, on the data set, better predictors than "traditional" code metrics, which can only be collected at a later phase of the software development processes.
ACM SIGSOFT Software Engineering NotesWhen do changes induce fixes?
803 Citations2005Jacek Śliwerski, Thomas Zimmermann +1 more
In a first investigation of the MOZILLA and ECLIPSE history, it turns out that fix-inducing changes show distinct patterns with respect to their size and the day of week they were applied.
Mining metrics to predict component failures
770 Citations2006Nachiappan Nagappan, Thomas Ball +1 more
Using principal component analysis on the code metrics, this work built regression models that accurately predict the likelihood of post-release defects for new entities and can be generalized to arbitrary projects.
Use of relative code churn measures to predict system defect density
748 Citations2005Nachiappan Nagappan, Thomas Ball
A technique for early prediction of system defect density using a set of relative code churn measures that relate the amount of churn to other variables such as component size and the temporal extent of churn, which shows that while absolute measures of code chum are poor predictors of defect density, these measures are highly predictive of defectdensity.
IEEE Transactions on Software EngineeringPredicting fault incidence using software change history
744 Citations2000Todd Graves, Alan F. Karr +2 more
This paper uses change management data from a very large, long-lived software system to explore the extent to which measurements from the change history are successful in predicting the distribution over modules of these incidences of faults.
IEEE Transactions on Software EngineeringPredicting the location and number of faults in large software systems
721 Citations2005Thomas J. Ostrand, Elaine J. Weyuker +1 more
A negative binomial regression model has been developed and used to predict the expected number of faults in each file of the next release of a system, based on the code of the file in the current release, and fault and modification history of thefile from previous releases.
IEEE Transactions on Software EngineeringEmpirical analysis of CK metrics for object-oriented design complexity: implications for software defects
671 Citations2003Ramanath Subramanyam, Mayuram S. Krishnan
Empirical evidence is provided supporting the role of OO design complexity metrics, specifically a subset of the Chidamber and Kemerer (1991, 1994) suite (CK metrics), in determining software defects, and indicates that these metrics are significantly associated with defects.
Populating a Release History Database from version control and bug tracking systems
534 Citations2004Michael Fischer, Martin Pinzger +1 more
An approach is introduced for populating a release history database that combines version data with bug tracking data and adds missing data not covered by version control systems such as merge points to obtain meaningful views showing the evolution of a software project.
When do changes induce fixes?
377 Citations2005Jacek Śliwerski, Thomas Zimmermann +1 more
IEEE Transactions on Software EngineeringPredicting fault-prone software modules in telephone switches
341 Citations1996Niclas Ohlsson, H. Alberg
Applying the method described in this paper makes it possible to use measures at the design phase to predict the most fault-prone modules, which is a valuable complement to linear regression when prediction data is ordinal.
Hipikat: recommending pertinent software development artifacts
320 Citations2003Davor Čubranić, Gail C. Murphy
Proceedings. 27th International Conference on Software Engineering, 2005. ICSE 2005.Use of relative code churn measures to predict system defect density
189 Citations2005Nachiappan Nagappan, T. Ball
Predicting component failures at design time
180 Citations2006Adrian Schröter, Thomas Zimmermann +1 more
An empirical study of 52 ECLIPSE plug-ins found that the software design as well as past failure history, can be used to build models which accurately predict failure-prone components in new programs.
25th International Conference on Software Engineering, 2003. Proceedings.Hipikat: recommending pertinent software development artifacts
173 Citations2003Davor Čubranić, Gail C. Murphy
The Hipikat tool is described, a tool that forms an implicit group memory from the information stored in a project's archives, and that recommends artifacts from the archives that are relevant to a task that a newcomer is trying to perform.
Validation of the coupling dependency metric as a predictor of run-time failures and maintenance measures
137 Citations1998Aaron B. Binkley, Stephen R. Schach
IEEE SoftwareEmerald: software metrics and models on the desktop
136 Citations1996J.P. Hudepohl, S.J. Aud +3 more
An empirical evaluation of fault-proneness models
128 Citations2002Giovanni Denaro, Mauro Pezzè
Detection of software modules with high debug code churn in a very large legacy system
94 Citations2002Taghi M. Khoshgoftaar, Edward B. Allen +3 more
This study analyzes two consecutive releases of a large legacy software system for telecommunications and applies discriminant analysis to identify fault prone modules based on 16 static software product metrics and the amount of code changed during development.
Validation of the coupling dependency metric as a predictor of run-time failures and maintenance measures
83 Citations2002Aaron B. Binkley, S.R. Schach
The coupling dependency metric is applied to four case studies and outperformed a wide variety of competing metrics in predicting run-time failures and a number of different maintenance measures, implying that coupling metrics may be good predictors of levels of interaction within a software product.
An empirical evaluation of fault-proneness models
54 Citations2002Giovanni Denaro, Mauro Pezzè
An empirical study of the validity of multivariate models for predicting software fault-proneness across different applications shows that suitably selectedMultivariate models can predict fault- pronounced modules of different software packages.
Deriving models of software fault-proneness
52 Citations2002Giovanni Denaro, Sandro Morasca +1 more
By using logistic regression, this paper shows how models can be built that relate software measures and software fault-proneness for classes of homogeneous software products and proposes the use of cross-validation for selecting valid models even for small data sets.
NatureExplaining Failures Using Software Dependences and Churn Metrics
12 Citations2006Nachiappan Nagappan, Thomas Ball
The Windows Server 2003 operating system is analyzed in order to assess the relationship between its software dependences, churn metrics and post-release failures and indicates the ability ofSoftware dependences and churn metrics to be efficient predictors of post- release failures.
Proceedings of the 14th international conference on Software engineering and knowledge engineering - SEKE '02Deriving models of software fault-proneness
3 Citations2002Giovanni Denaro, Sandro Morasca +1 more