The DOI matches its Crossref record; 17 of the 17 references it cites were found in a registry or an index.
Predicting the location and number of faults in large software systems
Abstract
Advance knowledge of which files in the next release of a large software system are most likely to contain the largest numbers of faults can be a very valuable asset. To accomplish this, a negative binomial regression model has been developed and used to predict the expected number of faults in each file of the next release of a system. The predictions are based on the code of the file in the current release, and fault and modification history of the file from previous releases. The model has been applied to two large industrial systems, one with a history of 17 consecutive quarterly releases over 4 years, and the other with nine releases over 2 years. The predictions were quite accurate: for each release of the two systems, the 20 percent of the files with the highest predicted number of faults contained between 71 percent and 92 percent of the faults that were actually detected, with the overall average being 83 percent. The same model was also used to predict which files of the first system were likely to have the highest fault densities (faults per KLOC). In this case, the 20 percent of the files with the highest predicted fault densities contained an average of 62 percent of the system's detected faults. However, the identified files contained a much smaller percentage of the code mass than the files selected to maximize the numbers of faults. The model was also used to make predictions from a much smaller input set that only contained fault data from integration testing and later. The prediction was again very accurate, identifying files that contained from 71 percent to 93 percent of the faults, with the average being 84 percent. Finally, a highly simplified version of the predictor selected files containing, on average, 73 percent and 74 percent of the faults for the two systems.
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
(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
Prioritizing test cases for regression testing
Rothermel, G., Untch, R. H., Chu, C., & Harrold, M. J. (2001) · IEEE Transactions on Software Engineering · doi:10.1109/32.962562 · Cited by 1,338
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
Quantitative analysis of faults and failures in a complex software system
Fenton, N. E., & Ohlsson, N. (2000) · IEEE Transactions on Software Engineering · doi:10.1109/32.879815 · Cited by 699
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
The detection of fault-prone programs
Munson, J. C., & Khoshgoftaar, T. M. (1992) · IEEE Transactions on Software Engineering · doi:10.1109/32.135775 · Cited by 442
Optimizing Preventive Service of Software Products
Adams, E. N. (1984) · IBM Journal of Research and Development · doi:10.1147/rd.281.0002 · Cited by 373
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
Robust Prediction of Fault-Proneness by Random Forests
Guo, L., Ma, Y., Cukic, B., & Singh, H. (2005) · 15th International Symposium on Software Reliability Engineering · doi:10.1109/issre.2004.35 · Cited by 271
The distribution of faults in a large industrial software system
Ostrand, T. J., & Weyuker, E. J. (2002) · ACM SIGSOFT Software Engineering Notes · doi:10.1145/566171.566181 · Cited by 246
Self-citationEarly quality prediction: a case study in telecommunications
Khoshgoftaar, T. M., Allen, E. B., Kalaichelvan, K. S., & Goel, N. (1996) · IEEE Software · doi:10.1109/52.476287 · Cited by 200
Reexamining the fault density component size connection
Hatton, L. (1997) · IEEE Software · doi:10.1109/52.582978 · Cited by 162
The distribution of faults in a large industrial software system
Ostrand, T. J., & Weyuker, E. J. (2002) · ACM SIGSOFT Software Engineering Notes · doi:10.1145/566180.566181 · Cited by 61
Self-citationAn empirical analysis of fault persistence through software releases
Pighin, M., & Marzona, A. (2004) · International Symposium on Empirical Software Engineering · doi:10.1109/isese.2003.1237979 · Cited by 32
Using static analysis to determine where to focus dynamic testing effort
Ostrand, T. J. (2004) · doi:10.1049/ic:20040292 · Cited by 18
Self-citation
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
Mining metrics to predict component failures
Nagappan, N., Ball, T., & Zeller, A. (2006) · Proceedings of the 28th international conference on Software engineering · doi:10.1145/1134285.1134349 · Cited by 782
A large-scale empirical study of just-in-time quality assurance
Kamei, Y., Shihab, E., Adams, B., Hassan, A. E., Mockus, A., Sinha, A., & Ubayashi, N. (2013) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2012.70 · Cited by 715
An extensive comparison of bug prediction approaches
D'Ambros, M., Lanza, M., & Robbes, R. (2010) · 2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010) · doi:10.1109/msr.2010.5463279 · Cited by 637
Shin, Y., Meneely, A., Williams, L., & Osborne, J. A. (2011) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2010.81 · Cited by 607
Metadata
- Authors
- Ostrand, T. J., Weyuker, E. J., & Bell, R. M.
- Venue
- IEEE Transactions on Software Engineering
- Published
- 2005-04
- Volume
- 31
- Issue
- 4
- Pages
- 340-355
- ISSN
- 0098-5589 (ISSN-L)
- OpenAlex
- W2159610968
- Cited by
- 720
- References
- 17
- FWCI
- 97.68
- 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.