Applying Code Inspection to Spreadsheet Testing
- 1 September 1999
- journal article
- research article
- Published by Taylor & Francis Ltd in Journal of Management Information Systems
- Vol. 16 (2), 159-176
- https://doi.org/10.1080/07421222.1999.11518250
Abstract
In programming, reliability requires an extensive testing phase. Spreadsheet development, which has about the error rate as program development, also needs to be followed by an extensive testing phase if spreadsheets are to be reliable. In this study, sixty undergraduate MIS students code-inspected a spreadsheet seeded with eight errors. They first inspected the spreadsheet working alone. They then met in twenty groups of three to reinspect the spreadsheet together. Effort was made to prevent hasty inspection. Individual code inspection, consistent with past studies of both spreadsheet and program code inspection, caught only 63 percent of the errors. Group inspection raised this to 83 percent. However, the group phase never found new errors; it merely pooled the errors found during the individual phase by the three members. One group even “lost” an error found during the individual phase. This raises the question of whether a group code inspection phase is really necessary. Other findings were that subjects were overconfident when inspecting alone, that certain types of errors are especially difficult to detect, and that the benefits of the group phase is greatest for these difficult-to-detect types of errors.Keywords
This publication has 28 references indexed in Scilit:
- An experiment to assess the cost-benefits of code inspections in large scale software developmentIEEE Transactions on Software Engineering, 1997
- Assessing software review meetings: results of a comparative analysis of two experimental studiesIEEE Transactions on Software Engineering, 1997
- Overconfidence, base rates and outcome positivity/negativity of predicted eventsBritish Journal of Psychology, 1996
- A comparison of strategies for reducing interval overconfidence in group judgments.Journal of Applied Psychology, 1995
- Comparing detection methods for software requirements inspections: a replicated experimentIEEE Transactions on Software Engineering, 1995
- Spreadsheet Modelling Abuse: An Opportunity for OR?Journal of the Operational Research Society, 1993
- The role of error in organizing behaviourErgonomics, 1990
- Training for calibrationOrganizational Behavior and Human Performance, 1980
- Proofreading errors on the word the: New evidence on reading units.Journal of Experimental Psychology: Human Perception and Performance, 1980
- A controlled experiment in program testing and code walkthroughs/inspectionsCommunications of the ACM, 1978