The Community for Technology Leaders
Green Image
<p><b>Abstract</b>—The decision about when to release a software product commercially is not a question of when the software has attained some objectively justifiable degree of correctness. It is, rather, a question of whether the software achieves a reasonable balance among engineering objectives, market demand, customer requirements, and marketing directives of the software organization. In this paper, we present a rigorous framework for addressing this important decision. Conjugate distributions from statistical decision theory provide an attractive means of modeling the cost and rate of bugs given information acquired during software testing, as well as prior information provided by software engineers about the fidelity of the software before testing begins. In contrast to methods such as [<ref type="bib" rid="bibE09071">1</ref>] and [<ref type="bib" rid="bibE090716">15</ref>], the stopping analysis presented here yields a computationally simple rule for deciding when to release a commercial software product based on information revealed to engineers during software testing—complicated numerical procedures are not needed. Our method has the added benefits that it is sequential: It measures explicitly the costs of customer dissatisfaction associated with bugs as well as the costs of declining market position while the testing process continues; and it incorporates a practical framework for cost-criticality assessment that makes sense to professional software developers. A probabilistic model of catastrophic bugs provides another useful way of characterizing and measuring the software's expected performance after commercial release. Taken together, these tools provide a software organization with a clearer basis for making decisions about when to release a commercial software product.</p>
Software testing, reliability, decision analysis, Bayesian statistics, commercial software development.
Tom Chávez, "A Decision-Analytic Stopping Rule for Validation of Commercial Software Systems", IEEE Transactions on Software Engineering, vol. 26, no. , pp. 907-918, September 2000, doi:10.1109/32.877849
79 ms
(Ver 3.3 (11022016))