Abstract
Here’s a shocker: your main quality objective in software development is to get a working program to your user that meets all their requirements and has no defects. That’s right: your code should be perfect. It meets all the user’s requirements and it has no errors in it when you deliver it. Impossible, you cry? Can’t be done? Well, software quality assurance is all about trying to get as close to perfection as you can - albeit within time and budget. (You knew there was a catch, didn’t you?)
Our objective with Inspections is to reduce the Cost of Quality by finding and removing defects earlier and at a lower cost. While some testing will always be necessary, we can reduce the costs of test by reducing the volume of defects propagated to test. —Ron Radice (2002)
When you catch bugs early, you also get fewer compound bugs. Compound bugs are two separate bugs that interact: you trip going downstairs, and when you reach for the handrail it comes off in your hand. —Paul Graham (2001)
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
References
Ackerman, A., et al. (1989). “Software Inspections: An Effective Verification Process.” IEEE Software 6(3): 31–36. 1989.
Dijkstra, E. “The Humble Programmer.” CACM 15(10): 859–866. 1972.
Doolan, P. “Experience with Fagan’s Inspection Method.” Software — Practice & experience 22(2): 173–182. 1992.
Dunsmore, A., M. Roper, et al. “Practical Code Inspection Techniques for Object-Oriented Systems: An Experimental Comparison.” IEEE Software 20(4): 21–29. 2003.
Fagan, M. “Design and Code Inspections to Reduce Errors in Program Development.” IBM Systems Journal 15(3): 182–211. 1976.
Fagan, M. “Advances in Software Inspections.” IEEE Trans on Software Engineering 12(7): 744–751. 1986.
Martin, R. C. Agile Software Development: Principles, Patterns, and Practices. (Upper Saddle River, NJ: Prentice Hall, 2003.)
McConnell, S. Code Complete 2: A Practical Handbook of Software Construction. (Redmond, WA: Microsoft Press, 2004.)
Rights and permissions
Copyright information
© 2011 John Dooley
About this chapter
Cite this chapter
Dooley, J. (2011). Walkthroughs, Code Reviews, and Inspections. In: Software Development and Professional Practice. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4302-3802-7_15
Download citation
DOI: https://doi.org/10.1007/978-1-4302-3802-7_15
Publisher Name: Apress, Berkeley, CA
Print ISBN: 978-1-4302-3801-0
Online ISBN: 978-1-4302-3802-7
eBook Packages: Professional and Applied ComputingApress Access BooksProfessional and Applied Computing (R0)