A software up-gradation model with testing effort and two types of imperfect debugging

Abstract

Recent advances in the software world have seen the rise of various Software Reliability Growth Models (SRGMs). These SRGMs take into account various factors and associate them to reliability to come out with a new approach. Some of them consider calendar time as the governing factor while others argued that effort based modeling is more towards reality. In the real industrial scenario, due to the ever growing demands of the customer and stiff contention in the market, developers generally prefer to release the software with multiple versions instead of rolling out all the functionalities at one go. Consequently the customary approach towards software development process as observed in practice is iterative in nature. Moreover, the debugging process is not a perfect event. It has bottlenecks owing to the increasing complexity of software due to up gradations which transcends the limited knowledge of testing team. Thus, it is not a practical approach to go with the assumption of fault removal with certainty after the failure is observed. In a real scenario, it may happen that initially the testing team may not be skilled enough to detect all the faults leading to imperfect debugging, also during debugging it may happen that some faults are added fault causing error generation. Some models successfully capture the influence of imperfect debugging on multiple releases of software. In this present paper, we present a two stage detection/correction based software reliability growth model with testing effort, integrating the concept of two types of imperfect debugging in multiple up gradations of a software. We have taken Exponential and logistic distribution functions for detection and correction process in this paper. The proposed model is successfully tested on a real life software data set.

Modelling reliability growth for multi‐version open source software considering varied testing and debugging factors

“…OSS reliability tools have been compared and reviewed and the characteristics and applications have been summarized 52 . More work in multi‐release modelling of OSS has been put forth by the number of researchers 13‐21,23‐29,34,38,40,42,48 …”

“…52 More work in multi-release modelling of OSS has been put forth by the number of researchers. [13][14][15][16][17][18][19][20][21][23][24][25][26][27][28][29]34,38,40,42,48 Following research gaps have been observed in the literature:…”

Developing a hybrid software reliability growth model

“…In all the above models, it has been assumed that detection of faults leads to immediate correction and as such detection and correction are taken as one step process. Then Singh et al (2014a, b) presented a unified multi-upgraded model for two-stage detection and correction where they have incorporated two types of imperfect debugging only, and Kapur et al (2015) extended it to incorporate testing effort and two types of imperfect debugging. Tickoo et al (2016) developed a two-dimensional multi-release framework considering single change point in each release.…”

Generalized multi‐release modelling of software reliability growth models from the perspective of two types of imperfect debugging and change point

“…Then, in Singh et al, a unified multi‐upgraded model for two‐stage detection and correction is proposed where they have incorporated two types of imperfect debugging. The model has been extended to incorporate testing effort along with imperfect debugging in Kapur et al In previous studies, multi‐release framework/models have been forwarded wherein two stage fault detection and correction processes have been considered. More of latest work in the field of multi‐release have been put forth by researchers in .…”