Author List: Jiang, Zhengrui; Sarkar, Sumit; Jacob, Varghese S.;
Information Systems Research, 2012, Volume 23, Issue 3, Page 635-657.
Prior work on software release policy implicitly assumes that testing stops at the time of software release. In this research, we propose an alternative release policy for custom-built enterprise-level software projects that allows testing to continue for an additional period after the software product is released. Our analytical results show that the software release policy with postrelease testing has several important advantages over the policy without postrelease testing. First, the total expected cost is lower. Second, even though the optimal time to release the software is shortened, the reliability of the software is improved throughout its lifecycle. Third, although the expected number of undetected bugs is higher at the time of release, the expected number of software failures in the field is reduced. We also analyze the impact of market uncertainty on the release policy and find that all our prior findings remain valid. Finally, we examine a comprehensive scenario where in addition to uncertain market opportunity cost, testing resources allocated to the focal project can change before the end of testing. Interestingly, the software should be released earlier when testing resources are to be reduced after release.
Keywords: Bayes risk principle; learning; market opportunity cost; market uncertainty; software reliability
Algorithm:

List of Topics

#260 0.314 policy movie demand features region effort second threshold release paid number regions analyze period respect availability released lower effect results
#232 0.161 software development product functionality period upgrade sampling examines extent suggests factors considered useful uncertainty previous called complementarities greater cost present
#151 0.156 costs cost switching reduce transaction increase benefits time economic production transactions savings reduction impact services reduced affect expected optimal associated
#96 0.153 errors error construction testing spreadsheet recovery phase spreadsheets number failures inspection better studies modules rate replicated detection correction optimal discovering
#139 0.055 project projects failure software commitment escalation cost factors study problem resources continue prior escalate overruns taken failing troubled sunk fail