Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to main content
Springer Nature Link
Log in

Joint Release and Testing Stop Time Policy with Testing-Effort and Change Point

  • Chapter
  • First Online:
Risk Based Technologies

Abstract

This study proposes an approach in which software developer should release the product early and continue the testing process for an added period in the operational phase. The software reliability model assumes that the tester’s fault-identification rate modifies after the software release. The time instant at which a bug-detection rate experience a change is termed as a change-point. This paper further discusses the optimal software release policy to determine the software time-to-market and testing duration by dealing with two criteria, namely, reliability and cost. Therefore, multi-criteria decision-making (MCDM) technique recognized as multi-attribute utility theory (MAUT) is applied to measure the optimal release policy. In the current research, the effect of testing effort on modeling the software reliability and cost function is investigated for the joint optimization problem. A numerical illustration is provided by using the actual data set to examine the performance of the developed optimal release time and testing termination time policy.

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

Access this chapter

Log in via an institution

Subscribe and save

Springer+ Basic
$34.99 /Month
  • Get 10 units per month
  • Download Article/Chapter or eBook
  • 1 Unit = 1 Article or 1 Chapter
  • Cancel anytime
Subscribe now

Buy Now

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
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

We’re sorry, something doesn't seem to be working properly.

Please try refreshing the page. If that doesn't work, please contact support so we can address the problem.

References

  1. Musa, J. D. (1975). A theory of software reliability and its application. IEEE Transactions on Software Engineering, 3, 312–327.

    Article  Google Scholar 

  2. Goel, A. L., & Okumoto, K. (1979). Time-dependent error-detection rate model for software reliability and other performance measures. IEEE Transactions on Reliability, 28(3), 206–211.

    Article  Google Scholar 

  3. Yamada, S., Ohtera, H., & Narihisa, H. (1986). Software reliability growth models with testing-effort. IEEE Transactions on Reliability, 35(1), 19–23.

    Article  Google Scholar 

  4. Yamada, S., Hishitani, J., & Osaki, S. (1993). Software-reliability growth with a Weibull test-effort: A model and application. IEEE Transactions on Reliability, 42(1), 100–106.

    Article  Google Scholar 

  5. Kapur, P. K., Kumar, S., & Garg, R. B. (1999). Contributions to hardware and software reliability (Vol. 3, p. 3). Singapore: World Scientific.

    MATH  Google Scholar 

  6. Kapur, P. K., Pham, H., Gupta, A., & Jha, P. C. (2011). Software reliability assessment with OR applications. London: Springer.

    Book  Google Scholar 

  7. Kapur, P. K., Pham, H., Aggarwal, A. G., & Kaur, G. (2012). Two dimensional multi-release software reliability modeling and optimal release planning. IEEE Transactions on Reliability, 61(3), 758–768.

    Article  Google Scholar 

  8. Zhang, J., Lu, Y., Yang, S., & Xu, C. (2016). NHPP-based software reliability model considering testing effort and multivariate fault detection rate. Journal of systems engineering and electronics, 27(1), 260–270.

    Google Scholar 

  9. Kapur, P. K., Gupta, A., Shatnawi, O., & Yadavalli, V. S. S. (2006). Testing effort control using flexible software reliability growth model with change point. International Journal of Performability Engineering, 2(3), 245–262.

    Google Scholar 

  10. Kapur, P. K., Grover, P. S., & Younes, S. (1994, November). Modelling an imperfect debugging phenomenon with testing effort. In Proceedings of 5th International Symposium on Software Reliability Engineering, 1994 (pp. 178–183). IEEE.

    Google Scholar 

  11. Kapur, P. K., Goswami, D. N., & Gupta, A. (2004). A software reliability growth model with testing effort dependent learning function for distributed systems. International Journal of Reliability, Quality and Safety Engineering, 11(04), 365–377.

    Article  Google Scholar 

  12. Huang, C. Y., & Kuo, S. Y. (2002). Analysis of incorporating logistic testing-effort function into software reliability modeling. IEEE Transactions on Reliability, 51(3), 261–270.

    Article  MathSciNet  Google Scholar 

  13. Peng, R., Li, Y. F., Zhang, W. J., & Hu, Q. P. (2014). Testing effort dependent software reliability model for imperfect debugging process considering both detection and correction. Reliability Engineering & System Safety, 126, 37–43.

    Article  Google Scholar 

  14. Li, Q., Li, H., & Lu, M. (2015). Incorporating S-shaped testing-effort functions into NHPP software reliability model with imperfect debugging. Journal of Systems Engineering and Electronics, 26(1), 190–207.

    Article  Google Scholar 

  15. Zhang, X., & Pham, H. (2002). Predicting operational software availability and its applications to telecommunication systems. International Journal of Systems Science, 33(11), 923–930.

    Article  Google Scholar 

  16. Lin, C. T., Huang, C. Y., & Chang, J. R. (2005, December). Integrating generalized Weibull-type testing-effort function and multiple change-points into software reliability growth models. In 12th Asia-Pacific Software Engineering Conference, 2005. APSEC’05 (p. 8). IEEE.

    Google Scholar 

  17. Kapur, P. K., & Garg, R. B. (1991). Optimal release policies for software systems with testing effort. International Journal of Systems Science, 22(9), 1563–1571.

    Article  Google Scholar 

  18. Dai, Y. S., Xie, M., Poh, K. L., & Yang, B. (2003). Optimal testing-resource allocation with genetic algorithm for modular software systems. Journal of Systems and Software, 66(1), 47–55.

    Article  Google Scholar 

  19. Jha, P. C., Gupta, D., Yang, B., & Kapur, P. K. (2009). Optimal testing resource allocation during module testing considering cost, testing effort and reliability. Computers & Industrial Engineering, 57(3), 1122–1130.

    Article  Google Scholar 

  20. Kapur, P. K., Pham, H., Chanda, U., & Kumar, V. (2013). Optimal allocation of testing effort during testing and debugging phases: a control theoretic approach. International Journal of Systems Science, 44(9), 1639–1650.

    Article  MathSciNet  Google Scholar 

  21. Yang, J., Liu, Y., Xie, M., & Zhao, M. (2016). Modeling and analysis of reliability of multi-release open source software incorporating both fault detection and correction processes. Journal of Systems and Software, 115, 102–110.

    Article  Google Scholar 

  22. Jiang, Z., Sarkar, S., & Jacob, V. S. (2012). Postrelease testing and software release policy for enterprise-level systems. Information Systems Research, 23(3-part-1), 635–657.

    Article  Google Scholar 

  23. Okumoto, K., & Goel, A. L. (1980). Optimum release time for software systems based on reliability and cost criteria. Journal of Systems and Software, 1(4), 315–318.

    Google Scholar 

  24. Yamada, S., & Osaki, S. (1987). Optimal software release policies with simultaneous cost and reliability requirements. European Journal of Operational Research, 31(1), 46–51.

    Article  MathSciNet  Google Scholar 

  25. Kapur, P. K., & Garg, R. B. (1991). Optimal release policies for software systems with testing effort. International Journal of Systems Science, 22(9), 1563–1571.

    Article  Google Scholar 

  26. Xie, M., & Yang, B. (2003). A study of the effect of imperfect debugging on software development cost. IEEE Transactions on Software Engineering, 29(5), 471–473.

    Article  Google Scholar 

  27. Huang, C. Y. (2005). Performance analysis of software reliability growth models with testing-effort and change-point. Journal of Systems and Software, 76(2), 181–194.

    Article  MathSciNet  Google Scholar 

  28. Huang, C. Y., & Lyu, M. R. (2005). Optimal release time for software systems considering cost, testing-effort, and test efficiency. IEEE Transactions on Reliability, 54(4), 583–591.

    Article  Google Scholar 

  29. Pham, H., & Zhang, X. (1999). Software release policies with gain in reliability justifying the costs. Annals of Software Engineering, 8(1–4), 147–166.

    Article  Google Scholar 

  30. Inoue, S., & Yamada, S. (2008, December). Optimal software release policy with change-point. In IEEE International Conference on Industrial Engineering and Engineering Management, 2008. IEEM 2008 (pp. 531–535). IEEE.

    Google Scholar 

  31. Lai, R., Garg, M., Kapur, P. K., & Liu, S. (2011). A Study of when to release a software product from the perspective of software reliability models. JSW, 6(4), 651–661.

    Article  Google Scholar 

  32. Kapur, P. K., Khatri, S. K., Tickoo, A., & Shatnawi, O. (2014). Release time determination depending on number of test runs using multi attribute utility theory. International Journal of System Assurance Engineering and Management, 5(2), 186–194.

    Article  Google Scholar 

  33. Minamino, Y., Inoue, S., & Yamada, S. (2015). Multi-attribute utility theory for estimation of optimal release time and change-point. International Journal of Reliability, Quality and Safety Engineering, 22(04), 1550019.

    Article  Google Scholar 

  34. Arora, A., Caulkins, J. P., & Telang, R. (2006). Research note—Sell first, fix later: Impact of patching on software quality. Management Sci., 52(3), 465–471.

    Article  Google Scholar 

  35. Majumdar, R., Shrivastava, A. K., Kapur, P. K., & Khatri, S. K. (2017). Release and testing stop time of a software using multi-attribute utility theory. Life Cycle Reliability and Safety Engineering, 6(1), 47–55.

    Article  Google Scholar 

  36. Kapur, P. K., Shrivastava, A. K., & Singh, O. (2017). When to release and stop testing of a software. Journal of the Indian Society for Probability and Statistics, 18(1), 19–37.

    Article  Google Scholar 

  37. Tickoo, A., Kapur, P. K., Shrivastava, A. K., & Khatri, S. K. (2016). Testing effort based modeling to determine optimal release and patching time of software. International Journal of System Assurance Engineering and Management, 7(4), 427–434.

    Article  Google Scholar 

  38. Keeney, R. L. (1971). Utility independence and preferences for multi attributed consequences. Operations Research, 19(4), 875–893.

    Article  MathSciNet  Google Scholar 

  39. Wood, A. (1996). Predicting software reliability. Computer, 29(11), 69–77.

    Article  Google Scholar 

  40. SAS. (2004). STAT User guide, Version 9.1.2. Cary, NC, USA: SAS Institute Inc.

    Google Scholar 

Download references

Acknowledgements

The research work presented in this paper is supported by grants to the third author from DST via DST PURSE phase II, India.

Author information

Authors and Affiliations

  1. Amity Center for Interdisciplinary Research, Amity University, Noida, Uttar Pradesh, India

    P. K. Kapur

  2. Department of Operational Research, University of Delhi, Delhi, India

    Saurabh Panwar, Ompal Singh & Vivek Kumar

Authors
  1. P. K. Kapur
    View author publications

    You can also search for this author in PubMed Google Scholar

  2. Saurabh Panwar
    View author publications

    You can also search for this author in PubMed Google Scholar

  3. Ompal Singh
    View author publications

    You can also search for this author in PubMed Google Scholar

  4. Vivek Kumar
    View author publications

    You can also search for this author in PubMed Google Scholar

Corresponding author

Correspondence to P. K. Kapur .

Editor information

Editors and Affiliations

  1. Bhabha Atomic Research Centre, Mumbai, Maharashtra, India

    Prabhakar V. Varde

  2. Department of Mechanical Engineering, Indian Institute of Technology Madras, Chennai, Tamil Nadu, India

    Raghu V. Prakash

  3. Bhabha Atomic Research Centre, Mumbai, Maharashtra, India

    Narendra S. Joshi

Rights and permissions

Reprints and permissions

Copyright information

© 2019 Springer Nature Singapore Pte Ltd.

About this chapter

Check for updates. Verify currency and authenticity via CrossMark

Cite this chapter

Kapur, P.K., Panwar, S., Singh, O., Kumar, V. (2019). Joint Release and Testing Stop Time Policy with Testing-Effort and Change Point. In: Varde, P., Prakash, R., Joshi, N. (eds) Risk Based Technologies. Springer, Singapore. https://doi.org/10.1007/978-981-13-5796-1_12

Download citation

  • DOI: https://doi.org/10.1007/978-981-13-5796-1_12

  • Published:

  • Publisher Name: Springer, Singapore

  • Print ISBN: 978-981-13-5795-4

  • Online ISBN: 978-981-13-5796-1

  • eBook Packages: EngineeringEngineering (R0)

Publish with us

Policies and ethics

Search

Navigation