• International Journal of Reliability and Applications
• /
• v.4 no.1
• /
• pp.1-12
• /
• 2003

Many software reliability growth models (SRGM's) based on a nonhomogeneous Poisson process (NHPP) have been proposed by many researchers. Most of the SRGM's which have been proposed up to the present treat the event of software fault-detection in the testing and operational phases as a counting process. However, if the size of the software system is large, the number of software faults detected during the testing phase becomes large, and the change of the number of faults which are detected and removed through debugging activities becomes sufficiently small compared with the initial fault content at the beginning of the testing phase. Therefore, in such a situation, we can model the software fault-detection process as a stochastic process with a continuous state space. In this paper, we propose a new software reliability growth model describing the fault-detection process by applying a mathematical technique of stochastic differential equations of an Ito type. We also compare our model with the existing SRGM's in terms of goodness-of-fit for actual data sets.

• KSII Transactions on Internet and Information Systems (TIIS)
• /
• v.15 no.3
• /
• pp.932-951
• /
• 2021

The effectiveness of testing in Model-based Testing (MBT) for Software Product Line (SPL) can be achieved by considering fault detection in test case. The lack of fault consideration caused test case in test suite to be listed randomly. Test Case Prioritization (TCP) is one of regression techniques that is adaptively capable to detect faults as early as possible by reordering test cases based on fault detection rate. However, there is a lack of studies that measured faults in MBT for SPL. This paper proposes a Test Case Prioritization (TCP) approach based on dissimilarity and string based distance called Last Minimal for Local Maximal Distance (LM-LMD) with Dice-Jaro-Winkler Dissimilarity. LM-LMD with Dice-Jaro-Winkler Dissimilarity adopts Local Maximum Distance as the prioritization algorithm and Dice-Jaro-Winkler similarity measure to evaluate distance among test cases. This work is based on the test case generated from statechart in Software Product Line (SPL) domain context. Our results are promising as LM-LMD with Dice-Jaro-Winkler Dissimilarity outperformed the original Local Maximum Distance, Global Maximum Distance and Enhanced All-yes Configuration algorithm in terms of Average Fault Detection Rate (APFD) and average prioritization time.

• Journal of the Korea Society of Computer and Information
• /
• v.20 no.5
• /
• pp.73-81
• /
• 2015

Most of the software fault prediction studies focused on the binary classification model that predicts whether an input entity has faults or not. However the ability to predict entity fault-proneness in various severity categories is more useful because not all faults have the same severity. In this paper, we propose fault prediction models at different severity levels of faults using traditional size and complexity metrics. They are ternary classification models and use four machine learning algorithms for their training. Empirical analysis is performed using two NASA public data sets and a performance measure, accuracy. The evaluation results show that backpropagation neural network model outperforms other models on both data sets, with about 81% and 88% in terms of accuracy score respectively.

• Journal of Internet Computing and Services
• /
• v.20 no.2
• /
• pp.29-37
• /
• 2019

As software development technology evolves, the quality of software has increased. But software created through sophisticated technology is still defective. The developer will be aware of the defect through a bug report and the reported defect must be fixed as soon as possible for the software to function correctly. It is important to know which component of the program is related to the reported defect and should be fixed. However, even though the developer understands the developed software, the task of tracing faults is a time-consuming task and requires effort. Therefore, if there is a way for developers to support tracing faults, they could fix defects more quickly. Because fixing defects rapidly is a factor of software reliability, fault traceability is essential and an effective method is needed. Therefore, in this paper, we propose a model-based fault traceability enhancement technique by using bug report and commit information and verify the effectiveness of the proposed technique.

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

• Journal of Korean Society for Quality Management
• /
• v.27 no.2
• /
• pp.263-276
• /
• 1999

In this paper, we consider the change request data collected from the system test of a large-scale telecommunication software and analyze the types and causes of failures. And we develop statistical models that incorporate a functional relation between the faults and some software metrics. To this end, we consider three possible regression models including a stepwise regression model and two nonlinear models. Three developed models are evaluated with respect to the predictive quality. We also discuss the advantage of proposed models and the application of our model to a new project.

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

• The KIPS Transactions:PartD
• /
• v.11D no.7 s.96
• /
• pp.1491-1498
• /
• 2004

Successful project planning relics on a good estimation of the manpower required to complete a project, together with the schedule options that may be available. Despite the extensive research done developing new and better models, existing software manpower estimation models are present only the total manpower or instantaneous manpower distribution according to the testing time for the software life-cycle. This paper suggests the manpower estimating models for software testing phase as well as testing process and debugging process in accordance with de-tected faults. This paper presents the polynomial model for effort based on testing and debugging faults. These models are verified by 5 different software project data sets with coefficient of determination and mean magnitude of relative error for adaptability of model.

• Proceedings of the Safety Management and Science Conference
• /
• 2001.05a
• /
• pp.77-81
• /
• 2001

Burn-in is a test procedure to find and eliminate the inherent initial failure of a product during or at the final stage of production process. Software testing is the validation and verification process which is used to cut off the faults from a software. The two have the common function and objective of "debugging". This article summarizes some significant models on the optimal hardware and software burn-in time, and provides the relevant paper lists. The need for the development of the unified burn-in policy of a hardware-software system is addressed.addressed.

• Journal of Integrative Natural Science
• /
• v.7 no.1
• /
• pp.67-73
• /
• 2014

We consider the mean value function for NHPP software reliability model and time series regression model in software failure data. We estimate parameters for the proposed models from two data sets. The values of SSE and MSE is presented from two data sets. We compare the predicted number of faults with the actual two data sets using the mean value function and regression curve.