Does the expert know? The reliability of predictions and confidence ratings of experts
Proceedings of the NATO Advanced Study Institute on Intelligent Decision Support on Intelligent decision support in process environments
An experimental study of people creating spreadsheets
ACM Transactions on Information Systems (TOIS)
Does every inspection need a meeting?
SIGSOFT '93 Proceedings of the 1st ACM SIGSOFT symposium on Foundations of software engineering
Software errors and complexity: an empirical investigation
Software engineering metrics I
Software inspection process
Assessing Software Review Meetings: Results of a Comparative Analysis of Two Experimental Studies
IEEE Transactions on Software Engineering
An experiment to assess different defect detection methods for software requirements inspections
ICSE '94 Proceedings of the 16th international conference on Software engineering
An Experiment to Assess the Cost-Benefits of Code Inspections in Large Scale Software Development
IEEE Transactions on Software Engineering
Hitting the wall: errors in developing and code inspecting a 'simple' spreadsheet model
Decision Support Systems
A controlled experiment in program testing and code walkthroughs/inspections
Communications of the ACM
Lessons from Three Years of Inspection Data
IEEE Software
Comparing Detection Methods for Software Requirements Inspections: A Replicated Experiment
IEEE Transactions on Software Engineering
An Experimental Study of Spreadsheet Presentation and Error Detection
HICSS '96 Proceedings of the 29th Hawaii International Conference on System Sciences Volume 2: Decision Support and Knowledge-Based Systems
Spreadsheets on Trial: A Survey of Research on Spreadsheet Risks
HICSS '96 Proceedings of the 29th Hawaii International Conference on System Sciences Volume 2: Decision Support and Knowledge-Based Systems
A Risk and Control Oriented Study of the Practices of Spreadsheet Application Developers
HICSS '96 Proceedings of the 29th Hawaii International Conference on System Sciences Volume 2: Decision Support and Knowledge-Based Systems
Spreadsheet presentation and error detection: an experimental study
Journal of Management Information Systems - Special issue: Information technology and its organizational impact
Inferring templates from spreadsheets
Proceedings of the 28th international conference on Software engineering
Type inference for spreadsheets
Proceedings of the 8th ACM SIGPLAN international conference on Principles and practice of declarative programming
UCheck: A spreadsheet type checker for end users
Journal of Visual Languages and Computing
GoalDebug: A Spreadsheet Debugger for End Users
ICSE '07 Proceedings of the 29th international conference on Software Engineering
An auditing protocol for spreadsheet models
Information and Management
Automatic detection of dimension errors in spreadsheets
Journal of Visual Languages and Computing
Testing spreadsheet accuracy theory
Information and Software Technology
Revising the Panko-Halverson taxonomy of spreadsheet errors
Decision Support Systems
Systematic evolution of model-based spreadsheet applications
Journal of Visual Languages and Computing
A Study of Help Requested Online by Spreadsheet Users
Journal of Organizational and End User Computing
Expert and Novice End-User Spreadsheet Debugging: A Comparative Study of Performance and Behaviour
Journal of Organizational and End User Computing
Hi-index | 0.00 |
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.