Optimal release and patching time of software with warranty

  • Yogita KansalEmail author
  • Gurinder Singh
  • Uday Kumar
  • P. K. Kapur
Original Article


As we know in a competitive market, software firms are looking to sell their products at the earliest for maximum gains. Early delivery of a product is beneficial in terms of gaining market potential but may include some defects in it. On the other hand late delivery of a product ensures reliability but may results into disinterest of the customers. Thus, a vendor must focus on the best time for releasing the software. In recent times, early software release and updating it by providing patches in the operational phase is in trend. Also to satisfy customer’s primary concern of reliable software, firms are providing warranty on their products. Warranty period is the time in which firm provide assurance to the customers that under this period product will work properly and if any defect is found, firm will either repair or replace the software without charging the customer. But servicing during warranty period by updating with patches is also not economical from firm’s point of view. Hence it is important to find the optimal patch release time. In this paper we have proposed a generalized framework to find out the optimal release and patching time of software under warranty so that the total cost is minimized. Numerical example is given at the end to validate the proposed cost model.


Software reliability Testing Release time Patch Warranty 


  1. Arora A, Caulkins JP, Telang R (2006) Research note: sell first, fix later: impact of patching on software quality. Manag Sci 52(3):465–471CrossRefGoogle Scholar
  2. Cavusoglu Hasan, Cavusoglu Huseyin, Zhang Jun (2008) Security patch management: share the burden or share the damage? INFORMS 54:657–670Google Scholar
  3. Dey D, Lahiri A, Zhang G (2015) Optimal policies for security patch management. INFORMS J Comput 27(3):462–477MathSciNetCrossRefzbMATHGoogle Scholar
  4. Dohi T, Kaio N, Osaki S (1997) Optimal Software Release Policies with Debugging Time Lag. Int J Reliab, Qual Saf Eng 04(03):241–255CrossRefGoogle Scholar
  5. Huang CY (2005) Cost-reliability-optimal release policy for software reliability models incorporating improvements in testing efficiency. J Syst Softw 77:139–155CrossRefGoogle Scholar
  6. Jiang Z, Sarkar S, Jacob VS (2012) Post-release testing and software release policy for enterprise-level systems. Inf Syst Res 23(3, Part 1 of 2):635–657CrossRefGoogle Scholar
  7. Kapur PK, Garg RB (1989) Cost-reliability optimum release policies for software system under penalty cost. Int J Syst Sci 20:2547–2562MathSciNetCrossRefzbMATHGoogle Scholar
  8. Kapur PK, Garg RB (1991) Optimal software release policies for software systems with testing effort. Int J Syst Sci 22(9):1563–1571CrossRefGoogle Scholar
  9. Kapur PK, Singh O, Shrivastava AK (2014a) Optimal price and testing time of a software under warranty and two types of imperfect debugging. Int J Syst Assur Eng Manag 5:120–126CrossRefGoogle Scholar
  10. Kapur PK, Shrivastava AK (2015) When to release and stop testing of a software: A new Insight, published in conference proceedings of international conference on reliability, infocom technology and optimization (trends and future directions), held during October 2-4, 2015 at Amity University Uttar Pradesh, Noida., pp 1–6Google Scholar
  11. Kapur PK, Agarwal S, Garg RB (1994) Bi-criterion release policy for exponential software reliabilitygrowth models. Rech Op/Op Res 28:165–180Google Scholar
  12. Kapur PK, Pham H, Gupta A, Jha PC (2011) Software reliability assessment with OR applications. Springer Series in Reliability Engineering, LondonCrossRefzbMATHGoogle Scholar
  13. Kapur P.K, Khatri S.K, Singh O, Shrivastava A.K, (2014). When to stop testing under warranty using SRGM with change point, In the IEEE Xplore conference proceeding of International Conference on IT in Business, Industry & Govt., CSIBIG held during March 8–9, 2014 at Sri Aurobindo Institute of Technology Indore Ujjain Highway Indore, pp. 200–206Google Scholar
  14. Kapur PK, Singh O, Shrivastava AK (2014c) Optimal price and testing time of a software under warranty and two types of imperfect debugging. Int J Syst Assurance Engineering and Management 5:120–126CrossRefGoogle Scholar
  15. Luo C, Okamura H, Dohi T (2015) Optimal planning for open source software updates. Proc IMechE Part O: J Risk Reliab. doi: 10.1177/1748006x15586507 Google Scholar
  16. Okamura H, Tokuzane M, Dohi T (2009) Optimal security patch release timing under non-homogeneous vulnerability-discovery processes, Proceedings of the 20th international symposium on software reliability engineering (ISSRE ‘09), Mysuru, India, pp 120–8Google Scholar
  17. Okumoto K, Goel AL (1980) Optimum release time for software systems based on reliability and coat criteria. J Syst Softw 1:315–318CrossRefGoogle Scholar
  18. Pham H, Zhang X (1999) A software cost model with warranty and risk costs. IEEE Trans Comp 48(1):71–75CrossRefGoogle Scholar
  19. Singh O, Kapur PK, Shrivastava AK, Kumar V (2015) Release time problem with multiple constraints. Int J Syst Assur Eng Manag 6(1):83–91CrossRefGoogle Scholar
  20. The 30-year-old prank that became the first computer virus,
  21. Wood A (1996) Predicting software reliability. IEEE 29:69–77Google Scholar
  22. Yamada S (2014) Software reliability modeling: fundamentals and applications. Springer, Tokyo/HeidelbergCrossRefzbMATHGoogle Scholar
  23. Yamada S, Osaki S (1987) Optimal software release policies with simultaneous cost and reliability requirements. Eur J Oper Res 31:46–51MathSciNetCrossRefzbMATHGoogle Scholar
  24. Yang B, Xie M (2000) A study of operational and testing reliability in software reliability analysis. Reliab Eng Syst Saf 70:323–329CrossRefGoogle Scholar
  25. Yun WY, Bai DS (1990) Optimum software release policy with random life cycle. IEEE Trans Reliab 39(2):338–353CrossRefzbMATHGoogle Scholar

Copyright information

© The Society for Reliability Engineering, Quality and Operations Management (SREQOM), India and The Division of Operation and Maintenance, Lulea University of Technology, Sweden 2016

Authors and Affiliations

  • Yogita Kansal
    • 1
    Email author
  • Gurinder Singh
    • 2
  • Uday Kumar
    • 3
  • P. K. Kapur
    • 4
  1. 1.Amity Institute of Information TechnologyAmity UniversityNoidaIndia
  2. 2.Amity International Business SchoolAmity UniversityNoidaIndia
  3. 3.Luleå University of TechnologyLuleåSweden
  4. 4.Amity Center for Interdisciplinary ResearchAmity UniversityNoidaIndia

Personalised recommendations