Software Release Time Management: How to Use Reliability Growth Models to Make Better Decisions

In late years, due to the significance of software application, professional testing of software becomes an increasingly important task. Once all detected faults are removed, project managers can begin to determine when to stop testing. Software reliability has important relations with many aspects of software, including the structure, the operational environment, and the amount of testing. Actually, software reliability analysis is a key factor of software quality and can be used for planning and controlling the testing resources during development. Over the past three decades, many software reliability growth models (SRGMs) have been proposed. For most traditional SRGMs, one common assumption is that the fault detection rate is a constant over time. However, the fault detection process in the operational phase is different from that in the testing phase. Thus, in this paper, we use the testing compression factor (TCF) to reflect the fact and describe the possible phenomenon. In addition, sometimes the one-to-one mapping relationship between failures and faults may not be realistic. Therefore, we also incorporate the concept of quantified ratio, not equal to 1, of faults to failures into software reliability growth modeling. We estimate the parameters of the proposed model based on real software failure data set and give a fair comparison with other SRGMs. Finally, we show how to use the proposed model to conduct software release time management

[1]  Michael R. Lyu,et al.  Optimal release time for software systems considering cost, testing-effort, and test efficiency , 2005, IEEE Transactions on Reliability.

[2]  Jean-Claude Laprie,et al.  Software Reliability Trend Analyses from Theoretical to Practical Considerations , 1994, IEEE Trans. Software Eng..

[3]  Hoan Sung Jung,et al.  Prediction of Safety Critical Software Operational Reliability from Test Reliability Using Testing Environment Factors , 1999 .

[4]  Mayuram S. Krishnan Software release management: a business perspective , 1994, CASCON.

[5]  Hoang Pham Software Reliability , 1999 .

[6]  Ming Zhao Change-point problems in software and hardware reliability , 1993 .

[7]  P. K. Kapur,et al.  An exponential SRGM with a bound on the number of failures , 1993 .

[8]  Pradip K. Srimani,et al.  An Examination of Fault Exposure Ratio , 1993, IEEE Trans. Software Eng..

[9]  Michael R. Lyu,et al.  Software reliability engineering study of a large-scale telecommunications software system , 1995, Proceedings of Sixth International Symposium on Software Reliability Engineering. ISSRE'95.

[10]  Mitsuru Ohba,et al.  Does imperfect debugging affect software reliability growth? , 1989, ICSE '89.

[11]  Michael R. Lyu,et al.  Applying reliability models more effectively (software) , 1992, IEEE Software.

[12]  Michael R. Lyu,et al.  A Unified Scheme of Some Nonhomogenous Poisson Process Models for Software Reliability Estimation , 2003, IEEE Trans. Software Eng..

[13]  M. Xie,et al.  Software Reliability Models - Past, Present and Future , 2000 .

[14]  Yashwant K. Malaiya,et al.  On input profile selection for software testing , 1994, Proceedings of 1994 IEEE International Symposium on Software Reliability Engineering.

[15]  Roger S. Pressman,et al.  Software Engineering: A Practitioner's Approach , 1982 .

[16]  Simon P. Wilson,et al.  Software Reliability Modeling , 1994 .