Qualitative and Quantitative Reliability Assessment

During the development of a software system, the supplier must efficiently monitor the development activities; comply with the delivery schedule; predict when a specified level of reliability will be reached, or at least check how well the software will satisfy the customer's requirements; and reduce maintenance efforts. On the other hand, the customer needs a reliable product, delivered on time and at the lowest price. Our method helps reach these goals. It is based on the analysis and evaluation of software reliability by processing failure data collected on a software product during its development and operation. Traditionally, system reliability efforts have not focused on software reliability. We believe that failure prediction can be improved if software reliability modeling is integrated into an overall approach. The method we propose is based on the combined use of descriptive analyses, trend analyses, and reliability models to control testing activities, evaluate software reliability, and plan maintenance.

[1]  Edward N. Adams,et al.  Optimizing Preventive Service of Software Products , 1984, IBM J. Res. Dev..

[2]  K Okumoto,et al.  TIME-DEPENDENT ERROR-DETECTION RATE MODEL FOR SOFTWARE AND OTHER PERFORMANCE MEASURES , 1979 .

[3]  Amrit L. Goel,et al.  Time-Dependent Error-Detection Rate Model for Software Reliability and Other Performance Measures , 1979, IEEE Transactions on Reliability.

[4]  Ytzhak H. Levendel Reliability Analysis of Large Software Systems: Defect Data Modeling , 1990, IEEE Trans. Software Eng..

[5]  Jean-Claude Laprie,et al.  Experience in software reliability: From data collection to quantitative evaluation , 1993, Proceedings of 1993 IEEE International Symposium on Software Reliability Engineering.

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

[7]  Karama Kanoun,et al.  Software dependability of a telephone switching system. , 1987 .

[8]  Sylvain Metge,et al.  SoRel: A tool for reliability growth analysis and prediction from statistical failure data , 1993, FTCS-23 The Twenty-Third International Symposium on Fault-Tolerant Computing.

[9]  Robert B. Grady,et al.  Software Metrics: Establishing a Company-Wide Program , 1987 .

[10]  Ram Chillarege,et al.  Identifying risk using ODC based growth models , 1994, Proceedings of 1994 IEEE International Symposium on Software Reliability Engineering.

[11]  Shigeru Yamada,et al.  Software quality/reliability measurement and assessment: software reliability growth models and data analysis , 1991 .

[12]  Karama Kanoun,et al.  Analyse des défaillances et suivi de la validation du logiciel d’un équipement de télécommunication* , 1990 .

[13]  Jean-Claude Laprie,et al.  The KAT (Knowledge-Action-Transformation) Approach to the Modeling and Evaluation of Reliability and Availability Growth , 1991, IEEE Trans. Software Eng..

[14]  Victor R. Basili,et al.  A Methodology for Collecting Valid Software Engineering Data , 1984, IEEE Transactions on Software Engineering.

[15]  Jean-Claude Laprie,et al.  Trend Analysis , 1996, The SAGE Encyclopedia of Research Design.

[16]  Olivier Gaudoin,et al.  Optimal properties of the Laplace trend test for soft-reliability models , 1992 .

[17]  Sylvain Metge,et al.  Failure analysis and validation monitoring of a telecommunication equipment software system , 1990 .