A detailed study about the characteristics of different types of faults is necessary to enhance the accuracy of software reliability estimation. Over the last three decades, some software reliability growth models have been proposed considering the possibility of existence of two types of faults in a software: (1) independent and (2) dependent faults. In these software reliability growth models, it is considered that the removal of a leading fault or independent fault causes detection of corresponding dependent faults. In practical, it is noticed that some dependent faults are possible in a software which are removed during the removal of other faults. Moreover, dependent faults may have different characteristics, which cannot be ignored. Considering these facts, a detailed study about the different characteristics of both dependent and independent faults has been performed, and based on this study, dependent faults have been categorized into different categories. Furthermore, a new software reliability growth model has been proposed with revised concept of fault dependency under imperfect debugging by introducing the fault removal proportionality. In addition, the effect of change point on model's parameters due to different environmental factors has been considered. The fault reduction factor is considered as a proportionality function. Experimental results establish the fact that the performance of the proposed model is better with respect to estimated and predicted cumulative number of faults on some real software failure datasets.

This paper presents a general software reliability growth model (SRGM) based on non-homogeneous Poisson process (NHPP) and optimal software release policy with cost and reliability criteria. The main motive of this study is to develop a software release time decision model considering maintenance cost and warranty cost under fuzzy environment. In previous studies, maintenance cost has been defined either in terms of warranty cost or fault debugging cost. In reality, maintenance cost includes the cost of free patches, updates, technical support and future enhancement. Also, it is possible that maintenance process causes the removal of software faults in the operational phase including the faults which occur outside the warranty period or warranty definition. In other words, warranty action may be included the maintenance action, but not the converse. Considering this fact, maintenance cost and warranty cost are defined separately in the proposed study. Initially, an SRGM has been proposed with the revised concept of imperfect debugging phenomenon considering fault removal efficiency (FRE). Furthermore, the effect of changes in various environmental factors on models parameters has been taken into account. Numerical examples based on real software failure data sets have been given to analyze the performance of the proposed models.

No abstract

This paper presents a unified approach to model the reliability growth of software with imperfect debugging and coverage factor. Existing testing coverage‐based software reliability growth models considered that faults present at a particular fault location are detected with certainty during the testing process. Practically, it is very difficult to detect all software faults. To overcome this limitation, a revised software reliability growth model has been developed with the assumption that detection of the faults at a particular fault location is not definite. Furthermore, a new method to model the imperfect debugging phenomenon has been incorporated in the proposed study. A revised model ranking method has been developed to improve the accuracy of model ranking, which is mainly extension of existing normalized criteria distance method. Change point analysis has been done with the effect of different environmental factors on the models' parameters. Numerical examples are given to demonstrate the effectiveness of the proposed model.

Software reliability growth models have been proposed to assess and predict the reliability growth of software, remaining number of faults, and failure rate. In previous studies, software faults have been mainly categorized into two categories based on its severity in removal process: simple faults and hard faults. In reality, fault detectability is one of the crucial factors which can influence the reliability growth of software. The detectability of a software fault depends on how frequently the instructions containing faults are executed. However, fault removability of a software fault depends on fault removal efficiency of debugging team. The main motive of this article is to incorporate the fault detectability in software reliability assessment. Fault exposure ratio is an essential factor for software reliability modeling that controls the per-fault hazard rate. It is strongly dependent on fault detectability. In this article, the effect of fault detectability, fault removability, fault exposure ratio, and fault removal efficiency has been considered simultaneously in software reliability growth modeling. Moreover, a logistic fault exposure ratio has been introduced. The effect of change point is incorporated in the proposed software reliability growth model. Two illustrative examples with software testing data have been presented.

No abstract

No abstract

Web browsers are primary targets of attacks because of their extensive uses and the fact that they interact with sensitive data. Vulnerabilities present in a web browser can pose serious risk to millions of users. Thus, it is pertinent to address these vulnerabilities to provide adequate protection for personally identifiable information. Research done in the past has showed that few vulnerability discovery models (VDMs) highlight the characterization of vulnerability discovery process. In these models, severity which is one of the most crucial properties has not been considered. Vulnerabilities can be categorized into different levels based on their severity. The discovery process of each kind of vulnerabilities is different from the other. Hence, it is essential to incorporate the severity of the vulnerabilities during the modelling of the vulnerability discovery process. This paper proposes a model to assess the vulnerabilities present in the software quantitatively with consideration for the severity of the vulnerabilities. It is possible to apply the proposed model to approximate the number of vulnerabilities along with vulnerability discovery rate, future occurrence of vulnerabilities, risk analysis, etc. Vulnerability data obtained from one of the major web browsers (Google Chrome) is deployed to examine goodness-of-fit and predictive capability of the proposed model. Experimental results justify the fact that the model proposed herein can estimate the required information better than the existing VDMs.