Software Inspections in Practice: Six Case Studies

  • Sami Kollanus
  • Jussi Koskinen
Part of the Lecture Notes in Computer Science book series (LNCS, volume 4034)


Software inspections have been acknowledged as an important method in software engineering, but they are not well applied in practice. This paper discusses the current practices and the related problems based on six case studies in industrial settings. The analysis of inspection practices was organized according to ICMM, which is a model for systematically assessing and improving software inspection process maturity. The sample case organizations used inspections relatively regularly. The involved units are compared and the revealed practices, their characteristics, inspection problems and implications of the study discussed. The main problem areas were non-existent inspection training, limited formality of inspections and immaturity of inspection metrics.


Organizational Policy Process Area Software Development Process Inspection Process Case Organization 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    Ciolkowski, M., Laitenberger, O., Biffl, S.: Software Reviews, the State of the Practice. IEEE Software 20(6), 46–51 (2003)CrossRefGoogle Scholar
  2. 2.
    Fagan, M.E.: Design and Code Inspection to Reduce Errors in Program Development. IBM Systems Journal 15(3), 182–211 (1976)CrossRefGoogle Scholar
  3. 3.
    Johnson, P.M.: Reengineering Inspection. Comm. of the ACM 41(2), 49–52 (1998)CrossRefGoogle Scholar
  4. 4.
    Kitchenham, B.A., Pfleeger, S.L., Pickard, L.M., Jones, P.W., Hoaglin, D.C., Emam, K.E., Rosenberg, J.: Preliminary Guidelines for Empirical Research in Software Engineering. IEEE Transactions on Software Engineering 28(8), 721–734 (2002)CrossRefGoogle Scholar
  5. 5.
    Kollanus, S.: ICMM – Inspection Capability Maturity Model. In: Proc. of the 2nd IASTED International Conference on Software Engineering (IASTED-SE 2005), pp. 372–377. ACTA Press, Innsbruck (2005)Google Scholar
  6. 6.
    Kollanus, S.: A Problem Based Approach to Inspection Improvement? In: Bomarius, F., Komi-Sirviö, S. (eds.) PROFES 2005. LNCS, vol. 3547, pp. 429–442. Springer, Heidelberg (2005)CrossRefGoogle Scholar
  7. 7.
    Laitenberger, O., DeBaud, J.-M.: An Encompassing Life-Cycle Centric Survey of Software Inspection. Journal of Systems and Software 50(1), 5–31 (2000)CrossRefGoogle Scholar
  8. 8.
    Sauer, C., Ross, J., Land, L., Yetton, P.: The Effectiveness of Software Development Technical Reviews: A Behaviorally Motivated Program of Research. IEEE Transactions on Software Engineering 26(1), 1–14 (2000)CrossRefGoogle Scholar
  9. 9.
    SEI: Capability Maturity Model Integration, version 1.1. Software Engineering Institute (2002),
  10. 10.
    Voas, J.: Software Quality’s Eight Greatest Myths. IEEE Software 16(5), 118–120 (1999)CrossRefGoogle Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2006

Authors and Affiliations

  • Sami Kollanus
    • 1
  • Jussi Koskinen
    • 1
  1. 1.Department of Computer Science and Information SystemsUniversity of JyväskyläAgoraFinland

Personalised recommendations