Skip to main content
Log in

Gaining Confidence in Software Inspection Using a Bayesian Belief Model

  • Published:
Software Quality Journal Aims and scope Submit manuscript

Abstract

In this paper I describe how confidence in a software inspection can be obtained through calculating an estimate of its effectiveness. The method uses a Bayesian Belief Network to model the software inspection process and calculates the inference on how effective a particular inspection was. This technique was selected as it provides a means of initialising the model with inspectors' experience and has the ability to learn and optimise performance. This technique provides answers to some of the questions and limitations raised by current models used to predict inspection effectiveness. The application of the model to a major software project is discussed, covering the initial practitioner survey, model initialisation, model calibration and verification results obtained.

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

Access this article

Price excludes VAT (USA)
Tax calculation will be finalised during checkout.

Instant access to the full article PDF.

Similar content being viewed by others

References

  • Ackerman, A.F., Buchwald, L.S., and Lewski, F.H. 1989. Software inspections: an effective verification process, IEEE Software May, 31-36.

  • Adams, E.N. 1984. Optimizing preventative service of software products, IBM J. 28(1): 2–14.

    Google Scholar 

  • Bisant, D.B. and Lyle, J.R. 1989. A two-person inspection method to improve programming productivity, IEEE Trans. Software Eng. SE-15(10): 1294–1304.

    Google Scholar 

  • Christenson, D.A. and Huang, S.T. 1988. Code inspection model for software quality management and prediction. Proc. IEEE Global Telecommun. Conf., IEEE Computer Society Press.

  • Cowell, R.G., Dawid, A.P., and Spiegelhalter, D.J. 1993. Sequential model criticism in probabilistic expert systems, IEEE Trans. Pattern Anal. Mach. Intellig.15(3): 209–219.

    Google Scholar 

  • Fagan, M. 1976. Design and code inspections to reduce errors in program development, IBM Syst. J. 15(3): 182–211.

    Google Scholar 

  • Fagan, M. 1986. Advances in software inspections, IEEE Trans. Software Eng. SE-12(7): 744–751.

    Google Scholar 

  • Fagan, M. and Knight, J.C. 1991. Testing is not the best means of defect detection and removal. Proc. Achieving Quality Software a National Debate, San Diego, CA, Society for Software Quality.

    Google Scholar 

  • Fenton, N.E. 1991. Software Metrics — A Rigorous Approach, London, Chapman and Hall.

    Google Scholar 

  • Hodgson, J.P.E. 1991. Knowledge Representation and Language in AI, Chichester, Ellis Horwood.

    Google Scholar 

  • Knight, J.C. and Meyers, E.A. 1991. Phased inspections and their implementation, ACM Sigsoft Software Eng. Notes 16(3): 2935.

    Google Scholar 

  • McCabe, T.J. 1976. A complexity measure, IEEE Trans. Software Eng. SE-2(4): 308–320.

    Google Scholar 

  • Myers, G.J. 1979. The Art of Software Testing, New York, John Wiley, pp. 22–23.

    Google Scholar 

  • O'Neill, D. 1997. Software inspections, http:// www.sei.cmu.edu / str / descriptions / inspections.

  • Porter, A.A. et al. 1988. Understanding the source of variations in software inspections, ACM Trans. Software Eng. Methodology 7(1):41-79.

    Google Scholar 

  • Porter, A.A. and Votta, L.G. 1994. An experiment to assess different defect detection methods for software requirements inspections. Proc. 16th Int. Conf. Software Eng.

  • Shepperd, M.J. 1988. A critique of cyclomatic complexity as a software metric, Syst. Eng. J. 3(2):3036.

    Google Scholar 

  • Strauss, S.H. and Ebenau, R.G. 1994. Software Inspection Process, New York, McGraw-Hill.

    Google Scholar 

Download references

Author information

Authors and Affiliations

Authors

Rights and permissions

Reprints and permissions

About this article

Cite this article

Cockram, T. Gaining Confidence in Software Inspection Using a Bayesian Belief Model. Software Quality Journal 9, 31–42 (2001). https://doi.org/10.1023/A:1016600602423

Download citation

  • Issue Date:

  • DOI: https://doi.org/10.1023/A:1016600602423

Navigation