Skip to main content

A Knowledge Management Framework to Support Software Inspection Planning

  • Chapter
Managing Software Engineering Knowledge

Abstract

Software inspection requires customization to each development context and guidelines for planning for optimal results. In this work we present a role-oriented knowledge management framework for key decisions in software inspection planning and focus on how to use available knowledge from literature, which may vary considerably in different contexts, with local empirical data. We identify three decision levels, which differ by knowledge requirements and the level of uncertainty for decision inputs: the quality management level, the project planning level,and the inspection level. On each inspection planning level we provide scenarios with key decisions that outline the decision-making process and show how available inspection knowledge based on measurement in a particular context can be used for decision support. The conceptual framework is a first step to make inspection planning more explicit and procedural in order to be able to further improve this process.

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

Chapter
USD 29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD 84.99
Price excludes VAT (USA)
  • Available as EPUB and PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD 109.00
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info
Hardcover Book
USD 109.99
Price excludes VAT (USA)
  • Durable hardcover edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. Aurum A., Petersson H. Wohlin C. (2002) State-of-the-art: software inspections after 25 years. Software testing, verification and reliability, 12: 133–154

    Article  Google Scholar 

  2. Basili V.R., Green S., Laitenberger O., Lanubile F., Shull F., Soerumgaard S., Zelkowitz M. (1996) The empirical investigation of perspective-based reading. Empirical software engineering: an international journal, 1: 133–164

    Article  Google Scholar 

  3. Bianchi A. Lanubile F., Visaggio, G. (2001) A controlled experiment to assess the effectiveness of inspection meetings. In: Proceedings of IEEE Metrics’01, London, UK, pp. 42–50

    Google Scholar 

  4. Biffl St., Hailing M., Köhle, M. (2000) Investigating the effect of a second software inspection cycle. In: Proceedings of the IEEE Asia-Pacific conference on quality software, Hong Kong, pp. 155–164

    Google Scholar 

  5. Biffl S., Gutjahr W. (2001) Influence of team size and defect detection methods on inspection effectiveness. In: Proceedings of IEEE Metrics’01, London, UK, pp. 63–75

    Google Scholar 

  6. Biffl S., Freimut B., Laitenberger O. (2001) Investigating the cost-effectiveness of reinspections in software development. In: Proceeding of ACM/IEEE international conference on Software Engineering, Toronto, Canada, pp. 155–164

    Google Scholar 

  7. Biffl St., Grossmann W. (2001) Evaluating the accuracy of objective estimation models based on inspection data from multiple inspection cycles. In: Proceedings of ACM/IEEE international conference on software engineering, Toronto, Canada, pp. 145–154

    Google Scholar 

  8. Biffl S. (2001) Software inspection techniques to support project and quality management. Habilitation thesis, Shaker Verlag, Aachen, Germany

    Google Scholar 

  9. Biffl S., Hailing M. (2001) A value-based framework for the cost-benefit evaluation of software inspection processes. In: Proceedings of the workshop on inspection in software engineering, Paris, France http://www.cas.mcmaster.ca/wise/ (date accessed 22nd April, 2003 )

    Google Scholar 

  10. Biffl S., Hailing M. (2002) Investigating the influence of inspector capability factors with four inspection techniques on inspection performance. In: Proceedings of 8th IEEE Metrics’02, Toronto, Canada, pp. 115–121

    Google Scholar 

  11. Biffl S., Hailing M. (2003) Investigating the defect detection effectiveness and cost-benefit of nominal inspection teams. To appear in the IEEE transactions on software engineering

    Google Scholar 

  12. Birk A., Dingsoyr T., Stalhane T. (2002) Postmortem: never leave a project without it. IEEE Software, 19: 43–45

    Article  Google Scholar 

  13. Chernak Y. (1996) A statistical approach to the inspection checklist formal synthesis and improvement. IEEE transactions on software engineering, 22: 866–874

    Article  Google Scholar 

  14. Ciolkowski M., Shull F., Biffl S. (2002) A concerted family of experiments to investigate the influence of context on the effect of inspection techniques. In: IEE Proceedings of the EASE conference, Keele University, UK

    Google Scholar 

  15. Dunsmore A., Roper M., Wood M. (2002) Further investigations into the development and evaluation of reading techniques for object-oriented code inspection. In: Proceedings of the 24th international conference on software engineering, Orlando, Florida, pp. 47–57

    Google Scholar 

  16. Fagan M.E. (1976) Design and code inspections to reduce errors in program development. IBM systems journal, 15: 182–211

    Article  Google Scholar 

  17. Gilb T., Graham D. (1993) Software inspection. Addison-Wesley, Reading, MA, USA

    Google Scholar 

  18. Hailing M., Griinbacher P., Biffl S. (2001) Tailoring a COTS group support system for software requirements inspection. In: Proceedings of 16th IEEE international conference on automated software engineering, San Diego, California, pp. 201–208

    Google Scholar 

  19. Hailing M. (2002) Supporting management decisions in software inspection process. PhD thesis, Vienna University of Technology, Austria

    Google Scholar 

  20. Hailing M., Biffl S., Griinbacher P. (2002) A groupware-supported inspection process for active inspection management. In: IEEE Proceedings of 28th Euromicro conference, track on software product and process improvement, Dortmund, Germany, pp. 251–258

    Google Scholar 

  21. Hailing M., Biffl S. (2002) Investigating the influence of software inspection process parameters on inspection meeting the performance. In: IEE Proceedings–Software engineering, 149: 115–122

    Google Scholar 

  22. Kakabadse N.K., Kouzmin A., Kakabadse A. (2001) From tacit knowledge to knowledge management: Leveraging invisible assets. Knowledge and process management, 8: 137–154

    Google Scholar 

  23. Kahneman D., Slovic P., Tversky A. (1984) Judgment under uncertainty: heuristics and biases. Cambridge university press, Cambridge, UK

    Google Scholar 

  24. Laitenberger O., DeBaud J.M. (2000) An encompassing life-cycle centric survey of software inspection. Journal of systems and software 50: 5–31

    Article  Google Scholar 

  25. Laitenberger O., El-Emam K; Harbich T.G. (2001) An internally replicated quasi-experimental comparison of checklist and perspective-based reading of code documents. IEEE transactions on software engineering, 27: 387–421

    Article  Google Scholar 

  26. Marchesi M., Succi G., Wells D., Williams L. (eds.) (2002) Extreme programming perspectives. Addison-Wesley professional series, Boston, MA, USA

    Google Scholar 

  27. Petersson H. (2001) Individual reviewer contribution to the effectiveness of software inspection teams In Proceeding of IEEE Australian software engineering conference, Canberra, Australia, pp. 160–168

    Google Scholar 

  28. Polanyi M. (1966) The tacit dimension. Routledge and Kegan Paul, London, UK

    Google Scholar 

  29. Port D., Hailing M, Kazman R., Biffl S. (2002) Strategic quality assurance planning. In: Proceedings of the 4th international workshop on economics driven software engineering research (EDSER-4) at the international conference on software engineering, Orlando, Florida, USA

    Google Scholar 

  30. Porter, A.A.., Johnson P.M. (1997) Assessing software review meetings: results of a comparative analysis of two experimental studies. IEEE transactions on software engineering, 23: 129–145

    Article  Google Scholar 

  31. Regnell B., Runeson P., Thelin T. (2000) Are the perspectives really different? Further experimentation on scenario-based reading of requirements. Empirical software engineering, 5: 331–356

    Article  MATH  Google Scholar 

  32. Reifer D.A.. (2002) A little bit of knowledge is a dangerous thing. IEEE Software, 19: 14–15

    Article  Google Scholar 

  33. Rus I., Lindvall M. (2002) Knowledge management in software engineering. IEEE Software, 19: 26–38

    Article  Google Scholar 

  34. Sauer C., Jeffery R., Land L., Yetton P. (2000) The effectiveness of software development technical reviews: A behaviorally motivated program of research IEEE transactions on software engineering, 26: 11–14

    Google Scholar 

  35. Shull F.J. (1998) Developing techniques for using software documents: A series of empirical studies. PhD thesis, University of Maryland, College Park, USA

    Google Scholar 

  36. Shull F., loan R. Basili V.R. (2000) How perspective-based reading can improve requirements inspections. IEEE Computer, 33: 73–79

    Google Scholar 

  37. Thelin T., Runeson P. Regnell B. (2001) Usage-based reading–An experiment to guide reviewers with use cases. Information and software technology, 43: 925–938.

    Google Scholar 

  38. Thelin T., Runeson P. Wohlin C. (2002) An experimental comparison of usage-based and checklist-based reading. Submitted to IEEE transactions on software engineering

    Google Scholar 

  39. Travassos Cl., Shull F., Fredericks M. Basili V. (1999) Detecting defects in object-oriented designs: using reading techniques to increase software quality. In: Proceedings conference on object-oriented programming systems, languages and applications, Denver, Colarado, USA, ACM Sigplan notices, 34: 47–56

    Chapter  Google Scholar 

  40. Trigeorgis L. (1996) Real options. MIT Press, Boston, MA, USA

    Google Scholar 

  41. Vincke P. (1992) Multicriteria decision-aid. John Wiley and Sons, New York, NY

    Google Scholar 

  42. Votta L. (1993) Does every Inspection need a meeting? ACM software engineering notes, 18: 107–114

    Article  Google Scholar 

  43. Weller E.F. (1993) Lessons from three years of inspection data. IEEE Software 10: 38–45

    Article  Google Scholar 

  44. Wohlin C., Aurum A., Petersson H., Shull F., Ciolkowski M. (2002): Software inspection benchmarking–a qualitative and quantitative comparative opportunity. In: Proceedings of 8th IEEE Metrics’02, Toronto, Canada, pp. 118–127

    Google Scholar 

  45. Yetton P.W., Bottger P.C. (1982) Individual versus group problem solving: an empirical test of a best-member strategy. Organizational behavior and human performance, 29: 307–321

    Article  Google Scholar 

Download references

Authors

Editor information

Editors and Affiliations

Rights and permissions

Reprints and permissions

Copyright information

© 2003 Springer-Verlag Berlin Heidelberg

About this chapter

Cite this chapter

Biffl, S., Halling, M. (2003). A Knowledge Management Framework to Support Software Inspection Planning. In: Aurum, A., Jeffery, R., Wohlin, C., Handzic, M. (eds) Managing Software Engineering Knowledge. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-662-05129-0_11

Download citation

  • DOI: https://doi.org/10.1007/978-3-662-05129-0_11

  • Publisher Name: Springer, Berlin, Heidelberg

  • Print ISBN: 978-3-642-05573-7

  • Online ISBN: 978-3-662-05129-0

  • eBook Packages: Springer Book Archive

Publish with us

Policies and ethics