Skip to main content

When to Stop Testing Software? Some Exact Results

  • Conference paper
Bayesian Analysis in Statistics and Econometrics

Part of the book series: Lecture Notes in Statistics ((LNS,volume 75))

Abstract

Developers of large software systems must decide how much to test a piece of software before it is released. We consider an explicit tradeoff between the costs of testing and releasing. The cost of testing may include the cost of a lost economic initiative because of continued testing and the cost of releasing may include the cost of customer dissatisfaction and cost of fixing an unknown number of bugs in the released version. The problem is formulated as a sequential Bayes problem in which information from past experience is also used. The structure of the optimal policy is determined.

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 PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD 109.99
Price excludes VAT (USA)
  • Compact, lightweight 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

  • Dalal, S. R. and Mallows, C. L (1988). When should one stop testing software? J. of Am. Statist. Assoc., 83, 872–879

    Article  MathSciNet  MATH  Google Scholar 

  • Dalal, S. R. and Mallows, C. L. (1990). Some graphical aids for deciding when to stop testing software. IEEE Journal on selected areas in communications, Special issue on Telecommunications Software Quality and Productivity, 8, 169–175.

    Google Scholar 

  • Goel, A. L. and Okumoto, K. (1979). Time dependent error detection rate model for software reliability and other performance measures. IEEE Trans. Rei, R-28, 206–211.

    Article  Google Scholar 

  • Jelinski, Z. and Moranda, P. B. (1972). Software reliability research. In Statistical Computer Performance Evaluation. Ed. Freiberger, W., Academic Press, Inc., New York.

    Google Scholar 

  • Langberg, N. and Singpurwalla, N. D. (1985). A unification of some software reliability models. SIAM. J. Sci. Stat. Comput. 6, 781–790.

    Article  MathSciNet  MATH  Google Scholar 

  • Musa, J. D. (1975). A theory of software reliability and its applications. IEEE Trans. Software Eng., SE-1, 312–327.

    Google Scholar 

  • Starr, Norman (1974). Optimal and adaptive stopping based on capture times. J. Appl. Prob. 11, 194–302.

    Article  MathSciNet  Google Scholar 

  • Vardi, Y. (1980). On a stopping time of Starr and its use in estimating the number of transmission sources. J. Appl. Prob. 17, 235–242.

    Article  MathSciNet  MATH  Google Scholar 

Download references

Author information

Authors and Affiliations

Authors

Editor information

Editors and Affiliations

Rights and permissions

Reprints and permissions

Copyright information

© 1992 Springer-Verlag New York, Inc.

About this paper

Cite this paper

Dalai, S.R., Mallows, C.L. (1992). When to Stop Testing Software? Some Exact Results. In: Goel, P.K., Iyengar, N.S. (eds) Bayesian Analysis in Statistics and Econometrics. Lecture Notes in Statistics, vol 75. Springer, New York, NY. https://doi.org/10.1007/978-1-4612-2944-5_18

Download citation

  • DOI: https://doi.org/10.1007/978-1-4612-2944-5_18

  • Publisher Name: Springer, New York, NY

  • Print ISBN: 978-0-387-97863-5

  • Online ISBN: 978-1-4612-2944-5

  • eBook Packages: Springer Book Archive

Publish with us

Policies and ethics