
TL;DR
This paper emphasizes the importance of early defect detection and disciplined review in software development to reduce errors, improve quality, and save costs, supported by research on spreadsheet error rates.
Contribution
It advocates for early review processes and quality measurements, demonstrating their effectiveness in reducing defects and project delays in software development.
Findings
Early review reduces defect density and improves defect removal efficiency.
Investing in early defect detection saves project costs and prevents expensive errors.
Spreadsheet error rates align with software defect trends based on review extent.
Abstract
Human error research on overconfidence supports the benefits of early visibility of defects and disciplined development. If risk to the enterprise is to be reduced, individuals need to become aware of the reality of the quality of their work. Several cycles of inspection and defect removal are inevitable. Software Quality Management measurements of defect density and removal efficiency are applicable. Research of actual spreadsheet error rates shows data consistent with other software depending on the extent to which the work product was reviewed before inspection. The paper argues that the payback for an investment in early review time is justified by the saving in project delay and expensive errors in use. 'If debugging is the process of removing bugs, then programming must be the process of putting them in' - Anon.
Peer Reviews
No public reviews on file for this paper yet. If you reviewed it on a platform where reviews are public (OpenReview, ICLR, NeurIPS, ICML), you can paste yours below so the community can read it here.
Videos
No videos yet. Explain this paper in a talk, walkthrough, or lecture? Add one.
Taxonomy
TopicsSpreadsheets and End-User Computing · Software Engineering Research · Software Engineering Techniques and Practices
