14th International Symposium on Software Reliability Engineering When Does It Pay to Make Software More Reliable? Denver, Colorado November 17-November 21 ISBN: 0-7695-2007-3
Substantial work has been done in the area of software fault analysis, prediction and evaluation. Some work considers the relationship between failures and cost. Unfortunately, current work does not address the issues of revenues, return on investment, or time-value of money. These shortcomings limit the usefulness and acceptance of software reliability within industry. To address these shortcomings, we have developed an Economic Reliability Analysis [ERA] framework at the University of Virginia, that fuses reliability engineering methods with economic analysis.We introduce the [ERA] framework to the software reliability community and fuse it with the Musa/Okumoto NHPP software reliability model to estimate the economic impact of operational software faults. This framework defines a set of economic vectors that are calculated using the software reliability model along with a few additional financial elements. This extended software reliability model is then used to evaluate an operational software system with three different proposed software upgrades. All four software systems are analyzed and compared. This analysis provides a more complete method to apply software reliability modeling techniques to existing software systems and proposed design changes.
Index Terms:
Software reliability models, Musa/Okumoto NHPP model, Discounted cash flow, Economic worth, Net Present Value
Citation:
Ed Stoker, Joanne Bechta Dugan, "When Does It Pay to Make Software More Reliable?," issre, pp.321, 14th International Symposium on Software Reliability Engineering, 2003 Usage of this product signifies your acceptance of the Terms of Use. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||