SOFTWARE RELEASE TIME BASED ON DIFFERENT MULTI-ATTRIBUTE UTILITY FUNCTIONS

The decision to release a software product will become an even more complex and important decision. A decision has strategic value when it has the potential for large prospective financial losses to a software manufacturer or its customers or end-users. A software release decision is a tradeoff between early release to capture the benefits of an earlier market introduction and the deferral of product release to the reliability. If a software product is released too early, the software manufacturer incurs post-release costs of later fixing failures. If a software product is released too late, the additional development cost and the opportunity cost of missing a market window could be substantial. These two attribute reliability and cost need to be combined to determine the optimal release time of software. This paper proposes a new practical method for determining when to stop software testing considering reliability and cost as two factors simultaneously. The proposed new decision model is based on three different weighted combination of utility function in Multi-attribute utility theory.

[1]  D. S. Bai,et al.  Optimum software release policy with random life cycle , 1990 .

[2]  Willa K. Ehrlich,et al.  Determining the cost of a stop-test decision (software reliability) , 1993, IEEE Software.

[3]  Z. Jelinski,et al.  Software reliability Research , 1972, Statistical Computer Performance Evaluation.

[4]  Roger S. Pressman,et al.  Software Engineering: A Practitioner's Approach , 1982 .

[5]  Nozer D. Singpurwalla,et al.  Determining an Optimal Time Interval for Testing and Debugging Software , 1991, IEEE Trans. Software Eng..

[6]  Ioannis Stamelos,et al.  Survival analysis on the duration of open source projects , 2010, Inf. Softw. Technol..

[7]  Shigeru Yamada,et al.  s-Shaped Software Reliability Growth Models and Their Applications , 1984, IEEE Transactions on Reliability.

[8]  Siddhartha R. Dalal,et al.  Buying with Exact Confidence , 1992 .

[9]  A. Wood,et al.  Predicting Software Reliability , 1996, Computer.

[10]  Sheldon M. Ross,et al.  Software Reliability: The Stopping Rule Problem , 1985, IEEE Transactions on Software Engineering.

[11]  R. L. Keeney,et al.  Decisions with Multiple Objectives: Preferences and Value Trade-Offs , 1977, IEEE Transactions on Systems, Man, and Cybernetics.

[12]  Shigeru Yamada,et al.  Cost-Reliability Optimal Release Policies for Software Systems , 1985, IEEE Transactions on Reliability.

[13]  Mitsuru Ohba,et al.  Software Reliability Analysis Models , 1984, IBM J. Res. Dev..

[14]  Siddhartha R. Dalal,et al.  When to Stop Testing for Large Software Systems with Changing Code , 1994, IEEE Trans. Software Eng..

[15]  Amrit L. Goel,et al.  Time-Dependent Error-Detection Rate Model for Software Reliability and Other Performance Measures , 1979, IEEE Transactions on Reliability.

[16]  Hoang Pham,et al.  A Software Cost Model with Warranty and Risk Costs , 1999, IEEE Trans. Computers.

[17]  Simon P. Wilson,et al.  Deciding How Long to Test Software , 2001 .

[18]  C. Mallows,et al.  When Should One Stop Testing Software , 1988 .

[19]  Sy-Yen Kuo,et al.  Optimal Release Times for Software Systems with Scheduled Delivery Time Based on the HGDM , 1997, IEEE Trans. Computers.

[20]  A. Chao,et al.  Reliability-estimation and stopping-rules for software testing, based on repeated appearances of bugs , 1995 .

[21]  Saeed Maghsoodloo,et al.  A Cost Model for Determining the Optimal Number of Software Test Cases , 1989, IEEE Trans. Software Eng..

[22]  Xiang Li,et al.  Reliability analysis and optimal version-updating for open source software , 2011, Inf. Softw. Technol..

[23]  Hoang Pham,et al.  Software release policies with gain in reliability justifying the costs , 1999, Ann. Softw. Eng..

[24]  Walter Freiberger,et al.  Statistical Computer Performance Evaluation , 1972 .

[25]  Harvey S. Koch,et al.  Optimal Release Time of Computer Software , 1983, IEEE Transactions on Software Engineering.

[26]  Adiel Teixeira de Almeida,et al.  A multi-criteria decision model to determine inspection intervals of condition monitoring based on delay time analysis , 2009, Reliab. Eng. Syst. Saf..

[27]  Siddhartha R. Dalal,et al.  Some Graphical Aids for Deciding When to Stop Testing Software , 1990, IEEE J. Sel. Areas Commun..

[28]  S. Yamada,et al.  Optimum software-release time considering an error-detection phenomenon during operation , 1990 .

[29]  P. K. Kapur,et al.  A Unified Approach for Developing Software Reliability Growth Models in the Presence of Imperfect Debugging and Error Generation , 2011, IEEE Transactions on Reliability.

[30]  Yiu-Wing Leung,et al.  Optimum software release time with a given cost budget , 1992, J. Syst. Softw..

[31]  S. Kumar,et al.  Contributions to Hardware and Software Reliability , 1999, Series on Quality, Reliability and Engineering Statistics.