Oy Laatukonsultointi P. Kantelinen Ab

# (#)

Inspections and reviews - sources


WWW sites:

  1. NASA's inspection/review checklists
  2. R.S. Pressman & Associates inspection/review checklists
  3. StickyMinds.com: resources about reciews and other areas, too ( (search for "review" or "inspection"))
  4. Process Impact's inspection checklists, templates and other useful stuff
  5. Vanadian Mind Products's How to write unmaintanable code, i.e. things to look for in code inspections
  6. Open Process Framework's Design Document Inspection Checklist
  7. Macadamian's Code Review Checklist
  8. FoxPro Code Review Checklist
  9. Seamonkey's Code Review Guide
  10. CWE - Common Weakness Enumeration - a list of common security weaknesses


Literature:
  1. IEEE Software magazines theme issue on Software Inspections, July/August 2003
  2. Implementing Peer Code Reviewing, June 29, 2006
  3. A.F. Ackerman, L.S. Buchwald, F.H. Lewski: “Software Inspections: An Effective Verification Process”, IEEE Software, May 1989
  4. P.M. Bailey: "A Formula for Successful Peer Reviews", Better Software, pp. 14 - 16, November/December 2004
  5. J. Barnard, K. El Emam, D. Zubrow: "Using Capture-Recapture Models for the Reinspection Decison", Software Quality Professional, pp. 11 - 19, March 2003
  6. J. Barnard & A. Price: Managing Code Inspection Information , IEEE Software, March 1994
  7. V.R. Basili, M.D. Dasantolonakis & R.H. Yacobellis: Technology Transfer at Motorola, IEEE Software, March 1994
  8. R. Bias: “Walkthroughs: Efficient Collaborative Testing”, IEEE Software, September 1991
  9. S. Biffl, M. Halling: "Investigating the Defect Detection Effectiveness and Cost Benefit of Nominal Inspection Teams", IEEE Transactions on Software Engineering, pp. 385 - 397, May 2003
  10. D. B. Bisant & J.R. Lyle: “A Two-Person Inspection Method to Improve Programming Productivity”, IEEE Transactions on Software Engineering, October 1989
  11. B. Brykczynski: "A Survey of Software Inspection Checklists", ACM Software Engineering Notes, January 1999
  12. J.K. Chaar, M.J. Halliday, I.S. Bhandari & R. Chillarege: "In-Process Evaluation of Software Inspection and Test",, IEEE Transactions on Software Engineering, November 1993
  13. Y. Chernak: "A Statistical Appraoch to the Inspection Checklist Formal Synthesis and Improvement", IEEE Transactions on Software Engineering, December 1996
  14. J. Cohen: The Best Kept Secrets of Code Review, Smart Bear Inc. (book available for free from Smart Bear), 2006
  15. L. Cohen: Inspection Moderators Handbook, Digital Equipment Corporation, 1991
  16. R.G. Ebenau & S.H. Strauss: Software Inspection Process, McGraw-Hill, 1994
  17. D. Evan, D. Larochelle: ”Improving Security Using Extensible Lightweight Static Analysis”, IEEE Software, pp. 42 - 51, January/February 2002
  18. J. R. de Almeida, et.al.: "Best Practices in Code Inspection for Safety-Critical Software", IEEE SOftware, pp. 56 - 63, May/June 2003
  19. C. Denger, F. Shull: "A Practical Approach for Quality-Driven Inspection", IEEE Software, pp. 79-86, March/April 2007
  20. M. Fagan: Design and Code Inspections and Process Control in the Development of Programs, IBM TR 21.572, 1974
  21. M. Fagan: Design and Code Inspections to Reduce Errors in Program Development, IBM Systems Journal, Vol 15, No.3, 1976
  22. M. Fagan: “Advances in Software Inspections”, IEEE Transactions on Software Engineering, July 1986
  23. D.P. Freeman & G.M. Weinberg: Handbook of Walkthroughs, Inspections and Technical Reviews, Little, Brown and Company, 1990
  24. G Fisher: Automated Source Code Analysis. When, why, and how to leverage source code analysis tools, White Paper, Kockwork, 2007
  25. J. Frittsch, et.al.: "Formal Inspection Best-in-Class Model", Software Quality, No.1 1998-99
  26. E. George, S. Janiszewski: "Optimizing Software Inspections with Statistical Quality Techniques", Software Quality Professional, pp. 16 - 29, December 2003
  27. T. Gilb: "Rule-Based Design Reviews", Software Quality Professional, pp. 4 - 13, December 2004
  28. T. Gilb: "Planning to Get the Most Out of Inspection", Software Quality Professional, March 2000
  29. T. Gilb, D. Graham: Software Inspection, Addison-Wesley, 1993
  30. T. Gilb: Principles of Software Engineering Managament, Addison-Wesley, 1988
  31. T. Gilb's interview: "Fighting Ambiguity One Document at a Time", IEEE Software, January 1994
  32. T. Golding: "Indulge in Code Review", Better Software,, pp. 12 - 13, May 2007
  33. L. Gotta: "Does Every Inspection Need a Meeting", Software Engineering Notes, December 1993
  34. R.B. Grady & T.V. Slack: “Key Lessons In Achieving Widespread Inspection Use”, IEEE Software, pp. 46 - 57, July 1994
  35. P. Hall: "Review Secrets: Asking Better Questions", StickyMinds, September 2006
  36. M. Hiltunen: "Tick-the-Code Inspection: Theory and Practice", Software Quality Professional, pp. 20 - 27, June 2007
  37. B.C Hungerford, A.R. Hevner, R.W. Collins: "Reviewing Software Diagrams: A Cognitive Study", IEEE Transactions of Software Engineering, pp. 82 - 96, February 2004
  38. J. Holmes: "Optimizing the Software Life Cycle", Software Quality Professional, pp. 14 - 23, December 2003
  39. D. Holland: "Document Inspection as an Agent of Change", Software Quality Professional, December 1999
  40. C.P. Hollocker: Software Reviews and Audits Handbook, 1990
  41. A. L. Jacob, S.K. Pillai: "Statistical Process Control to Improve Coding and Code Review", IEEE Software, pp. 50 - 55, May/June 2003
  42. IEEE Standard for Software Reviews and Audits, IEEE Std 1028-1997
  43. R. Kazman, L. Bass: "Making Architecture Reviews Work in the Real World", IEEE Software, pp. 76 - 73, January/February 2002
  44. J.C. Knight, E.A. Myers: “Phased Inspections and Their Implementation”, Software Engineering Notes, July 1991
  45. J.C. Knight & A. Myers: “An Improved Inspection Technique”, Communications of the ACM, pp. 51 - 61, November 1993
  46. O.R. Kohli: High Level Design Inspection Specification, IBM TR 21.601, 1975
  47. O. Laitenberger, K. El Emam, T. G. Harbich: "An Internally Replicated Quasi-Experimental Comparison of Checklist and Perspective-Based Reading of Code Documents", IEEE Transactions on Software Enginering, May 2001
  48. R.R. Larson: Test Plan and Test Case Inspection Specification, IBM TR 21.586, 1975
  49. R. MacFarland: "Case Study of an Improvement Program Featuring Reviews and Inspections", Software Quality Professional, June, 2001
  50. R.J. Madachy: Measuring Inspections at Litton, Software Quality, July 1996
  51. J.F. Maranzano, et.al.: "Architecture Reviews: Practice and Experience", IEEE Software, pp. 34 - 43, March/April 2005
  52. V. Mashayekhi, J.M. Drake, W-T Tsai & J. Riedl: “Distributed, Collaborative Software Inspection”, IEEE Software, pp. 66 - 75,September 1993
  53. A. Miller: “Looking Ahead with Software Reviews”, IEEE Software, September 1993
  54. A. Porter, L. Votta: "What Makes Inspections Work?", IEEE Software, November/December 1996
  55. A. Porter, P.M. Johnson "Assessing Software Review Meetings: Results of a Comparative Analysis of Two Experimental Studies", IEEE Transactions on Software Engineering, March 1997
  56. A. Porter, H.P. Siy, C.A. Toman, L.G. Votta "An Experiment to Assess the Cost-Benefits of Code Inspections in Large Scale Software Development", IEEE Transactions on Software Engineering, June 1997
  57. R.A. Radice: High Quality, Low Cost Software Inspections, Paradoxicon Publishing, 2002
  58. G.W. Russell: “Experience with Inspections in Ultralarge-Scale Developments”, IEEE Software, January 1991
  59. N. Rutar, C. B. Almazan, J. S. Foster: A Comparison of Bug Finding Tools for Java , University of Maryland
  60. A. Savoia: "From Primitive to Prominent. The Past, Present, and Future of Automated Code Analysis", Better Software, pp. 19 - 22, April 2006
  61. C.B. Seaman, V.R. Basili: "Communication and Organization: An Empirical Study of Discussions in Inspection Meetings", IEEE Transactions on Software Engineering, July 1998
  62. A. Shalloway: "Agile Design and Code Reviews"
  63. S.H. Strauss & R.G. Ebenbau: Software Inspection Process, IEEE Computer Society Press, 1994
  64. G.K. Tyran, J.F. George: "Improving Software Inspections with Group Process Support", Communications of the ACM, pp. 87- 92, September 2002
  65. E.P.W.M van Veenendaal: ”Practical Quality Assurance for Embedded Software, Software Quality Professional, June 1999
  66. D.A. Wheeler, B. Brykczynski, R.N. Meeson: Software Inspection. An Industry Best Practice, IEEE Computer Society Press, 1996
  67. M. van Genuchten, C. van Dijk, H. Scholten, D. Vogel: "Using Group Support System for Software Inspections", IEEE Software, pp. 60 - 65, May/June 2001
  68. P. Vitharana, K. Ramamurthy: "Computer-Mediated Group Support, Anonymity, and the Software Inspection Process: An Empricial Investigation", IEEE Transactions of Software Engineering, pp. 167 - 180, February 2003
  69. G.M. Weinberg: "Egoless Programming", IEEE Software January/February 1999
  70. G.M. Weinberg: The Psychology of Computer Programming: Silver Anniversary Edition, Dorset House 1998
  71. E. Weller: “Lessons from Three Years of Inspection Data”, IEEE Software, September 1993
  72. K. Wiegers "Seven Deadly Sins of Software Reviews", StickyMInds.com
  73. K. Wiegers: Peer Reviews in Software: A Practical Guide, Addison-Wesley, 2002
  74. K. Wiegers: "When Two Eyes Aren't Enough", Software Development, pp. 58 - 61, October 2001
  75. L. Wyssocky: Are Your Code Reviews Effective?, Lidor Wyssocky’s Blog
  76. E. Yourdon: Structured Walkthroughs, Yourdon Press, 1978
  77. J Zheng et.al.: "On the Value of Static Analysis for Fault Detection in Software",IEEE Transactions on Software Engineering, pp. 240 - 253, APRIL 2006