A Graph Model for Software Evolution
IEEE Transactions on Software Engineering
The Detection of Fault-Prone Programs
IEEE Transactions on Software Engineering
Orthogonal Defect Classification-A Concept for In-Process Measurements
IEEE Transactions on Software Engineering - Special issue on software measurement principles, techniques, and environments
Faults, Failures, and a Metrics Revolution
IEEE Software
Software Measurement: A Necessary Scientific Basis
IEEE Transactions on Software Engineering
METRICS '96 Proceedings of the 3rd International Symposium on Software Metrics: From Measurement to Empirical Results
Code Churn: A Measure for Estimating the Impact of Code Change
ICSM '98 Proceedings of the International Conference on Software Maintenance
Determining Fault Insertion Rates for Evolving Software Systems
ISSRE '98 Proceedings of the The Ninth International Symposium on Software Reliability Engineering
Software system defect content prediction from development process and product characteristics
Software system defect content prediction from development process and product characteristics
Prioritizing test cases for regression testing
Proceedings of the 2000 ACM SIGSOFT international symposium on Software testing and analysis
Incorporating varying test costs and fault severities into test case prioritization
ICSE '01 Proceedings of the 23rd International Conference on Software Engineering
Test Case Prioritization: A Family of Empirical Studies
IEEE Transactions on Software Engineering
| Hi-index | 0.00 |
In any manufacturing environment,the fault introduction rate might be considered one of the mostmeaningful criterion to evaluate the goodness of the developmentprocess. In many investigations, the estimates of such a rateare often oversimplified or misunderstood generating unrealisticexpectations on the prediction power of regression models witha fault criterion. The computation of fault introduction ratesin software development requires accurate and consistent measurement,which translates into demanding parallel efforts for the developmentorganization. This paper presents the techniques and mechanismsthat can be implemented in a software development organizationto provide a consistent method of anticipating fault contentand structural evolution across multiple projects over time.The initial estimates of fault introduction rates can serve asa baseline against which future projects can be compared to determinewhether progress is being made in reducing the fault introductionrate, and to identify those development techniques that seemto provide the greatest reduction.