Code churn: a measure for estimating the impact of code change

This study presents a methodology that will produce a viable fault surrogate. The focus of the effort is on the precise measurement of software development process and product outcomes. Tools and processes for the static measurement of the source code have been installed and made operational in a large embedded software system. Source code measurements have been gathered unobtrusively for each build in the software evolution process. The measurements are synthesized to obtain the fault surrogate. The complexity of sequential builds is compared and a new measure, code churn, is calculated. This paper demonstrates the effectiveness of code complexity churn by validating it against the testing problem reports.

[1]  Filippo Lanubile Why Software Reliability Predictions Fail , 1996, IEEE Softw..

[2]  J. C. Munson,et al.  Software risk assessment through software measurement and modeling , 1998, 1998 IEEE Aerospace Conference Proceedings (Cat. No.98TH8339).

[3]  John C. Munson Software measurement: Problems and practice , 1995, Ann. Softw. Eng..

[4]  Robert L. Glass,et al.  Science and substance: a challenge to software engineers , 1994, IEEE Software.

[5]  Taghi M. Khoshgoftaar,et al.  The Detection of Fault-Prone Programs , 1992, IEEE Trans. Software Eng..

[6]  Taghi M. Khoshgoftaar,et al.  Early Quality Prediction: A Case Study in Telecommunications , 1996, IEEE Softw..

[7]  Taghi M. Khoshgoftaar,et al.  Predicting Software Development Errors Using Software Complexity Metrics , 1990, IEEE J. Sel. Areas Commun..

[8]  John C. Munson Software faults, software failures and software reliability modeling , 1996, Inf. Softw. Technol..

[9]  John C. Munson,et al.  Measuring software evolution , 1996, Proceedings of the 3rd International Software Metrics Symposium.