Applying Code Inspection to Spreadsheet Testing
The DOI matches its Crossref record; 4 of the 4 references it cites were found in a registry or an index.
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.
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
Reason, J. (1990) · doi:10.1017/cbo9781139062367 · Cited by 5,108
Calibration of probabilities: the state of the art to 1980
Lichtenstein, S., Fischhoff, B., & Phillips, L. D. (1982) · Judgment under Uncertainty · doi:10.1017/cbo9780511809477.023 · Cited by 1,967
The problems of flexibility, fluency, and speed-accuracy trade-off in skilled behavior
MacKay, D. G. (1982) · Psychological Review · doi:10.1037/0033-295x.89.5.483 · Cited by 490
Lichtenstein, S., & Fischhoff, B. (1980) · Organizational Behavior and Human Performance · doi:10.1016/0030-5073(80)90052-5 · Cited by 375
Cited by
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
“Other techniques aimed at reducing the occurrence of errors in spreadsheets include code inspection [279], refactoring [42], and adoption of better spreadsheet design practices [82], [83].”
MethodWhat we know about spreadsheet errors
Panko, R. R. (1998) · Journal of Organizational and End User Computing · doi:10.4018/joeuc.1998040102 · Cited by 464
Self-citationSpreadsheet Errors: What We Know. What We Think We Can Do
Panko, R. R. (2008) · arXiv · doi:10.48550/arxiv.0802.3457 · Cited by 107
Self-citationTen simple rules for building and maintaining a responsible data science workflow
Stoudt, S., Jernite, Y., Marshall, B., Marwick, B., Sharan, M., Whitaker, K., & Danchev, V. (2024) · PLOS Computational Biology · doi:10.1371/journal.pcbi.1012232 · Cited by 11
Metadata
- Authors
- Panko, R. R.
- Venue
- Journal of Management Information Systems
- Publisher
- Informa UK Limited
- Published
- 1999-09
- Volume
- 16
- Issue
- 2
- Pages
- 159-176
- ISSN
- 0742-1222 (ISSN-L)
- 1557-928X
- OpenAlex
- W93717786
- Cited by
- 89
- References
- 4
- FWCI
- 1.60
- 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
How to cite
Cite CoChat for the checks on this page, and the paper for its own findings.
- This page
- CoChat. (2026). Citation check: Applying Code Inspection to Spreadsheet Testing. https://app.cochat.ai/papers/10.1080/07421222.1999.11518250
- The paper
- Panko, R. R. (1999). Applying Code Inspection to Spreadsheet Testing. Journal of Management Information Systems. https://doi.org/10.1080/07421222.1999.11518250
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.