Walkthroughs, Code Reviews, and Inspections

  • John Dooley

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?)

Keywords

Marketing 

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. Ackerman, A., et al. (1989). “Software Inspections: An Effective Verification Process.” IEEE Software 6(3): 31–36. 1989.MathSciNetCrossRefGoogle Scholar
  2. Dijkstra, E. “The Humble Programmer.” CACM 15(10): 859–866. 1972.CrossRefGoogle Scholar
  3. Doolan, P. “Experience with Fagan’s Inspection Method.” Software — Practice & experience 22(2): 173–182. 1992.CrossRefGoogle Scholar
  4. Dunsmore, A., M. Roper, et al. “Practical Code Inspection Techniques for Object-Oriented Systems: An Experimental Comparison.” IEEE Software 20(4): 21–29. 2003.CrossRefGoogle Scholar
  5. Fagan, M. “Design and Code Inspections to Reduce Errors in Program Development.” IBM Systems Journal 15(3): 182–211. 1976.CrossRefGoogle Scholar
  6. Fagan, M. “Advances in Software Inspections.” IEEE Trans on Software Engineering 12(7): 744–751. 1986.CrossRefGoogle Scholar
  7. Martin, R. C. Agile Software Development: Principles, Patterns, and Practices. (Upper Saddle River, NJ: Prentice Hall, 2003.)Google Scholar
  8. McConnell, S. Code Complete 2: A Practical Handbook of Software Construction. (Redmond, WA: Microsoft Press, 2004.)Google Scholar

Copyright information

© John Dooley 2011

Authors and Affiliations

  • John Dooley

There are no affiliations available

Personalised recommendations