The DOI matches its Crossref record; 5 of the 5 references it cites were found in a registry or an index.
Software errors and complexity: an empirical investigation0
Open accessAbstract
An analysis of the distributions and relationships derived from the change data collected during development of a medium-scale software project produces some surprising insights into the factors influencing software development. Among these are the tradeoffs between modifying an existing module as opposed to creating a new one, and the relationship between module size and error proneness.
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
A model of large program development
Belady, L. A., & Lehman, M. M. (1976) · IBM Systems Journal · doi:10.1147/sj.153.0225 · Cited by 476
An analysis of errors and their causes in system programs
Endres, A. (1975) · ACM SIGPLAN Notices · doi:10.1145/390016.808455 · Cited by 200
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 143
Programming measurement and estimation in the software engineering laboratory
Basili, V. R., & Freburger, K. (1981) · Journal of Systems and Software · doi:10.1016/0164-1212(81)90046-7 · Cited by 99
Self-citation
Cited by
EXPERT SYSTEMS WITH APPLICATIONS
(2005) · Expert Systems with Applications · doi:10.1016/j.eswa.2004.10.010 · Cited by 1,656
The TAME Project: Towards Improvement-Oriented Software Environments
Basili, V. R., & Rombach, H. D. (2005) · Foundations of Empirical Software Engineering · doi:10.1007/3-540-27662-9_8 · Cited by 1,411
Self-citationA 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
Orthogonal defect classification-a concept for in-process measurements
Chillarege, R., Bhandari, I. S., Chaar, J. K., Halliday, M. J., Moebus, D. S., Ray, B. K., & Wong, M.-Y. (1992) · IEEE Transactions on Software Engineering · doi:10.1109/32.177364 · Cited by 792
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
Predicting 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
An empirical study of operating systems errors
Chou, A., Yang, J., Chelf, B., Hallem, S., & Engler, D. (2001) · Proceedings of the eighteenth ACM symposium on Operating systems principles · doi:10.1145/502034.502042 · Cited by 713
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
Subramanyam, R., & Krishnan, M. S. (2003) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2003.1191795 · Cited by 672
Does 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
Effects of Process Maturity on Quality, Cycle Time, and Effort in Software Product Development
Harter, D. E., Krishnan, M. S., & Slaughter, S. A. (2000) · Management Science · doi:10.1287/mnsc.46.4.451.12056 · Cited by 507
Should computer scientists experiment more?
Tichy, W. F. (1998) · Computer · doi:10.1109/2.675631 · Cited by 487
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
Predicting risk of software changes
Mockus, A., & Weiss, D. M. (2002) · Bell Labs Technical Journal · doi:10.1002/bltj.2229 · Cited by 429
Sullivan, M., & Chillarege, R. (2002) · [1991] Digest of Papers. Fault-Tolerant Computing: The Twenty-First International Symposium · doi:10.1109/ftcs.1991.146625 · Cited by 346
The road ahead for Mining Software Repositories
Hassan, A. E. (2008) · 2008 Frontiers of Software Maintenance · doi:10.1109/fosm.2008.4659248 · Cited by 337
Software complexity and maintenance costs
Banker, R. D., Datar, S. M., Kemerer, C. F., & Zweig, D. (1993) · Communications of the ACM · doi:10.1145/163359.163375 · Cited by 334
Fenton, N. E., & Neil, M. (2000) · Proceedings of the Conference on The Future of Software Engineering · doi:10.1145/336512.336588 · Cited by 317
Software Dependencies, Work Dependencies, and Their Impact on Failures
Cataldo, M., Mockus, A., Roberts, J. A., & Herbsleb, J. D. (2009) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2009.42 · 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
A critique of cyclomatic complexity as a software metric
Shepperd, M. (1988) · Software Engineering Journal · doi:10.1049/sej.1988.0003 · Cited by 240
Landman, D., Serebrenik, A., Bouwers, E., & Vinju, J. J. (2016) · Journal of Software: Evolution and Process · doi:10.1002/smr.1760 · Cited by 29
A Case Study of Measuring Degeneration of Software Architectures from a Defect Perspective
Li, Z., & Long, J. (2011) · 2011 18th Asia-Pacific Software Engineering Conference · doi:10.1109/apsec.2011.51 · Cited by 12
“In contrast, Basili and Perricone [28] adopt a stricter definition in that even if a maintainer needs to “examine” (not necessarily change) more than one component in order to “understand” how to fix it then it is designated as an interface defect.”
BackgroundMethodResultInfluential
Metadata
- Authors
- Basili, V. R., & Perricone, B. T.
- Venue
- Communications of the ACM
- Published
- 1984-01
- Volume
- 27
- Issue
- 1
- Pages
- 42-52
- ISSN
- 0001-0782 (ISSN-L)
- 1557-7317
- OpenAlex
- W2066459581
- Cited by
- 634
- References
- 5
- FWCI
- 39.05
- Type
- journal article
- Language
- en
- Open access
- bronze
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.