• Proceedings of the Safety Management and Science Conference
• /
• 2011.04a
• /
• pp.451-459
• /
• 2011

In this paper, a software release model is presented to determine the optimum testing time with consideration of software error type. The software errors are classified into two types, major and minor errors. The software testing is continued until the Nth major error is discovered and corrected. The total cost needed before and after testing time is modeled under nonhomogeneous Poisson error correction model. Numerical examples are presented to demonstrate the results.

• 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.

• 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.

• Journal of Software Assessment and Valuation
• /
• v.16 no.2
• /
• pp.69-76
• /
• 2020

In this paper, the problem of determining the optimal time to market of software was studied using error correction time, an indicator of error correction difficulty. In particular, it was intended to modify the assumption that error detection time and correction time are independent in the software reliability growth model considering the existing error correction time, and to establish a general framework model that expresses the correlation between error detection time and correction time to determine when the software will be released. The results showed that it was important from an economic perspective to detect errors that took time to correct early in the test. It was concluded that it was very important to analyze the correlation between error detection time and error correction time in determining when to release the optimal software.

• 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 Korean Institute of Electrical Engineers D
• /
• v.49 no.5
• /
• pp.264-268
• /
• 2000

In discuss how the existing study results that decide optimum release time are rational and reasonable, considering the cost and reliability simultaneously in this paper. As a study method this paper examines the proposed results and their methodologies centering around the existing related papers for the general cost-reliability optimal release policies, especially their limitation for the derived results.

• Proceedings of the Korean Operations and Management Science Society Conference
• /
• 1991.10a
• /
• pp.405-421
• /
• 1991

In this paper, faults existing in a software system is classified into three types; simple, degenerative and regenerative faults. The reliability functions and failure rates of both a software module and system which have a mixture of such faults are obtained and the expected number of failures in the system after time T is also derived. Using the formulas obtained, a cost-reliability model and an efficient algorithm for optimal software release time are proposed via nonlinear programming formulation ; minimizing the total test cost with constraints on the failure rates of each module. Application of this model to several cases are presented and it appears to be more realistic.

• Journal of Information Technology Applications and Management
• /
• v.11 no.4
• /
• pp.87-94
• /
• 2004

The software reliability growth model(SRGM) has been developed in order to estimate such reliability measures as remaining fault number, failure rate and reliability for the developing stage software. Almost of them assumed that the faults detected during testing were evetually removed. Namely, they have studied SRGM based on the assumption that the faults detected during testing were perfectly removed. The fault removing efficiency. however. IS imperfect and it is widely known as so in general. It is very difficult to remove detected fault perfectly because the fault detecting is not easy and new error may be introduced during debugging and correcting. Therefore, the fault detecting efficiency may influence the SRGM or cost of developing software. It is a very useful measure for the developing software. much helpful for the developer to evaluate the debugging efficiency, and, moreover, help to additional workloads necessary. Therefore. it is very important to evaluate the effect of imperfect dubugging in point of SRGM and cost. and may influence the optimal release time and operational budget. I extent and study the generally used reliability and cost models to the imperfect debugging range in this paper.

• Journal of Information Processing Systems
• /
• v.8 no.1
• /
• pp.21-54
• /
• 2012

As we know every software development process is pretty large and consists of different modules. This raises the idea of prioritizing different software modules so that important modules can be tested by preference. In the software testing process, it is not possible to test each and every module regressively, which is due to time and cost constraints. To deal with these constraints, this paper proposes an approach that is based on the fuzzy multi-criteria approach for prioritizing several software modules and calculates optimal time and cost for software testing by using fuzzy logic and the fault tolerance approach.