The DOI matches its Crossref record.
Design and code inspections to reduce errors in program development
Abstract
We can summarize the discussion of design and code inspections and process control in developing programs as follows: 1. Describe the program development process in terms of operations, and define exit criteria which must be satisfied for completion of each operation. 2. Separate the objectives of the inspection process operations to keep the inspection team focused on one objective at a time: Operation Overview Preparation Inspection Rework Follow-up Objective Communications/education Education Find errors Fix errors Ensure all fixes are applied correctly 3. Classify errors by type, and rank frequency of occurrence of types. Identify which types to spend most time looking for in the inspection. 4. Describe how to look for presence of error types. 5. Analyze inspection results and use for constant process improvement (until process averages are reached and then use for process control).
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
Cited by
Data Mining Static Code Attributes to Learn Defect Predictors
Menzies, T., Greenwald, J., & Frank, A. (2007) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2007.256941 · Cited by 1,215
Programs, life cycles, and laws of software evolution
Lehman, M. M. (1980) · Proceedings of the IEEE · doi:10.1109/proc.1980.11805 · Cited by 1,181
Introduction to Software Architecture
(2009) · Advanced Topics in Science and Technology in China · doi:10.1007/978-3-540-74343-9_1 · Cited by 1,099
The walkthrough method: An approach to the study of apps
Light, B., Burgess, J., & Duguay, S. (2018) · New Media & Society · doi:10.1177/1461444816675438 · Cited by 1,047
On the relative value of cross-company and within-company data for defect prediction
Turhan, B., Menzies, T., Bener, A. B., & Di Stefano, J. (2009) · Empirical Software Engineering · doi:10.1007/s10664-008-9103-7 · Cited by 725
Best Practices for Scientific Computing
Wilson, G., Aruliah, D. A., Brown, C. T., Chue Hong, N. P., Davis, M., Guy, R. T., Haddock, S. H. D., Huff, K. D., Mitchell, I. M., Plumbley, M. D., et al. (2014) · PLoS Biology · doi:10.1371/journal.pbio.1001745 · Cited by 723
Understanding and controlling software costs
Boehm, B. W., & Papaccio, P. N. (1988) · IEEE Transactions on Software Engineering · doi:10.1109/32.6191 · Cited by 667
Expectations, outcomes, and challenges of modern code review
Bacchelli, A., & Bird, C. (2013) · 2013 35th International Conference on Software Engineering (ICSE) · doi:10.1109/icse.2013.6606617 · Cited by 650
Advances in software inspections
Fagan, M. E. (1986) · IEEE Transactions on Software Engineering · doi:10.1109/tse.1986.6312976 · Cited by 630
Self-citationManadhata, P. K., & Wing, J. M. (2011) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2010.60 · Cited by 625
Case studies for method and tool evaluation
Kitchenham, B., Pickard, L., & Pfleeger, S. L. (1995) · IEEE Software · doi:10.1109/52.391832 · Cited by 601
Verifying and Validating Software Requirements and Design Specifications
Boehm, B. W. (1984) · IEEE Software · doi:10.1109/ms.1984.233702 · Cited by 513
Identifying reasons for software changes using historic databases
Mockus, & Votta (2000) · Proceedings 2000 International Conference on Software Maintenance · doi:10.1109/icsm.2000.883028 · Cited by 472
Defect prediction from static code features: current results, limitations, new approaches
Menzies, T., Milton, Z., Turhan, B., Cukic, B., Jiang, Y., & Bener, A. (2010) · Automated Software Engineering · doi:10.1007/s10515-010-0069-5 · Cited by 466
A method of programming measurement and estimation
Walston, C. E., & Felix, C. P. (1977) · IBM Systems Journal · doi:10.1147/sj.161.0054 · Cited by 462
Validation, Verification, and Testing of Computer Software
Adrion, W. R., Branstad, M. A., & Cherniavsky, J. C. (1982) · ACM Computing Surveys · doi:10.1145/356876.356879 · Cited by 426
The empirical investigation of Perspective-Based Reading
Basili, V. R., Green, S., Laitenberger, O., Lanubile, F., Shull, F., S�rumg�rd, S., & Zelkowitz, M. V. (1996) · Empirical Software Engineering · doi:10.1007/bf00368702 · Cited by 412
Java quality assurance by detecting code smells
van Emden, E., & Moonen, L. (2003) · Ninth Working Conference on Reverse Engineering, 2002. Proceedings. · doi:10.1109/wcre.2002.1173068 · Cited by 379
McIntosh, S., Kamei, Y., Adams, B., & Hassan, A. E. (2014) · Proceedings of the 11th Working Conference on Mining Software Repositories · doi:10.1145/2597073.2597076 · Cited by 348
Improving the reliability of commodity operating systems
Swift, M. M., Bershad, B. N., & Levy, H. M. (2005) · ACM Transactions on Computer Systems · doi:10.1145/1047915.1047919 · Cited by 338
An empirical study of the impact of modern code review practices on software quality
McIntosh, S., Kamei, Y., Adams, B., & Hassan, A. E. (2016) · Empirical Software Engineering · doi:10.1007/s10664-015-9381-9 · Cited by 332
Deissenboeck, F., & Pizka, M. (2006) · Software Quality Journal · doi:10.1007/s11219-006-9219-1 · Cited by 315
Convergent contemporary software peer review practices
Rigby, P. C., & Bird, C. (2013) · Proceedings of the 2013 9th Joint Meeting on Foundations of Software Engineering · doi:10.1145/2491411.2491444 · Cited by 311
Software Reliability—Status and Perspectives
Ramamoorthy, C. V., & Bastani, F. B. (1982) · IEEE Transactions on Software Engineering · doi:10.1109/tse.1982.235728 · Cited by 296
Modern code review: a case study at google
Sadowski, C., Söderberg, E., Church, L., Sipko, M., & Bacchelli, A. (2018) · Proceedings of the 40th International Conference on Software Engineering: Software Engineering in Practice · doi:10.1145/3183519.3183525 · Cited by 280
Heterogeneous Defect Prediction
Nam, J., Fu, W., Kim, S., Menzies, T., & Tan, L. (2018) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2017.2720603 · Cited by 277
Software inspections: an effective verification process
Ackerman, A. F., Buchwald, L. S., & Lewski, F. H. (1989) · IEEE Software · doi:10.1109/52.28121 · Cited by 276
Management of Large Software Development Efforts
Zmud, R. W. (1980) · MIS Quarterly · doi:10.2307/249336 · Cited by 271
A controlled experiment in program testing and code walkthroughs/inspections
Myers, G. J. (1978) · Communications of the ACM · doi:10.1145/359588.359602 · Cited by 257
(2014) · doi:10.1145/2597073.2597082 · Cited by 252
Code review quality: how developers see it
Kononenko, O., Baysal, O., & Godfrey, M. W. (2016) · Proceedings of the 38th International Conference on Software Engineering · doi:10.1145/2884781.2884840 · Cited by 183
Agile Software Development Methodologies and Practices
Williams, L. (2010) · Advances in Computers · doi:10.1016/s0065-2458(10)80001-4 · Cited by 159
Understanding and improving technology transfer in software engineering
Pfleeger, S. L. (1999) · Journal of Systems and Software · doi:10.1016/s0164-1212(99)00031-x · Cited by 128
CORE: Automating Review Recommendation for Code Changes
Siow, J. K., Gao, C., Fan, L., Chen, S., & Liu, Y. (2020) · 2020 IEEE 27th International Conference on Software Analysis, Evolution and Reengineering (SANER) · doi:10.1109/saner48275.2020.9054794 · Cited by 56
The Value of Software Documentation Quality
Plosch, R., Dautovic, A., & Saft, M. (2014) · 2014 14th International Conference on Quality Software · doi:10.1109/qsic.2014.22 · Cited by 44
Empirical studies of requirements validation techniques
Raja, U. A. (2009) · 2009 2nd International Conference on Computer, Control and Communication · doi:10.1109/ic4.2009.4909209 · Cited by 24
Metadata
- Authors
- Fagan, M. E.
- Venue
- IBM Systems Journal
- Publisher
- IBM
- Published
- 1976
- Volume
- 15
- Issue
- 3
- Pages
- 182-211
- ISSN
- 0018-8670 (ISSN-L)
- OpenAlex
- W2161407365
- Cited by
- 1,492
- References
- 0
- FWCI
- 52.58
- 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.