IDEAS home Printed from https://ideas.repec.org/a/igg/joris0/v8y2017i3p21-38.html
   My bibliography  Save this article

Optimal Release Policy for Multi-Release Software System

Author

Listed:
  • Anu G. Aggarwal

    (University of Delhi, Department of Operational Research, New Delhi, India)

  • Chandra K. Jaggi

    (University of Delhi, Department of Operational Research, New Delhi, India)

  • Nidhi Nijhawan

    (University of Delhi, Department of Operational Research, New Delhi, India)

Abstract

In software industry, multi release software development process is a latest phenomenon that brings the benefits of newer technologies, while retaining the quality. In this paper, it is assumed that the development of next version or release starts immediately after the launch of the previous version and the field test of each version continues after its release so that undetected faults of just previous version along with the added faults of latest version are detected during the testing of new software code. Today's dynamic customers need timely up gradation. Therefore, to sustain user growth and satisfaction it is imperative for the developers to know the appropriate time to launch upgraded software into the market. In this paper, an optimal release policy for multi release software system has been proposed by taking into consideration the testing as well as the operational phase. A numerical example has been presented to illustrate the optimal release policy. Parameter estimation has been done using the real-life fault data set. Goodness-of-fit curves have been drawn.

Suggested Citation

  • Anu G. Aggarwal & Chandra K. Jaggi & Nidhi Nijhawan, 2017. "Optimal Release Policy for Multi-Release Software System," International Journal of Operations Research and Information Systems (IJORIS), IGI Global, vol. 8(3), pages 21-38, July.
    • Handle: RePEc:igg:joris0:v:8:y:2017:i:3:p:21-38
    as

    Download full text from publisher

    File URL: http://services.igi-global.com/resolvedoi/resolve.aspx?doi=10.4018/IJORIS.2017070102
    Download Restriction: no
    ---><---

    More about this item

    Statistics

    Access and download statistics

    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:igg:joris0:v:8:y:2017:i:3:p:21-38. 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.

    We have no bibliographic references for this item. You can help adding them by using 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: Journal Editor (email available below). General contact details of provider: https://www.igi-global.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.