Welcome to the InfoSci Platform
Reference Hub2
Optimal Release Policy for Multi-Release Software System

Optimal Release Policy for Multi-Release Software System

Anu G. Aggarwal, Chandra K. Jaggi, Nidhi Nijhawan
Copyright: © 2017 |Volume: 8 |Issue: 3 |Pages: 18
ISSN: 1947-9328|EISSN: 1947-9336|EISBN13: 9781522513315|DOI: 10.4018/IJORIS.2017070102
Cite Article Cite Article

MLA

Aggarwal, Anu G., et al. "Optimal Release Policy for Multi-Release Software System." IJORIS vol.8, no.3 2017: pp.21-38. http://doi.org/10.4018/IJORIS.2017070102

APA

Aggarwal, A. G., Jaggi, C. K., & Nijhawan, N. (2017). Optimal Release Policy for Multi-Release Software System. International Journal of Operations Research and Information Systems (IJORIS), 8(3), 21-38. http://doi.org/10.4018/IJORIS.2017070102

Chicago

Aggarwal, Anu G., Chandra K. Jaggi, and Nidhi Nijhawan. "Optimal Release Policy for Multi-Release Software System," International Journal of Operations Research and Information Systems (IJORIS) 8, no.3: 21-38. http://doi.org/10.4018/IJORIS.2017070102

Export Reference

Mendeley
Favorite Full-Issue Download

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.

Request Access

You do not own this content. Please login to recommend this title to your institution's librarian or purchase it from the IGI Global bookstore.