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

• Journal of Korean Society for Quality Management
• /
• v.29 no.4
• /
• pp.92-102
• /
• 2001

Software testing during development and operation should exercise to obtain the desired software quality and leave failure data set. So far, many software reliability models are classified and can be used to measure a software reliability only based on its failure history But, in practice, developers or testers of software systems must decide which existing software reliability model can be fitted. In this paper, we will show that an appropriate reliability model can be selected by considering relations between characteristics of each testing environment and models' assumptions. Several methods of software testing are presented and discussed. Also, unit test, integrated test, function test and system test that are sequentially exercised during development will be introduced.

• Nuclear Engineering and Technology
• /
• v.31 no.1
• /
• pp.49-57
• /
• 1999

It has been a critical issue to predict the safety critical software reliability in nuclear engineering area. For many years, many researches have focused on the quantification of software reliability and there have been many models developed to quantify software reliability. Most software reliability models estimate the reliability with the failure data collected during the test assuming that the test environments well represent the operation profile. User's interest is however on the operational reliability rather than on the test reliability. The experiences show that the operational reliability is higher than the test reliability. With the assumption that the difference in reliability results from the change of environment, from testing to operation, testing environment factors comprising the aging factor and the coverage factor are developed in this paper and used to predict the ultimate operational reliability with the failure data in testing phase. It is by incorporating test environments applied beyond the operational profile into testing environment factors. The application results show that the proposed method can estimate the operational reliability accurately.

• International Journal of Computer Science & Network Security
• /
• v.23 no.9
• /
• pp.157-161
• /
• 2023

Reliability is one of the computable quality features of the software. To assess the reliability the software reliability growth models(SRGMS) are used at different test times based on statistical learning models. In all situations, Tradational time-based SRGMS may not be enough, and such models cannot recognize errors in small and medium sized applications.Numerous traditional reliability measures are used to test software errors during application development and testing. In the software testing and maintenance phase, however, new errors are taken into consideration in real time in order to decide the reliability estimate. In this article, we suggest using the Weibull model as a computational approach to eradicate the problem of software reliability modeling. In the suggested model, a new distribution model is suggested to improve the reliability estimation method. We compute the model developed and stabilize its efficiency with other popular software reliability growth models from the research publication. Our assessment results show that the proposed Model is worthier to S-shaped Yamada, Generalized Poisson, NHPP.

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

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

Many software reliability growth models(SRGM) have been proposed since the software reliability issue was raised in 1972. The technology to estimate and grow the reliability of developing S/W to target value during testing phase were developed using them. Most of these propositions assumed the S/W debugging testing efforts be constant or even did not consider them. A few papers were presented as the software reliability evaluation considering the testing effort was important afterwards. The testing effort forms which have been presented by this kind of papers were exponential, Rayleigh, Weibull, or logistic functions, and one of these 4 types was used as a testing effort function depending on the S/W developing circumstances. I propose the methology to evaluate the SRGM using least square estimator and maximum likelihood estimator for those 4 functions, and then examine parameters applying actual data adopted from real field test of developing S/W.

• Journal of the Korea Institute of Information and Communication Engineering
• /
• v.12 no.1
• /
• pp.1-9
• /
• 2008

The Logistic cone is studied as a most desirable for the software testing effort. 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 cure 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.

• Communications for Statistical Applications and Methods
• /
• v.20 no.6
• /
• pp.467-474
• /
• 2013

It is common to measure multiple coverage metrics during software testing. Software reliability growth models and coverage growth functions have been applied to each coverage metric to evaluate software reliability; however, analysis results for the individual coverage metrics may conflict with each other. This paper proposes the virtual coverage metric of a normalized first principal component in order to avoid conflicting cases. The use of the virtual coverage metric causes a negligible loss of information.

• Journal of Korean Institute of Industrial Engineers
• /
• v.33 no.4
• /
• pp.487-493
• /
• 2007

In this paper, we deal with an optimal software-release problem of determining the time to stop testing and release the software system to the user. The optimal release time problem is considered from maintenance like the periodic distribution of service packs and the unpredictable distribution of patches after the release. Moreover, the environment of software error-detection during operation differs from the environment during testing. This paper proposes the software reliability growth model which incorporates periodic service packs, unpredictable patches and operational environment. Based on the proposed model, we derive optimal release time to minimize total cost composed of fixing an error, testing and maintenance. Using numerical examples, optimal release time is determined and illustrated.

• Journal of Advanced Navigation Technology
• /
• v.14 no.1
• /
• pp.119-126
• /
• 2010

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 eventually 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, We want to study imperfect software testing effort for the logistic testing effort which is thought to be the most adequate in this paper.