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

• International Journal of Reliability and Applications
• /
• v.2 no.3
• /
• pp.147-160
• /
• 2001

The reliability of computer software is of prime importance for all developers of software. The complicated nature of detecting and removing faults from software has led to a plethora of models for reliability growth. One of the most basic of these is the Jelinski Moranda model, where it is assumed that there are N faults in the software, and that in testing, bugs (or faults) are encountered (and removed when defected) according to a stochastic process at a rate which at a given point in time is proportional to the number of bugs remaining in the system. In this research, we consider the possibility that imperfect repair may occur in any attempt to remove a detected bug in the Jelinski Moranda model. We let p represent the probability that a fault which is discovered or detected is actually perfectly repaired. The possibility that the probability p may differ before and after release of the software is also considered. The distribution of both the number of bugs detected and perfectly repaired in a given time period is studied. Cost models for the development and release of software are investigated, and the impact of the parameter p on the optimal release time minimizing expected costs is assessed.

• Journal of the military operations research society of Korea
• /
• v.16 no.2
• /
• pp.135-150
• /
• 1990

This paper classifies faults into three types : simple, degenerated, and regenerated faults. This paper also deals with the characteristics of each type of fault to determine the software reliability based on the assumption; i. e., a system consisting of several subsystems (modules) which may be debugged simultaneously. For each type of fault, several formulas are developed to obtain the failure rate and the expected number of failures found during debugging. A model is developed based on the formulas of the failure rate and the expected number of failures to decide the optimal release time of a new software: minimizing the total cost with constraints restricting to the failure rate of each module in the software. By using this model, optimal release times are found for some cases; the eliminated faults are assumed simple faults only, regenerated faults only, simple and degenerated faults, and so on.

• Proceedings of the Korean Reliability Society Conference
• /
• 2005.06a
• /
• pp.251-257
• /
• 2005

Software system which is essential in operating the computer has gradually become an indispensable element in many aspects of our daily lives and an important factor in numerous systems. In recent years, software cost sometimes exceeds the cost of maintaining the hardware system. In addition to the cost necessary to develop the new software system and to maintain the system, the penalty costs incurred due to software failures are even more significant. In this paper, a cost model incorporating the warranty cost, debugging costto remove each fault detected in the software system, and delivery delay cost is developed. A software reliability model based on non-homogeneous Poisson process(NHPP) is established and the optimal software release policies to minimize the expected total software cost are discussed. Numerical examples are provided to illustrate the results.

• The Journal of Korea Institute of Information, Electronics, and Communication Technology
• /
• v.12 no.6
• /
• pp.554-560
• /
• 2019

In this study, after applying the finite failure NHPP Rayleigh distribution model and NHPP Inverse Rayleigh distribution model which are widely used in the field of software reliability to the software development cost model, the attributes of development cost and optimal release time were compared and analyzed. To analyze the attributes of software development cost, software failure time data was used, parametric estimation was applied to the maximum likelihood estimation method, and nonlinear equations were calculated using the bisection method. As a result, it was confirmed that Rayleigh model is relatively superior to Inverse Rayleigh model because software development cost is relatively low and software release time is also fast. Through this study, the development cost attributes of the Rayleigh model and the Inverse Rayleigh model without the existing research examples were newly analyzed. In addition, we expect that software developers will be able to use this study as a basic guideline for exploring software reliability improvement method and development cost attributes.

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

• Proceedings of the IEEK Conference
• /
• 1998.10a
• /
• pp.221-224
• /
• 1998

Software release over the network is the most efficacious way of software update. Software release of electronic switching system, considering its environments, is the typical case that is in need of adopting the method. The media of transferring software and data of TDX-10A electronic switching system are magnetic tapes containing them, so the MT must be delivered between remotely placed office and package generation system. SMART-10A system provides the file tranfer on the data network between TDX-10A and the package generation system and ability of remote application of new software. This paper shows the implementation of file transfer between TDX-10A and computer system connected by data networks, status handling for duplicated system, and monitor process design with IPC on UNIX system.

• Journal of Information Technology Applications and Management
• /
• v.12 no.2
• /
• pp.1-13
• /
• 2005

This paper proposes a software-reliability growth model incoporating the amount of testing effort expended during the software testing phase after developing it. The time-dependent behavior of testing effort expenditures is described by a Logistic 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, This paper discusses the relations between testing time and reliability and between duration following failure fixing and reliability are studied. SRGM in several literatures has used the exponential curve, Railleigh curve or Weibull curve as an amount of testing effort during software testing phase. However, it might not be appropriate to represent the consumption curve for testing effort by one of already proposed curves in some software development environments. Therefore, this paper shows that a logistic testing-effort function can be adequately expressed as a software development/testing effort curve and that it gives a good predictive capability based on real failure data.

• Asia-Pacific Journal of Business Venturing and Entrepreneurship
• /
• v.7 no.4
• /
• pp.49-54
• /
• 2012

In this paper, a software policy considering testing time and the number of errors corrected is presented. The software is tested until a specified testing time or the time to a specified number of errors are corrected, whichever comes first. The model includes the cost of error correction and software testing during the testing time, and the cost of error correction during operation. It is assumed that the length of software life cycle has no bounds, and the error correction follows an non-homogeneous Poisson process. An expression for the total cost under the policy is derived. It is shown that the model includes the previous models as special cases.

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