Generalized software release and testing stop time policy

Abstract

Purpose

Almost everything around us is the output of software-driven machines or working with software. Software firms are working hard to meet the user’s requirements. But developing a fault-free software is not possible. Also due to market competition, firms do not want to delay their software release. But early release software comes with the problem of user reporting more failures during operations due to more number of faults lying in it. To overcome the above situation, software firms these days are releasing software with an adequate amount of testing instead of delaying the release to develop reliable software and releasing software patches post release to make the software more reliable. The paper aims to discuss these issues.

Design/methodology/approach

The authors have developed a generalized framework by assuming that testing continues beyond software release to determine the time to release and stop testing of software. As the testing team is always not skilled, hence, the rate of detection correction of faults during testing may change over time. Also, they may commit an error during software development, hence increasing the number of faults. Therefore, the authors have to consider these two factors as well in our proposed model. Further, the authors have done sensitivity analysis based on the cost-modeling parameters to check and analyze their impact on the software testing and release policy.

Findings

From the proposed model, the authors found that it is better to release early and continue testing in the post-release phase. By using this model, firms can get the benefits of early release, and at the same time, users get the benefit of post-release software reliability assurance.

Originality/value

The authors are proposing a generalized model for software scheduling.

Citation

Shrivastava, A.K. and Sachdeva, N. (2020), "Generalized software release and testing stop time policy", International Journal of Quality & Reliability Management, Vol. 37 No. 6/7, pp. 1087-1111. https://doi.org/10.1108/IJQRM-07-2019-0227