Search

Advancements in science and technology have led to the widespread use of computer systems in various applications, emphasizing the importance of software reliability. Software failures can have severe consequences, making thorough testing crucial. Software reliability growth models (SRGMs) play a significant role in enhancing reliability by predicting improvement over time. This article introduces a comprehensive approach to software reliability that incorporates a dynamic fault detection rate, along with fault removal efficiency. The fault detection rate measures the rate at which faults are identified during testing, reflecting the effectiveness of the testing process. By incorporating this dynamic component, the model provides a more accurate estimation of software reliability and enables adaptive testing strategies and resource allocation. Achieving a high fault detection rate is desirable, but organizations must consider the cost implications and strike a balance between reliability and time-to-market constraints. This article extends the analysis to calculate the optimal release time and optimal warranty period that minimize development costs, subject to the desired reliability. By considering these factors, development teams can make informed decisions regarding the timing of software release and the duration of the warranty period, optimizing both reliability and cost. [ABSTRACT FROM AUTHOR]

In our fast-paced modern world, software systems have become indispensable in both personal and professional spheres. With increasing reliance on software products, the demand for reliable and high-quality software has intensified, placing significant pressure on developers to stay competitive. Software reliability growth models (SRGMs) play a vital role in assessing the dependability of software systems during their development. These models mathematically analyze the relationship between detected faults, testing time, and failures, enabling the prediction of software failures. This paper introduces an approach to software reliability evaluation, considering the dynamic nature of fault removal efficiency (FRE) during development. Additionally, the model accounts for the change rate of residual errors, considering both error introduction and correction processes. Moreover, the adoption of S-shaped curves captures the learning process of software developers, enhancing the model's accuracy. This approach guides software developers to make informed decisions, leading to improved software reliability and performance, meeting escalating demands. [ABSTRACT FROM AUTHOR]

Software reliability is a critical aspect of ensuring the quality and dependability of software systems. However, existing software reliability models often make assumptions that do not align with real-world scenarios, such as perfect fault removal and independent faults. In this paper, we address this gap by developing a software reliability model that considers fault-dependent detection, imperfect fault removal, and the maximum number of faults that may present in the system. By accounting for these factors, our proposed model aims to provide a more accurate representation of software reliability. We evaluate the effectiveness of our model by comparing it to existing models using three commonly used goodness-of-fit criteria. The results demonstrate the importance of incorporating these considerations in software reliability modeling and highlight the superiority of our approach in capturing the complexities associated with software faults. Additionally, this paper conducts an analysis of optimal release planning, which yields highly encouraging results for software managers and engineers. This analysis adds significant value to the existing literature, further emphasizing the practical relevance of our proposed model. [ABSTRACT FROM AUTHOR]

Software developers' goal is to develop reliable and superior software. Due to the fact that software errors frequently generate large societal or financial losses, software reliability is essential. Software reliability growth models are a widely used technique for software reliability assessment. This study examines various nonhomogeneous Poisson process models with the newly developed software reliability distribution and evaluates the unknown model parameters based on frequentist and Bayesian methods of estimation. Finally, we conduct evaluations on real datasets using a variety of evaluation criteria to compare the results of previous software reliability growth models and show how the proposed model may be applied under both approaches in a practical setting. According to this study, the innovative model's mean square error, R2, Adj−R2$Adj - {R}^2$, bias, predicted relative variation, Theil statistic, and mean error of prediction values show the lowest values under the Bayesian approach for data sets II to IV, and both approaches perform well for data set I. These implementation findings demonstrate the effectiveness of our specific approach based on our examination of failure data. [ABSTRACT FROM AUTHOR]

Goel proposed generalization of the Goel-Okumoto (G-O) software reliability growth model (SRGM), in order to model the failure intensity function, i.e. the rate of occurrence of failures (ROCOF) that initially increases and then decreases (I/D), which occurs in many projects due to the learning phenomenon of the testing team and a few other causes. The ROCOF of the generalized non-homogenous poisson process (NHPP) model can be expressed in the same mathematical form as that of a two-parameter Weibull function. However, this SRGM is susceptible to wide fluctuations in time between failures and sometimes it seems unable to recognize the I/D pattern of ROCOF present in the datasets and hence does not adequately describe such data. The authors therefore propose a shifted Weibull function ROCOF instead for the generalized NHPP model. This modification to the Goel-generalized NHPP model results in an SRGM that seems to perform better consistently, as confirmed by the goodness of fit statistic and predictive validity metrics, when applied to failure datasets of 11 software projects with widely varying characteristics. A case study on software release time determination using the proposed SRGM is also given. [ABSTRACT FROM AUTHOR]