The DOI matches its Crossref record; 19 of the 19 references it cites were found in a registry or an index.
Predicting fault-prone software modules in telephone switches
Abstract
An empirical study was carried out at Ericsson Telecom AB to investigate the relationship between several design metrics and the number of function test failure reports associated with software modules. A tool, ERIMET, was developed to analyze the design documents automatically. Preliminary results from the study of 130 modules showed that: based on fault and design data one can satisfactorily build, before coding has started, a prediction model for identifying the most fault-prone modules. The data analyzed show that 20 percent of the most fault-prone modules account for 60 percent of all faults. The prediction model built in this paper would have identified 20 percent of the modules accounting for 47 percent of all faults. At least four design measures can alternatively be used as predictors with equivalent performance. The size (with respect to the number of lines of code) used in a previous prediction model was not significantly better than these four measures. The Alberg diagram introduced in this paper offers a way of assessing a predictor based on historical data, which is a valuable complement to linear regression when prediction data is ordinal. Applying the method described in this paper makes it possible to use measures at the design phase to predict the most fault-prone modules.
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
Statistical Methods for Psychology.
Gudgeon, A. C., & Howell, D. C. (1994) · The Statistician · doi:10.2307/2348956 · Cited by 8,278
McCabe, T. J. (1976) · IEEE Transactions on Software Engineering · doi:10.1109/tse.1976.233837 · Cited by 6,059
Nonlinear Regression Analysis and Its Applications
Bates, D. M., & Watts, D. G. (1988) · Wiley Series in Probability and Statistics · doi:10.1002/9780470316757 · Cited by 3,979
Holder, R. L., Mosteller, F., & Tukey, J. W. (1979) · Applied Statistics · doi:10.2307/2346739 · Cited by 1,676
Osborn, J. F., Mosteller, F., & Tukey, J. W. (1978) · Journal of the Royal Statistical Society. Series A (General) · doi:10.2307/2344493 · Cited by 1,446
A critique of software defect prediction models
Fenton, N. E., & Neil, M. (1999) · IEEE Transactions on Software Engineering · doi:10.1109/32.815326 · Cited by 1,040
Software Metrics. A Rigorous Approach
(1991) · Journal of Information Technology · doi:10.1177/0268396291006003-421 · Cited by 843
Operational profiles in software-reliability engineering
Musa, J. D. (1993) · IEEE Software · doi:10.1109/52.199724 · Cited by 765
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
Software complexity: Measures and methods
Zuse, H. (1991) · Medical Entomology and Zoology · Cited by 328
Science and substance: a challenge to software engineers
Fenton, N., Pfleeger, S. L., & Glass, R. L. (1994) · IEEE Software · doi:10.1109/52.300094 · Cited by 265
Empirically guided software development using metric-based classification trees
Porter, A. A., & Selby, R. W. (1990) · IEEE Software · doi:10.1109/52.50773 · Cited by 264
A critique of cyclomatic complexity as a software metric
Shepperd, M. (1988) · Software Engineering Journal · doi:10.1049/sej.1988.0003 · Cited by 240
Predicting software development errors using software complexity metrics
Khoshgoftaar, T. M., & Munson, J. C. (1990) · IEEE Journal on Selected Areas in Communications · doi:10.1109/49.46879 · Cited by 239
Software Complexity: Measures and Methods
Zuse, H. (1991) · De Gruyter eBooks · doi:10.1515/9783110866087 · Cited by 201
Decline and Fall of the American Programmer
Yourdon, E. (1992) · Medical Entomology and Zoology · Cited by 181
Myers, G. J. (1976) · Cited by 74
Design metrics: an empirical analysis
Shepperd, M. (1990) · Software Engineering Journal · doi:10.1049/sej.1990.0002 · Cited by 56
Zannetti, P. (1990) · Environmental Software · doi:10.1016/0266-9838(90)90010-4 · Cited by 9
Cited by
Lessmann, S., Baesens, B., Mues, C., & Pietsch, S. (2008) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2008.35 · Cited by 1,226
A critique of software defect prediction models
Fenton, N. E., & Neil, M. (1999) · IEEE Transactions on Software Engineering · doi:10.1109/32.815326 · Cited by 1,040
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
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
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
Metadata
- Authors
- Ohlsson, N., & Alberg, H.
- Venue
- IEEE Transactions on Software Engineering
- Published
- 1996
- Volume
- 22
- Issue
- 12
- Pages
- 886-894
- ISSN
- 0098-5589 (ISSN-L)
- OpenAlex
- W2110656807
- Cited by
- 346
- References
- 19
- FWCI
- 13.40
- 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.