Does code decay? Assessing the evidence from change management data

doi:10.1109/32.895984

Does code decay? Assessing the evidence from change management data

2001-01-01

344

PRE

AI

DOI：10.1109/32.895984

Original

Original request for help

Save

Abstract

En 中文

A central feature of the evolution of large software systems is that change-which is necessary to add new functionality, accommodate new hardware, and repair faults-becomes increasingly difficult over time. In this paper, we approach this phenomenon, which we term code decay, scientifically and statistically. We define code decay and propose a number of measurements (code decay indices) on software and on the organizations that produce it, that serve as symptoms, risk factors, and predictors of decay. Using an unusually rich data set (the fifteen-plus year change history of the millions of lines of software for a telephone switching system), we find mixed, but on the whole persuasive, statistical evidence of code decay, which is corroborated by developers of the code. Suggestive indications that perfective maintenance can retard code decay are also discussed.

Keywords:

software maintenance

metrics

statistical analysis

fault potential

span of changes

effort modeling

Does code decay? Assessing the evidence from change management data

Abstract

AI Summary

Journal

Organization