The DOI matches its Crossref record; 3 of the 3 references it cites were found in a registry or an index.
A model of large program development
Abstract
Currently, the process of large-scale program development and maintenance appears to be unpredictable; its costs are high and its output is a fragile product. Clearly, one should try to reach beyond understanding and attempt to change the process for the better.
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
The Statistical Analysis of Series of Events.
Huitson, A., Cox, D. R., & Lewis, P. A. W. (1966) · The Statistician · doi:10.2307/2986878 · Cited by 1,884
Notes on Structured Programming
Dijkstra, E. W. (1970) · TU/e Research Portal · doi:10.26153/tsw/53177 · Cited by 824
Dijkstra, E. W. (1972) · Communications of the ACM · doi:10.1145/355604.361591 · Cited by 705
Cited by
Programs, life cycles, and laws of software evolution
Lehman, M. M. (1980) · Proceedings of the IEEE · doi:10.1109/proc.1980.11805 · Cited by 1,181
Self-citationDoes code decay? Assessing the evidence from change management data
Eick, S. G., Graves, T. L., Karr, A. F., Marron, J. S., & Mockus, A. (2001) · IEEE Transactions on Software Engineering · doi:10.1109/32.895984 · Cited by 636
Software 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
Characteristics of application software maintenance
Lientz, B. P., Swanson, E. B., & Tompkins, G. E. (1978) · Communications of the ACM · doi:10.1145/359511.359522 · Cited by 431
Predicting risk of software changes
Mockus, A., & Weiss, D. M. (2002) · Bell Labs Technical Journal · doi:10.1002/bltj.2229 · Cited by 429
Program understanding: Challenge for the 1990s
Corbi, T. A. (1989) · IBM Systems Journal · doi:10.1147/sj.282.0294 · Cited by 388
Curating GitHub for engineered software projects
Munaiah, N., Kroh, S., Cabrey, C., & Nagappan, M. (2017) · Empirical Software Engineering · doi:10.1007/s10664-017-9512-6 · Cited by 365
“We can trace 36 such analysis all the way back to the 1970s, when Belady and Lehman (1976) proposed Lehman’s Laws 37 of software evolution.”
BackgroundInfluentialAn empirical approach to studying software evolution
Kemerer, C. F., & Slaughter, S. (1999) · IEEE Transactions on Software Engineering · doi:10.1109/32.799945 · Cited by 328
Software Reliability—Status and Perspectives
Ramamoorthy, C. V., & Bastani, F. B. (1982) · IEEE Transactions on Software Engineering · doi:10.1109/tse.1982.235728 · Cited by 296
(2012) · doi:10.1145/2393596.2393655 · Cited by 239
An Empirical Study of RefactoringChallenges and Benefits at Microsoft
Kim, M., Zimmermann, T., & Nagappan, N. (2014) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2014.2318734 · Cited by 231
“Many believe that a lack of refactoring incurs technical debt to be repaid in the form of increased maintenance cost [2].”
BackgroundHow do professionals perceive legacy systems and software modernization?
Khadka, R., Batlajery, B. V., Saeidi, A. M., Jansen, S., & Hage, J. (2014) · Proceedings of the 36th International Conference on Software Engineering · doi:10.1145/2568225.2568318 · Cited by 111
“The seminal work in this area is the first law of continuing change by Belady & Lehman [7], followed by the concept of preventative maintenance [29].”
BackgroundTheory-oriented software engineering
Stol, K.-J., & Fitzgerald, B. (2015) · Science of Computer Programming · doi:10.1016/j.scico.2014.11.010 · Cited by 63
Modeling coordination in software construction: An analytical approach
Koushik, M. V., & Mookerjee, V. S. (1995) · Information Systems Research · doi:10.1287/isre.6.3.220 · Cited by 47
Williams, B. J., & Carver, J. C. (2014) · Empirical Software Engineering · doi:10.1007/s10664-012-9223-y · Cited by 8
Metadata
- Authors
- Belady, L. A., & Lehman, M. M.
- Venue
- IBM Systems Journal
- Publisher
- IBM
- Published
- 1976
- Volume
- 15
- Issue
- 3
- Pages
- 225-252
- ISSN
- 0018-8670 (ISSN-L)
- OpenAlex
- W2143232930
- Cited by
- 476
- References
- 3
- FWCI
- 44.70
- 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.