The mythical man-month (anniversary ed.)
The mythical man-month (anniversary ed.)
The distribution of faults in a large industrial software system
ISSTA '02 Proceedings of the 2002 ACM SIGSOFT international symposium on Software testing and analysis
Quantitative Analysis of Faults and Failures in a Complex Software System
IEEE Transactions on Software Engineering
Using Historical In-Process and Product Metrics for Early Estimation of Software Failures
ISSRE '06 Proceedings of the 17th International Symposium on Software Reliability Engineering
Data Mining Static Code Attributes to Learn Defect Predictors
IEEE Transactions on Software Engineering
Predicting Defects for Eclipse
ICSEW '07 Proceedings of the 29th International Conference on Software Engineering Workshops
The influence of organizational structure on software quality: an empirical case study
Proceedings of the 30th international conference on Software engineering
Extracting structural information from bug reports
Proceedings of the 2008 international working conference on Mining software repositories
A Study of the Time Dependence of Code Changes
WCRE '09 Proceedings of the 2009 16th Working Conference on Reverse Engineering
Characterizing the roles of classes and their fault-proneness through change metrics
Proceedings of the ACM-IEEE international symposium on Empirical software engineering and measurement
| Hi-index | 0.00 |
Failures after the release of software products are expensive and time-consuming to fix. Each of these failures has different reasons pointing into different portions of code. We conduct a retrospective analysis on bugs reported after beta release of Eclipse versions. Our objective is to investigate what went wrong during the development process. We identify six in-process metrics that have explanatory effects on beta-release bugs. We conduct statistical analyses to check relationships between files and metrics. Our results show that files with beta-release bugs have different characteristics in terms of in-process metrics. Those bugs are specifically concentrated on Eclipse files with little activity: few edits by few committers. We suggest that in-process metrics should be investigated individually to identify beta-release bugs. Companies may benefit from such a retrospective analysis to understand characteristics of failures. Corrective actions can be taken earlier in the process to avoid similar failures in future releases.