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

This paper is concerned with forecasting the existing number of errors in the computer software and optimizing the stopping time of the software test based upon the forecasted number of errors. The most commonly used models have assessed software reliability under the assumption that the software failure late is proportional to the current fault content of the software but invariant to time since software faults are independents of others and equally likely to cause a failure during testing. In practice, it has been observed that in many situations, the failure rate decrease. Hence, this paper proposes a mathematical model to describe testing situations where the failure rate of software limearly decreases proportional to testing time. The least square method is used to estimate parameters of the mathematical model. A cost model to optimize the software testing time is also proposed. In this cost mode two cost factors are considered. The first cost is to test execution cost directly proportional to test time and the second cost is the failure cost incurred after delivery of the software to user. The failure cost is assumed to be proportional to the number of errors remained in the software at the test stopping time. The optimal stopping time is determined to minimize the total cost, which is the sum of test execution cast and the failure cost. A numerical example is solved to illustrate the proposed procedure.

• The Journal of Korea Institute of Information, Electronics, and Communication Technology
• /
• v.9 no.4
• /
• pp.351-358
• /
• 2016

Science and technology is developing rapidly as more powerful software with the rapid development of software testing and reliability assessment by the difficulty increases with the complexity of the software features of the larger increases NHPP software reliability models for failure analysis can have, in the literature, exhibit either constant, monotonic increasing or monotonic decreasing failure occurrence rates per fault. In this paper, finite failure NHPP models that assuming the expected value of the defect and infinite failures NHPP models that repairing software failure point in time reflects the situation, were presented for comparing property. Commonly used in the field of software reliability based on Erlang distribution software reliability model finite failures and infinite failures were presented for performance comparative evaluation problem. As a result, finite failure model is better than infinite failure model effectively. The parameters estimation using maximum likelihood estimation in the course of this study was conducted. As the results of this research, software developers to identify software failure property be able to help is concluded.

• The Journal of Korea Institute of Information, Electronics, and Communication Technology
• /
• v.9 no.6
• /
• pp.566-572
• /
• 2016

Software Reliability implemented in software development is one of the most important issues. In finite failure NHPP software reliability models for software failure analysis, the hazard function that means a failure rate may have constant independently for failure time, non-increasing or non-decreasing pattern. In this study, software development cost analysis considering the variable shape parameter of Erlang distribution as the failure life distribution in the software product testing process was studied. The software failure model was applied finite failure Non-Homogeneous Poisson Procedure and the parameters approximation using maximum likelihood estimation was accompanied. Thus, this paper was presented comparative analysis by applying a software failure time data to the software, considering the shape parameter of Erlang distribution for development cost model analysis. When compared to the cost curve in accordance with the shape parameter, the model of smaller shape can be seen that the optimal software release time delay and more cost. Through this study, it is thought that it can serve as a preliminary information which can basically help the software developers to search for development cost according to software shape parameters.

• Journal of Information Technology Applications and Management
• /
• v.24 no.2
• /
• pp.71-80
• /
• 2017

Software reliability is one of the most elementary and important problems in software development In order to find the software failure occurrence, the instantaneous failure rate function in the Poisson process can have a constant, incremental or decreasing tendency independently of the failure time. In this study, we compared the reliability performance of the software reliability model using the parameters of Pareto life distribution with the intensity decreasing pattern and the shape parameter of Erlang life distribution with the intensity increasing and decreasing pattern in the software product testing. In order to identify the software failure environment, the parametric estimation was applied to the maximum likelihood estimation method. Therefore, in this paper, we compare and evaluate software reliability by applying software failure time data. The reliability of the Erlang and Pareto life models is shown to be higher than that of the Pareto lifetime distribution model when the shape parameter is higher and the Erlang model is more reliable when the shape parameter is higher. Through this study, the software design department will be able to help the software design by applying various life distribution and shape parameters, and providing basic knowledge using software failure analysis.

• Nuclear Engineering and Technology
• /
• v.39 no.2
• /
• pp.129-132
• /
• 2007

It is generally known that software reliability growth models such as the Jelinski-Moranda model and the Goel-Okumoto's non-homogeneous Poisson process (NHPP) model cannot be applied to safety-critical software due to a lack of software failure data. In this paper, by applying two of the most widely known software reliability growth models to sample software failure data, we demonstrate the possibility of using the software reliability growth models to prove the high reliability of safety-critical software. The high sensitivity of a piece of software's reliability to software failure data, as well as a lack of sufficient software failure data, is also identified as a possible limitation when applying the software reliability growth models to safety-critical software.

• International Journal of Quality Innovation
• /
• v.5 no.1
• /
• pp.110-121
• /
• 2004

There is a new trend of incorporating software coverage metrics into software reliability modelling. This paper proposes a coverage-based software reliability growth model. Firstly, the failure rate function in coverage is analytically derived. Then it is shown that the number of detected faults follows a Nonhomogeneous Poisson distribution of which intensity function is the failure rate function in coverage. Practical applicability of the proposed models is examined by illustrative numerical examples.

• The Journal of Korean Institute of Communications and Information Sciences
• /
• v.29 no.4A
• /
• pp.399-414
• /
• 2004

In this paper, an evolution of software reliability engineering in a large-scale software project is summarized. The considered software consists of many components, called functional blocks in software of switching system. These functional blocks are served as the unit of coding and test, and the software is continuously updated by adding new functional blocks. We are mainly concerned with the analysis of the effects of these software components in software reliability and reliability evolution. We analyze the static characteristics of the software related to software reliability using collected failure data during system test. We also discussed a pattern which represents a local and global growth of the software reliability as version evolves. To find the pattern of system software, we apply the S-shaped model to a collection of failure data sets of each evolutionary version and the Goel-Okumoto(G-O) model to a grouped overall failure data set. We expect this pattern analysis will be helpful to plan and manage necessary human/resources fur a new similar software project which is developed under the same developing circumstances by estimating the total software failures with respect to its size and time.

• Journal of Convergence for Information Technology
• /
• v.12 no.5
• /
• pp.15-20
• /
• 2022

This research studied the evaluation of reliability among the software quality characteristics: suitability, reliability, usability, portability, maintainability, performance efficiency, security, and compatibility. It proposes a quantitative evaluation of reliability in the measurement of software quality. This study introduces a method for measuring the failure rate included in maturity during reliability evaluation, which is one of the characteristics of software quality, and is a study with experimental data on how the failure rate changes depending on the form of failure data. Focusing on software testing, the failure rate was measured and compared according to the type of failure data by applying it to the software reliability growth model, focusing on the number of failures per day. The failure rate was measured around the failure time found through the 6-day test, and the failure rate was compared with the failure rate proposed by the international standard ISO/IEC 25023 using the measurement results, and the application was reviewed according to the data type.

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

The failure rate functions between successive failures are of concatenated form. We allow the parameters of failure rate function change after a certain failure and its fixing. We confine out attention to a model wherein the interfailure times are described by its failure rate function. We suggest an adaptive failure rate function with a change-point under the assumption that interfailure times are record value statistics from a Weibull distribution. The proposed model will be applied through a practical example of software failure data.

• Journal of Information Technology Applications and Management
• /
• v.23 no.4
• /
• pp.117-125
• /
• 2016

Software reliability in the software development process is an important issue. In infinite failure non-homogeneous Poisson process software reliability models, the failure occurrence rates per fault. can be presented constant, monotonic increasing or monotonic decreasing pattern. In this paper, the reliability software cost model considering decreasing intensity function was studied in the software product testing process. The decreasing intensity function that can be widely used in the field of reliability using power law process, log-linear processes and Musal-Okumoto process were studied and the parameter estimation method was used for maximum likelihood estimation. In this paper, from the software model analysis, we was compared by applying a software failure interval failure data considering the decreasing intensity function The decreasing intensity function model is also efficient in terms of reliability in the arena of the conservative model can be used as an alternating model can be established. From this paper, the software developers have to consider life distribution by preceding information of the software to classify failure modes which can be gifted to support.