IDEAS home Printed from https://ideas.repec.org/a/spr/ijsaem/v7y2016i4d10.1007_s13198-016-0510-7.html
   My bibliography  Save this article

Optimal release and patching time of software with warranty

Author

Listed:
  • Yogita Kansal

    (Amity University)

  • Gurinder Singh

    (Amity University)

  • Uday Kumar

    (Luleå University of Technology)

  • P. K. Kapur

    (Amity University)

Abstract

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.

Suggested Citation

  • Yogita Kansal & Gurinder Singh & Uday Kumar & P. K. Kapur, 2016. "Optimal release and patching time of software with warranty," International Journal of System Assurance Engineering and Management, Springer;The Society for Reliability, Engineering Quality and Operations Management (SREQOM),India, and Division of Operation and Maintenance, Lulea University of Technology, Sweden, vol. 7(4), pages 462-468, December.
    • Handle: RePEc:spr:ijsaem:v:7:y:2016:i:4:d:10.1007_s13198-016-0510-7
    DOI: 10.1007/s13198-016-0510-7
    as

    Download full text from publisher

    File URL: http://link.springer.com/10.1007/s13198-016-0510-7
    File Function: Abstract
    Download Restriction: Access to the full text of the articles in this series is restricted.
    File URL: https://libkey.io/10.1007/s13198-016-0510-7?utm_source=ideas
    LibKey link: if access is restricted and if your library uses this service, LibKey will redirect you to where you can use your library subscription to access this item
    ---><---

    As the access to this document is restricted, you may want to search for a different version of it.

    References listed on IDEAS

    as
    1. Ashish Arora & Jonathan P. Caulkins & Rahul Telang, 2006. "Research Note--Sell First, Fix Later: Impact of Patching on Software Quality," Management Science, INFORMS, vol. 52(3), pages 465-471, March.
    2. Hasan Cavusoglu & Huseyin Cavusoglu & Jun Zhang, 2008. "Security Patch Management: Share the Burden or Share the Damage?," Management Science, INFORMS, vol. 54(4), pages 657-670, April.
    3. Yamada, Shigeru & Osaki, Shunji, 1987. "Optimal software release policies with simultaneous cost and reliability requirements," European Journal of Operational Research, Elsevier, vol. 31(1), pages 46-51, July.
    4. Debabrata Dey & Atanu Lahiri & Guoying Zhang, 2015. "Optimal Policies for Security Patch Management," INFORMS Journal on Computing, INFORMS, vol. 27(3), pages 462-477, August.
    5. P.K. Kapur & Hoang Pham & A. Gupta & P.C. Jha, 2011. "Software Reliability Assessment with OR Applications," Springer Series in Reliability Engineering, Springer, number 978-0-85729-204-9, March.
    Full references (including those not matched with items on IDEAS)

    Citations

    Citations are extracted by the CitEc Project, subscribe to its RSS feed for this item.
    as


    Cited by:

    1. Luo, Ming & Wu, Shaomin, 2019. "A comprehensive analysis of warranty claims and optimal policies," European Journal of Operational Research, Elsevier, vol. 276(1), pages 144-159.

    Most related items

    These are the items that most often cite the same works as this one and are cited by the same works as this one.
    1. Anshul Tickoo & P. K. Kapur & A. K. Shrivastava & Sunil K. Khatri, 2016. "Testing effort based modeling to determine optimal release and patching time of software," International Journal of System Assurance Engineering and Management, Springer;The Society for Reliability, Engineering Quality and Operations Management (SREQOM),India, and Division of Operation and Maintenance, Lulea University of Technology, Sweden, vol. 7(4), pages 427-434, December.
    2. Terrence August & Marius Florin Niculescu, 2013. "The Influence of Software Process Maturity and Customer Error Reporting on Software Release and Pricing," Management Science, INFORMS, vol. 59(12), pages 2702-2726, December.
    3. Debabrata Dey & Atanu Lahiri & Guoying Zhang, 2015. "Optimal Policies for Security Patch Management," INFORMS Journal on Computing, INFORMS, vol. 27(3), pages 462-477, August.
    4. Terrence August & Duy Dao & Kihoon Kim, 2019. "Market Segmentation and Software Security: Pricing Patching Rights," Management Science, INFORMS, vol. 65(10), pages 4575-4597, October.
    5. Li, Bo & Tan, Zhen & Arreola-Risa, Antonio & Huang, Yiwei, 2023. "On the improvement of uncertain cloud service capacity," International Journal of Production Economics, Elsevier, vol. 258(C).
    6. Avinash K. Shrivastava & Vivek Kumar & P. K. Kapur & Ompal Singh, 0. "Software release and testing stop time decision with change point," International Journal of System Assurance Engineering and Management, Springer;The Society for Reliability, Engineering Quality and Operations Management (SREQOM),India, and Division of Operation and Maintenance, Lulea University of Technology, Sweden, vol. 0, pages 1-12.
    7. P. K. Kapur & Saurabh Panwar & Ompal Singh & Vivek Kumar, 2022. "Joint optimization of software time-to-market and testing duration using multi-attribute utility theory," Annals of Operations Research, Springer, vol. 312(1), pages 305-332, May.
    8. Terrence August & Duy Dao & Marius Florin Niculescu, 2022. "Economics of Ransomware: Risk Interdependence and Large-Scale Attacks," Management Science, INFORMS, vol. 68(12), pages 8979-9002, December.
    9. Avinash K. Shrivastava & Vivek Kumar & P. K. Kapur & Ompal Singh, 2020. "Software release and testing stop time decision with change point," International Journal of System Assurance Engineering and Management, Springer;The Society for Reliability, Engineering Quality and Operations Management (SREQOM),India, and Division of Operation and Maintenance, Lulea University of Technology, Sweden, vol. 11(2), pages 196-207, July.
    10. Vidyanand Choudhary & Zhe (James) Zhang, 2015. "Research Note—Patching the Cloud: The Impact of SaaS on Patching Strategy and the Timing of Software Release," Information Systems Research, INFORMS, vol. 26(4), pages 845-858, December.
    11. Arora, Ashish & Forman, Chris & Nandkumar, Anand & Telang, Rahul, 2010. "Competition and patching of security vulnerabilities: An empirical analysis," Information Economics and Policy, Elsevier, vol. 22(2), pages 164-177, May.
    12. Viral Gupta & P. K. Kapur & Deepak Kumar, 2019. "Prioritizing and Optimizing Disaster Recovery Solution using Analytic Network Process and Multi Attribute Utility Theory," International Journal of Information Technology & Decision Making (IJITDM), World Scientific Publishing Co. Pte. Ltd., vol. 18(01), pages 171-207, January.
    13. Vibha Verma & Sameer Anand & P. K. Kapur & Anu G. Aggarwal, 2022. "Unified framework to assess software reliability and determine optimal release time in presence of fault reduction factor, error generation and fault removal efficiency," International Journal of System Assurance Engineering and Management, Springer;The Society for Reliability, Engineering Quality and Operations Management (SREQOM),India, and Division of Operation and Maintenance, Lulea University of Technology, Sweden, vol. 13(5), pages 2429-2441, October.
    14. Yeh, Wei-Chang, 2017. "Evaluation of the one-to-all-target-subsets reliability of a novel deterioration-effect acyclic multi-state information network," Reliability Engineering and System Safety, Elsevier, vol. 166(C), pages 132-137.
    15. Subhashis Chatterjee & Ankur Shukla, 2016. "Change point–based software reliability model under imperfect debugging with revised concept of fault dependency," Journal of Risk and Reliability, , vol. 230(6), pages 579-597, December.
    16. Yoshinobu Tamura & Shigeru Yamada, 2016. "Reliability computing and management considering the network traffic for a cloud computing," Annals of Operations Research, Springer, vol. 244(1), pages 163-176, September.
    17. Chao Luo & Hiroyuki Okamura & Tadashi Dohi, 2016. "Optimal planning for open source software updates," Journal of Risk and Reliability, , vol. 230(1), pages 44-53, February.
    18. Doroudi, Sherwin & Avgerinos, Thanassis & Harchol-Balter, Mor, 2021. "To clean or not to clean: Malware removal strategies for servers under load," European Journal of Operational Research, Elsevier, vol. 292(2), pages 596-609.
    19. Avinash K. Shrivastava & Armaan Singh Ahluwalia & P. K. Kapur, 0. "On interdisciplinarity between product adoption and vulnerability discovery modeling," International Journal of System Assurance Engineering and Management, Springer;The Society for Reliability, Engineering Quality and Operations Management (SREQOM),India, and Division of Operation and Maintenance, Lulea University of Technology, Sweden, vol. 0, pages 1-12.
    20. Yoshinobu Tamura & Shigeru Yamada, 2022. "Prototype of 3D Reliability Assessment Tool Based on Deep Learning for Edge OSS Computing," Mathematics, MDPI, vol. 10(9), pages 1-20, May.

    Corrections

    All material on this site has been provided by the respective publishers and authors. You can help correct errors and omissions. When requesting a correction, please mention this item's handle: RePEc:spr:ijsaem:v:7:y:2016:i:4:d:10.1007_s13198-016-0510-7. See general information about how to correct material in RePEc.

    If you have authored this item and are not yet registered with RePEc, we encourage you to do it here. This allows to link your profile to this item. It also allows you to accept potential citations to this item that we are uncertain about.

    If CitEc recognized a bibliographic reference but did not link an item in RePEc to it, you can help with this form .

    If you know of missing items citing this one, you can help us creating those links by adding the relevant references in the same way as above, for each refering item. If you are a registered author of this item, you may also want to check the "citations" tab in your RePEc Author Service profile, as there may be some citations waiting for confirmation.

    For technical questions regarding this item, or to correct its authors, title, abstract, bibliographic or download information, contact: Sonal Shukla or Springer Nature Abstracting and Indexing (email available below). General contact details of provider: http://www.springer.com .

    Please note that corrections may take a couple of weeks to filter through the various RePEc services.

    IDEAS is a RePEc service. RePEc uses bibliographic data supplied by the respective publishers.