The DOI matches its Crossref record; 20 of the 20 references it cites were found in a registry or an index.
Predicting fault incidence using software change history
Abstract
This paper is an attempt to understand the processes by which software ages. We define code to be aged or decayed if its structure makes it unnecessarily difficult to understand or change and we measure the extent of decay by counting the number of faults in code in a period of time. Using change management data from a very large, long-lived software system, we explore the extent to which measurements from the change history are successful in predicting the distribution over modules of these incidences of faults. In general, process measures based on the change history are more useful in predicting fault rates than product metrics of the code: For instance, the number of times code has been changed is a better indication of how many faults it will contain than is its length. We also compare the fault rates of code of various ages, finding that if a module is, on the average, a year older than an otherwise similar module, the older module will have roughly a third fewer faults. Our most successful model measures the fault potential of a module as the sum of contributions from all of the times the module has been changed, with large, recent changes receiving the most weight.
Overview
The claims and statistics of this paper haven’t been checked yet.
Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.
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
An Introduction to the Bootstrap
Efron, B., & Tibshirani, R. J. (1994) · doi:10.1201/9780429246593 · Cited by 40,500
An Introduction to the Bootstrap
Efron, B., & Tibshirani, R. J. (1993) · doi:10.1007/978-1-4899-4541-9 · Cited by 21,230
(2005) · Statistics for Biology and Health · doi:10.1007/0-387-27255-0_9 · Cited by 20,133
McCullagh, P., & Nelder, J. A. (1989) · doi:10.1007/978-1-4899-3242-6 · Cited by 16,836
McCabe, T. J. (1976) · IEEE Transactions on Software Engineering · doi:10.1109/tse.1976.233837 · Cited by 6,059
Halstead, M. H. (1977) · CERN Document Server (European Organization for Nuclear Research) · Cited by 2,930
Halstead, M. H. (1977) · CERN Document Server (European Organization for Nuclear Research) · Cited by 2,339
Jelinski, Z., & Moranda, P. B. (1972) · Elsevier eBooks · doi:10.1016/b978-0-12-266950-7.50028-1 · Cited by 1,070
Program Evolution: Processes of Software Change
Lehman, M. M., & Belady, L. A. (1985) · CERN Document Server (European Organization for Nuclear Research) · Cited by 809
Pham, H. (1999) · Wiley Encyclopedia of Electrical and Electronics Engineering · doi:10.1002/047134608x.w6952 · Cited by 737
The source code control system
Rochkind, M. J. (1975) · IEEE Transactions on Software Engineering · doi:10.1109/tse.1975.6312866 · Cited by 708
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
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
Identifying Error-Prone Software—An Empirical Study
Shen, V. Y., Yu, T.-J., Thebaut, S. M., & Paulsen, L. R. (1985) · IEEE Transactions on Software Engineering · doi:10.1109/tse.1985.232222 · Cited by 209
Software Complexity: Measures and Methods
Zuse, H. (1991) · De Gruyter eBooks · doi:10.1515/9783110866087 · Cited by 201
Reexamining the fault density component size connection
Hatton, L. (1997) · IEEE Software · doi:10.1109/52.582978 · Cited by 162
Remoortere, P. V. (1979) · Mathematics and Computers in Simulation · doi:10.1016/0378-4754(79)90027-2 · Cited by 142
An Experiment in Software Error Data Collection and Analysis
Schneidewind, N. F., & Hoffmann, H.-M. (1979) · IEEE Transactions on Software Engineering · doi:10.1109/tse.1979.234188 · Cited by 126
Regression modelling of software quality: empirical investigation
Munson, J. C., & Khoshgoftaar, Y. M. (1990) · Information and Software Technology · doi:10.1016/0950-5849(90)90109-5 · Cited by 90
Cited by
A Systematic Literature Review on Fault Prediction Performance in Software Engineering
Hall, T., Beecham, S., Bowes, D., Gray, D., & Counsell, S. (2012) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2011.103 · Cited by 1,154
The Daikon system for dynamic detection of likely invariants
Ernst, M. D., Perkins, J. H., Guo, P. J., McCamant, S., Pacheco, C., Tschantz, M. S., & Xiao, C. (2007) · Science of Computer Programming · doi:10.1016/j.scico.2007.01.015 · Cited by 1,080
Mining version histories to guide software changes
Zimmermann, T., Zeller, A., Weissgerber, P., & Diehl, S. (2005) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2005.72 · Cited by 856
Use of relative code churn measures to predict system defect density
Nagappan, N., & Ball, T. (2005) · Proceedings of the 27th international conference on Software engineering - ICSE '05 · doi:10.1145/1062455.1062514 · Cited by 775
Predicting Defects for Eclipse
Zimmermann, T., Premraj, R., & Zeller, A. (2007) · Third International Workshop on Predictor Models in Software Engineering (PROMISE'07: ICSE Workshops 2007) · doi:10.1109/promise.2007.10 · Cited by 753
Metadata
- Authors
- Graves, T. L., Karr, A. F., Marron, J. S., & Siy, H.
- Venue
- IEEE Transactions on Software Engineering
- Published
- 2000-07
- Volume
- 26
- Issue
- 7
- Pages
- 653-661
- ISSN
- 0098-5589 (ISSN-L)
- OpenAlex
- W2147105902
- Cited by
- 753
- References
- 20
- FWCI
- 31.42
- 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.