The DOI matches its Crossref record; 16 of the 16 references it cites were found in a registry or an index.
The detection of fault-prone programs
Abstract
The use of the statistical technique of discriminant analysis as a tool for the detection of fault-prone programs is explored. A principal-components procedure was employed to reduce simple multicollinear complexity metrics to uncorrelated measures on orthogonal complexity domains. These uncorrelated measures were then used to classify programs into alternate groups, depending on the metric values of the program. The criterion variable for group determination was a quality measure of faults or changes made to the programs. The discriminant analysis was conducted on two distinct data sets from large commercial systems. The basic discriminant model was constructed from deliberately biased data to magnify differences in metric values between the discriminant groups. The technique was successful in classifying programs with a relatively low error rate. While the use of linear regression models has produced models of limited value, this procedure shows great promise for use in the detection of program modules with potential for faults.>
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
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 3,639
Halstead, M. H. (1977) · CERN Document Server (European Organization for Nuclear Research) · Cited by 2,339
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 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
Self-citationIdentifying 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
An analysis of errors and their causes in system programs
Endres, A. (1975) · ACM SIGPLAN Notices · doi:10.1145/390016.808455 · Cited by 200
Number of Faults per Line of Code
Lipow, M. (1982) · IEEE Transactions on Software Engineering · doi:10.1109/tse.1982.235579 · Cited by 151
Lind, R., & Vairavan, K. (1989) · IEEE Transactions on Software Engineering · doi:10.1109/32.24715 · Cited by 117
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 100
Self-citation
Cited by
A validation of object-oriented design metrics as quality indicators
Basili, V. R., Briand, L. C., & Melo, W. L. (1996) · IEEE Transactions on Software Engineering · doi:10.1109/32.544352 · Cited by 1,726
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
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 Survey on Software Fault Localization
Wong, W. E., Gao, R., Li, Y., Abreu, R., & Wotawa, F. (2016) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2016.2521368 · Cited by 1,110
“Unfortunately, this has also resulted in more software bugs, which often lead to execution failures with huge losses [260], [275], [365].”
BackgroundA 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
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
“It has been used as a tool for the detection of fau lt-prone programs [13, 14, 18].”
MethodPredicting the location and number of faults in large software systems
Ostrand, T. J., Weyuker, E. J., & Bell, R. M. (2005) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2005.49 · Cited by 720
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
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
Cross-project defect prediction: a large scale experiment on data vs. domain vs. process
Zimmermann, T., Nagappan, N., Gall, H. C., Giger, E., & Murphy, B. (2009) · Zurich Open Repository and Archive (University of Zurich) · doi:10.5167/uzh-25785 · Cited by 694
Test case prioritization: an empirical study
Rothermel, G., Untch, R. H., Chu, C., & Harrold, M. J. (1999) · Proceedings IEEE International Conference on Software Maintenance - 1999 (ICSM'99). 'Software Maintenance for Business Change' (Cat. No.99CB36360) · doi:10.1109/icsm.1999.792604 · Cited by 625
Predicting defects using network analysis on dependency graphs
Zimmermann, T., & Nagappan, N. (2008) · Proceedings of the 13th international conference on Software engineering - ICSE '08 · doi:10.1145/1368088.1368161 · Cited by 580
Predicting defect-prone software modules using support vector machines
Elish, K. O., & Elish, M. O. (2008) · Journal of Systems and Software · doi:10.1016/j.jss.2007.07.040 · Cited by 525
Software measurement: a necessary scientific basis
Fenton, N. (1994) · IEEE Transactions on Software Engineering · doi:10.1109/32.268921 · Cited by 501
Quality Management in Systems Development: An Organizational System Perspective1
Ravichandran, T., & Rai, A. (2000) · MIS Quarterly · doi:10.2307/3250967 · Cited by 442
Using metrics to evaluate software system maintainability
Coleman, D., Ash, D., Lowther, B., & Oman, P. (1994) · Computer · doi:10.1109/2.303623 · Cited by 431
The confounding effect of class size on the validity of object-oriented metrics
El Emam, K., Benlarbi, S., Goel, N., & Rai, S. N. (2001) · IEEE Transactions on Software Engineering · doi:10.1109/32.935855 · Cited by 422
A General Software Defect-Proneness Prediction Framework
Song, Q., Jia, Z., Shepperd, M., Ying, S., & Liu, J. (2011) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2010.90 · Cited by 374
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 defect prediction using Bayesian networks
Okutan, A., & Yıldız, O. T. (2014) · Empirical Software Engineering · doi:10.1007/s10664-012-9218-8 · Cited by 330
Fenton, N. E., & Neil, M. (2000) · Proceedings of the Conference on The Future of Software Engineering · doi:10.1145/336512.336588 · Cited by 317
Bennin, K. E., Keung, J., Phannachitta, P., Monden, A., & Mensah, S. (2018) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2017.2731766 · Cited by 298
On the value of static analysis for fault detection in software
Zheng, J., Williams, L., Nagappan, N., Snipes, W., Hudepohl, J. P., & Vouk, M. A. (2006) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2006.38 · Cited by 283
Static analysis tools as early indicators of pre-release defect density
Nagappan, N., & Ball, T. (2005) · Proceedings of the 27th international conference on Software engineering - ICSE '05 · doi:10.1145/1062455.1062558 · Cited by 272
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
Ostrand, T. J., Weyuker, E. J., & Bell, R. M. (2004) · Proceedings of the 2004 ACM SIGSOFT international symposium on Software testing and analysis · doi:10.1145/1007512.1007524 · Cited by 269
Can developer-module networks predict failures?
Pinzger, M., Nagappan, N., & Murphy, B. (2008) · Proceedings of the 16th ACM SIGSOFT International Symposium on Foundations of software engineering · doi:10.1145/1453101.1453105 · Cited by 256
Code churn: a measure for estimating the impact of code change
Munson, J. C., & Elbaum, S. G. (2002) · Proceedings. International Conference on Software Maintenance (Cat. No. 98CB36272) · doi:10.1109/icsm.1998.738486 · Cited by 153
Self-citation
Metadata
- Authors
- Munson, J. C., & Khoshgoftaar, T. M.
- Venue
- IEEE Transactions on Software Engineering
- Published
- 1992-05
- Volume
- 18
- Issue
- 5
- Pages
- 423-433
- ISSN
- 0098-5589 (ISSN-L)
- OpenAlex
- W2123127356
- Cited by
- 442
- References
- 16
- FWCI
- 37.55
- 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.