Hitting the wall: errors in developing and debugging a "simple" spreadsheet model

Undergraduate MIS business students developed and debugged a spreadsheet model from a word problem. This model consisted of a bid to build a wall. The problem was designed to be relatively simple and domain-free to address the concern that past spreadsheet experiments may have used problems that were too difficult or that required domain knowledge that subjects did not have. During the development phase, 72 subjects created the spreadsheet model. Even with this rather simple problem, 38% of the models contained an error. This high number of incorrect spreadsheets was not due to subjects making many errors. They only made 0.4 errors per spreadsheet. In addition, their cell error rate (CER) was only 1.7%, meaning that only 1.7% of their cells contained errors. Unfortunately, spreadsheets tend to have long cascades of cells leading to the bottom line. This means that even tiny cell error rates will multiply into high rates of bottom-line errors. In a debugging phase, subjects tried to debug their own models. Of 19 subjects with incorrect models who did the debugging part of the experiment, only three (16%) found and corrected their errors. So even with a relatively simple model, development and debugging were problematic. This is a fewer rate of finding errors than (Galletta et al., 1993; 1996) found when subjects debugged models created by the experimenter. This may mean that people are not as good at debugging their own models as they are at debugging models created by others.

[1]  Ralph H. Sprague,et al.  Hitting the wall: errors in developing and code inspecting a 'simple' spreadsheet model , 1998, Decis. Support Syst..

[2]  Carl Martin Allwood,et al.  Error Detection Processes in Statistical Problem Solving , 1984, Cogn. Sci..

[3]  Marilyn M. Mantei,et al.  Computerized financial planning: discovering cognitive difficulties in model building , 1988 .

[4]  Herbert Solomon,et al.  Two models of group behavior in the solution of eureka-type problems , 1955 .

[5]  Joline Morrison,et al.  Factors influencing risks and outcomes in end-user development , 1996, Proceedings of HICSS-29: 29th Hawaii International Conference on System Sciences.

[6]  Raymond R. Panko End user computing: management applications and technology , 1988 .

[7]  Jr. Richard Wayne Selby,et al.  Evaluations of software technologies: testing, cleanroom, and metrics (development methodology, characteristic set, offline software review, empirical study) , 1985 .

[8]  Glenford J. Myers,et al.  A controlled experiment in program testing and code walkthroughs/inspections , 1978, CACM.

[9]  Dennis F. Galletta,et al.  An empirical study of spreadsheet error-finding performance , 1993 .

[10]  Raymond R. Panko,et al.  Spreadsheets on trial: a survey of research on spreadsheet risks , 1996, Proceedings of HICSS-29: 29th Hawaii International Conference on System Sciences.

[11]  Dennis F. Galletta,et al.  An experimental study of spreadsheet presentation and error detection , 1996, Proceedings of HICSS-29: 29th Hawaii International Conference on System Sciences.

[12]  David G. Hendry,et al.  Creating, comprehending and explaining spreadsheets: a cognitive interpretation of what discretionary users think of the spreadsheet model , 1994, Int. J. Hum. Comput. Stud..