• Journal of Korean Society of Industrial and Systems Engineering
• /
• v.9 no.13
• /
• pp.29-32
• /
• 1986

A decision procedure to determine when computer software should be released after testing is described. This paper extends optimum release policies minimizing the total expected software cost with a scheduled software delivery time under reliability requirement constraint. Such cost considerations enable us to make a release decision as to when transfer a software system from testing phase to operational phase. The underlying model is software reliability growth model described by a nonhomogeneous poisson process. It is assumed that the penalty cost function due to delay for a scheduled software delivery time is linearly proportional to time. Numerical examples are shown to illustrate the results.

• The KIPS Transactions:PartD
• /
• v.8D no.6
• /
• pp.835-842
• /
• 2001

We propose a software-reliability growth model incoporating the amount of testing effort expended during the software testing phase. The time-dependent behavior of testing effort expenditures is described by a Weibull curve. Assuming that the error detection rate to the amount of testing effort spent during the testing phase is proportional to the current error content, a software-reliability growth model is formulated by a nonhomogeneous Poisson process. Using this model the method of data analysis for software reliability measurement is developed. After defining a software reliability, we discuss the relations between testing time and reliability and between duration following failure fixing and reliability are studied in this paper. The release time making the testing cost to be minimum is determined through studying the cost for each condition. Also, the release time is determined depending on the conditions of the specified reliability. The optimum release time is determined by simultaneously studying optimum release time issue that determines both the cost related time and the specified reliability related time.

• Proceedings of the Korean Reliability Society Conference
• /
• 2002.06a
• /
• pp.273-273
• /
• 2002

In this paper, we investigate a software release policy with software reliability growth factor during the warranty period by assuming that the software reliability growth is assumed to occur after the testing phase with probability p and the software reliability growth is not assumed to occur after the testing phase with probability 1-p. The optimal release policy to minimize the expected total software cost is discussed. Numerical examples are shown to illustrate the results of the optimal policy. And we consider a Bayesian decision theoretic approach to determine an optimal software release policy. This approach enables us to update our uncertainty when determining optimal software release time, When the failure time is Weibull distribution with uncertain parameters, a bayesian approach is established. Finally, numerical examples are presented for illustrative propose.

• Proceedings of the IEEK Conference
• /
• 2005.11a
• /
• pp.1109-1112
• /
• 2005

The software reliability is defined, and not only the relations between testing time and reliability, but also the relation between duration following failure fixing and reliability are studied in this paper. The release time making the testing cost to be minimum is determined through evaluating the cost for each condition. Also, the release time is determined depending on the conditions of the first reliability, considering the specified reliability. The optimum release time is determined by simultaneously studying two optimum release time issues that determine both the cost related time and the specified reliability related time. And, each condition and limitation are studied. The trend of the optimum time is also examined.

• The Transactions of the Korean Institute of Electrical Engineers D
• /
• v.51 no.1
• /
• pp.18-25
• /
• 2002

The software reliability is defined, and not only the relations between testing time and reliability, but also the relation between duration following failure fixing and reliability are studied in this paper. The release time making the testing cost to be minimum is determined through evaluating the cost for each condition. Also, the release time is determined depending on the conditions of the first reliability, considering the specified reliability. the optimum release time is determined by simultaneously studying two optimum release time issues that determine both the cost related time and the specified reliability related time. And, each condition and limitation are studied. The trend of the optimum time is also examined.

• The Transactions of the Korea Information Processing Society
• /
• v.5 no.5
• /
• pp.1225-1233
• /
• 1998

An important issue for software developers is to determine when to stop testing the software system and release it to users. Generally the release time is specified by the number of detected faults or the testing time needed to meet the reliability requirement. Software reliability directly depends on the number of remaining or corrected faults. All the detected faults are not always corrected under imperfect debugging environment. We therefore need a new approach to software release policy for imperfect debugging. This paper suggests a software release policy, which guarantees that the reliability requirement has been achieved. The suggested policy is then implemented and illustrated for specific SRGMs.

• Communications for Statistical Applications and Methods
• /
• v.12 no.3
• /
• pp.673-682
• /
• 2005

In this paper, we generalize the software reliability growth model by assuming that the testing cost and maintenance cost are random and adopt the Bayesian approach to determine the optimal software release time. Numerical examples are provided to illustrate the Bayesian method for certain parametric models.

• Journal of Korean Society for Quality Management
• /
• v.26 no.3
• /
• pp.141-149
• /
• 1998

It is of great practical interest to decide when to stop testing a software system in the development phase and transfer it to the user. This decision problemcalled an optimal software release one is discussed to specify the a, pp.opriate release time. In almost all studies, the software reliability models used are nonphomogenous Poisson process(NHPP) model with bounded mean value function. HNPP models with unbounded mean value function are more suitable in practice because of the possibility of introducing new faults when correcting or modifying the software. We discuss optimal software release policies which minimize a total average software cost under the constraint of satisfying a software reliability requirement. A numerical example illustrates the results.

• Journal of the Korea Society of Computer and Information
• /
• v.14 no.8
• /
• pp.1-9
• /
• 2009

In this paper, make a study decision problem called an optimal release policies after testing a software system in development phase and transfer it to the user. When correcting or modifying the software, because of the possibility of introducing new faults when correcting or modifying the software, infinite failure non-homogeneous Poisson process models presented and propose an optimal release policies of the life distribution applied fixed shape parameter distribution which can capture the increasing/decreasing nature of the failure occurrence rate per fault. In this paper, discuss optimal software release policies which minimize a total average software cost of development and maintenance under the constraint of satisfying a software reliability requirement. In a numerical example, after trend test applied and estimated the parameters using maximum likelihood estimation of inter-failure time data, make out estimating software optimal release time

• Journal of Korean Society for Quality Management
• /
• v.17 no.2
• /
• pp.27-35
• /
• 1989

Software developers often allocate a significant amount of effort to software testing. But for most business-related software system it is natural to expect the continued discovery of defects after the software system is released into field. Such defects are usually very expensive to fix and have the potential to cause great damages to the users. It is important to stop testing the software and release it to the users at the correct time. In this paper, we propose the determination of the optimal number of software test oy minimizing a total expected software cost. A numerical example is used when the criterion is the expected profit. The result indicates that the proposed software release policy based on the number of software test can be a good alternative to the existing policy.