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

• Journal of Information Technology Applications and Management
• /
• v.11 no.2
• /
• pp.191-204
• /
• 2004

Many software reliability growth model(SRGM) have been proposed for past several decades. 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. We consider the methology to evaluate the SRGN using least square estimator(LSE) and maximum likelihood estimator(MLE) for those 4 functions, and then examine parameters applying actual data adopted from real field test of developing S/W.

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

• Journal of Korea Society of Industrial Information Systems
• /
• v.14 no.5
• /
• pp.61-73
• /
• 2009

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 estimater and maximum likelihood estimater for those 4 functions, and then examine parameters applying actual data adopted from real field test of developing S/W.

• The KIPS Transactions:PartD
• /
• v.11D no.1
• /
• pp.173-182
• /
• 2004

The research to estimate development effort of software has been progress. But, it is not easy gain that testing data for estimating of development effort. Also, if we get the testing data, it is important that analysis testing data. In this paper, we study the data analysis of software development effort using the 789 software development projects which developed in the 1990's. Software development scale and software development team site are various. Using the characteristic of factor, we have to study characteristic of data and we estimate the development effort step by step. First, we prove the difference of development effort with the 789 project data according to development type, development environment, the development language etc. Also, we execute the crosstabs analysis that team site and function point.

• The KIPS Transactions:PartD
• /
• v.11D no.4
• /
• pp.885-892
• /
• 2004

Weibull distribution Iincluding Rayleigh and Exponential distribution is a typical model to estimate the effort distribution which is committed to the software testing phase. This model does not represent standpoint that many efforts are committed actually at the test beginning point. Moreover, it does not properly represent the various distribution form of actual test effort. To solve these problems, this paper proposes the Sigmoid model. The sigmoid function to be applicable in neural network transformed into the function which properly represents the test effort of software in the model. The model was verified to the six test effort data which were got from actual software projects which have various distribution form and verified the suitability. The Sigmoid model nay be selected by the alternative of Weibull model to estimate software test effort because it is superior than the Weibull model.

• Journal of the Korea Institute of Information and Communication Engineering
• /
• v.12 no.4
• /
• pp.737-743
• /
• 2008

I compare my parameter estimation methodoloay with existing method, considering both of testing effort and fault detecting rate simultaneously in software reliability modeling. Generally speaking, fault detection/removal mechanism depends on how apply previous fault detection/removal and testing effort of S/W. The fault removal efficiency makes large influence to the reliability growth, testing and removal cost in developing stage S/W. This is very useful measure during all the developing stages and much helpful for the developer to estimate debugging efficiency, and furthermore, to anticipate additional working amount.

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