• Corpus ID: 14539910

Recommended Practices for Spreadsheet Testing

@article{Panko2007RecommendedPF,
  title={Recommended Practices for Spreadsheet Testing},
  author={Raymond R. Panko},
  journal={ArXiv},
  year={2007},
  volume={abs/0712.0109}
}
  • R. Panko
  • Published 1 December 2007
  • Materials Science
  • ArXiv
This paper presents the authors recommended practices for spreadsheet testing. Documented spreadsheet error rates are unacceptable in corporations today. Although improvements are needed throughout the systems development life cycle, credible improvement programs must include comprehensive testing. Several forms of testing are possible, but logic inspection is recommended for module testing. Logic inspection appears to be feasible for spreadsheet developers to do, and logic inspection appears… 
View PDF on arXiv
29 Citations
Highly Influential Citations
3
Background Citations
10
Methods Citations
6

Figures from this paper

29 Citations

Automating Spreadsheet Discovery & Risk Assessment

This paper proposes an automated approach to the initial stages of the spreadsheet management lifecycle - discovery, inventory and risk assessment - and shows how by leveraging technology, these phases become a sustainable business process.

Measuring maintainability of spreadsheets in the wild

Several studies have shown how spreadsheets are pervasive in many organizations as a form of end-user programming, but they are seldom developed with maintenance concerns in mind, and organizations have no efficient way of estimating the risk they present.

Spreadsheet Testing in Practice

A mixed methods study investigates whether spreadsheet users also test, or how do they test and to what extent, and indicates that ensuring correctness is an important concern, and a major fraction of users do test their spreadsheets.

Spreadsheet testing in practice

A mixed methods study investigates whether spreadsheet users also test, or how do they test and to what extent, and indicates that ensuring correctness is an important concern, and a major fraction of users do test their spreadsheets.

Establishing and Measuring Standard Spreadsheet Practices for End-Users

It is considered how establishing standard practices in spreadsheet training and certification can help reduce some of the risks associated with spreadsheets, and help promote productivity.

Development and Experimentation of a Software Tool for Identifying High Risk Spreadsheets for Auditing

Conference paper published in Proceedings of the European Spreadsheets Risks Interest Group Conference on "Spreadsheet Risk Management" shows the importance of knowing how to manage spreadsheets risk in the event of a financial crisis.

How can non-technical end users effectively test their spreadsheets?

Purpose – An alarming number of spreadsheet faults have been reported in the literature, indicating that effective and easy-to-apply spreadsheet testing techniques are not available for…

The Detection of Human Spreadsheet Errors by Humans versus Inspection (Auditing) Software

This study attempted to find errors in human-developed spreadsheets to avoid the potential artifacts created by error seeding, and found Excel Error Check and Spreadsheet Professional were almost useless for correctly flagging natural (human) errors.

In Pursuit of Spreadsheet Excellence

A simple sampling test - The Clean Sheet Test - which can be used to objectively evaluate if an organisation is in control of the spreadsheets it is using in important processes such as financial reporting.

Integrating Spreadsheet Engineering in a Management Science Course: A Hierarchical Approach

Embracing spreadsheet engineering provides a magnificent opportunity for management science instructors to increase relevance and student satisfaction while increasing the likelihood of management science application by the authors' graduates.

References

SHOWING 1-10 OF 35 REFERENCES

Applying Code Inspection to Spreadsheet Testing

  • R. Panko
  • Business
    J. Manag. Inf. Syst.
  • 1999
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 type of errors.

Managing code inspection information

Nine key metrics that software project managers can use to plan, monitor, and improve inspections are defined and graphs of these metrics expose problems early and can help managers evaluate the inspection process itself.

Design and Code Inspections to Reduce Errors in Program Development

It is shown that by using inspection results, a mechanism for initial error reduction followed by ever-improving error rates can be achieved.

Experience with inspection in ultralarge-scale development

The use of code inspection to detect errors in ultralarge software projects is discussed. In particular, quantitative results based on a 1988 study of inspection of 2.5 million lines of high-level…

Lessons from three years of inspection data (software development)

The implementation of an inspection program as part of a standard development process for an operating system at Bull HN Information Systems Major Systems Division is reviewed. The methods used to…

Measures for Excellence: Reliable Software on Time, Within Budget

From the Publisher: This book helps you accurately measure the completion time frames for small-to-medium software development projects, with practical techniques for performing software estimates,…

Advances in software inspections

Studies and experiences are presented which enhance the use of the inspection process and improve its contribution to development of defect-free software on time and at lower cost.

A controlled experiment in program testing and code walkthroughs/inspections

The results show that the popular code walkthrough/inspection method was as effective as other computer-based methods in finding errors and that the most effective methods (in terms of errors found and cost) employed pairs of subjects who tested the program independently and then pooled their findings.

An experiment to assess the cost-benefits of code inspections in large scale software development

A long-term experiment to compare the costs and benefits of several different software inspection methods applied by professional developers to a commercial software product they were creating found that certain combinations of changes dramatically increased the inspection interval.

An experiment to assess different defect detection methods for software requirements inspections

  • A. PorterL. Votta
  • Computer Science
    Proceedings of 16th International Conference on Software Engineering
  • 1994
A scenario-based detection method, in which each reviewer executes a specific procedure to discover a particular class of defects has a higher defect detection rate than either ad hoc or checklist methods.