The DOI matches its Crossref record; 23 of the 23 references it cites were found in a registry or an index.
Does code decay? Assessing the evidence from change management data
Abstract
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. 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.
Overview
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Self-check
Percentages, sums and reported differences re-computed from the paper’s own numbers.
The self-check needs the paper’s full text.
Citations
Cites
Local Polynomial Modelling and its Applications
Fan, J., & Gijbels, I. (1994) · Springer eBooks · doi:10.1007/978-1-4899-3150-4 · Cited by 2,849
Wand, M. P., & Jones, M. C. (1995) · Springer eBooks · doi:10.1007/978-1-4899-4493-1 · Cited by 2,663
Local Polynomial Modelling and its Applications
Copeland, K. A. F. (1997) · Journal of Quality Technology · doi:10.1080/00224065.1997.11979762 · Cited by 1,195
A Methodology for Collecting Valid Software Engineering Data
Basili, V. R., & Weiss, D. M. (1984) · IEEE Transactions on Software Engineering · doi:10.1109/tse.1984.5010301 · Cited by 1,149
Local Polynomial Modelling and Its Applications
Fan, J., & Gijbels, I. (2018) · Routledge eBooks · doi:10.1201/9780203748725 · Cited by 1,038
Program Evolution: Processes of Software Change
Lehman, M. M., & Belady, L. A. (1985) · CERN Document Server (European Organization for Nuclear Research) · Cited by 809
Wand, M. P., & Jones, M. C. (1994) · Chapman & Hall/CRC eBooks · doi:10.1201/b14876 · Cited by 763
Predicting fault incidence using software change history
Graves, T. L., Karr, A. F., Marron, J. S., & Siy, H. (2000) · IEEE Transactions on Software Engineering · doi:10.1109/32.859533 · Cited by 753
Self-citationSoftware errors and complexity: an empirical investigation0
Basili, V. R., & Perricone, B. T. (1984) · Communications of the ACM · doi:10.1145/69605.2085 · Cited by 634
SiZer for Exploration of Structures in Curves
Chaudhuri, P., & Marron, J. S. (1999) · Journal of the American Statistical Association · doi:10.1080/01621459.1999.10474186 · Cited by 591
Self-citationA model of large program development
Belady, L. A., & Lehman, M. M. (1976) · IBM Systems Journal · doi:10.1147/sj.153.0225 · Cited by 476
Swanson, E. B. (1976) · doi:10.5555/800253.807723 · Cited by 444
Parnas, D. L. (2002) · Proceedings of 16th International Conference on Software Engineering · doi:10.1109/icse.1994.296790 · Cited by 369
Predicting fault-prone software modules in telephone switches
Ohlsson, N., & Alberg, H. (1996) · IEEE Transactions on Software Engineering · doi:10.1109/32.553637 · Cited by 346
Software complexity: Measures and methods
Zuse, H. (1991) · Medical Entomology and Zoology · Cited by 328
Software Complexity: Measures and Methods
Zuse, H. (1991) · De Gruyter eBooks · doi:10.1515/9783110866087 · Cited by 201
Parallel changes in large-scale software development: an observational case study
Perry, D. E., Siy, H. P., & Votta, L. G. (2001) · ACM Transactions on Software Engineering and Methodology · doi:10.1145/383876.383878 · Cited by 157
SiZer for Exploration of Structures in Curves
Chaudhuri, P., & Marron, J. S. (1999) · Journal of the American Statistical Association · doi:10.2307/2669996 · Cited by 138
Self-citationUnderstanding Software Maintenance Work
Bendifallah, S. (1987) · IEEE Transactions on Software Engineering · doi:10.1109/tse.1987.233162 · Cited by 108
Status report on software measurement
Pfleeger, S. L., Jeffery, R., Curtis, B., & Kitchenham, B. A. (1997) · IEEE Software · doi:10.1109/52.582973 · Cited by 95
Managing Software Engineering Projects: A Social Analysis
Scacchi, W. (1984) · IEEE Transactions on Software Engineering · doi:10.1109/tse.1984.5010198 · Cited by 94
Lehman, M. M. (1984) · Information Processing & Management · doi:10.1016/0306-4573(84)90037-2 · Cited by 69
Inferring change effort from configuration management databases
Graves, T., & Mockus, A. (2002) · IEEE International Software Metrics Symposium (METRICS) · doi:10.1109/metric.1998.731253 · Cited by 65
Self-citation
Cited by
An empirical study of speed and communication in globally distributed software development
Herbsleb, J. D., & Mockus, A. (2003) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2003.1205177 · Cited by 997
Self-citationKnowledge management in software engineering
Rus, I., & Lindvall, M. (2002) · IEEE Software · doi:10.1109/ms.2002.1003450 · Cited by 742
MacCormack, A., Rusnak, J., & Baldwin, C. Y. (2006) · Management Science · doi:10.1287/mnsc.1060.0552 · Cited by 718
An overview of JML tools and applications
Burdy, L., Cheon, Y., Cok, D. R., Ernst, M. D., Kiniry, J. R., Leavens, G. T., Leino, K. R. M., & Poll, E. (2005) · International Journal on Software Tools for Technology Transfer · doi:10.1007/s10009-004-0167-4 · Cited by 714
Predicting faults using the complexity of code changes
Hassan, A. E. (2009) · 2009 IEEE 31st International Conference on Software Engineering · doi:10.1109/icse.2009.5070510 · Cited by 708
Metadata
- Authors
- Eick, S. G., Graves, T. L., Karr, A. F., Marron, J. S., & Mockus, A.
- Venue
- IEEE Transactions on Software Engineering
- Published
- 2001
- Volume
- 27
- Issue
- 1
- Pages
- 1-12
- ISSN
- 0098-5589 (ISSN-L)
- OpenAlex
- W2151191515
- Cited by
- 636
- References
- 23
- FWCI
- 83.65
- Type
- journal article
- Language
- en
- Open access
- closed
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review
Data sources
Bibliographic data: Semantic Scholar, OpenAlex, Crossref.
Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).
Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.