Software reliability measures applied to system engineering

Boehm, Brown, and Lipow 1 have characterized the multidimensional nature of software quality in terms of a hierarchy of attributes. One of the high-level attributes is reliability, which they define qualitatively as the satisfactory performance of intended functions. This definition may be refined to the quantitative statement "probability of failure- free operation in a specified environment for a specified time." A "failure" is an unacceptable departure of program operation from program requirements, where, as in the case of hardware, "unacceptable" must ultimately be defined by the user. The term "fault" will be used to indicate the program defect that causes the failure.

[1]  Fumio Akiyama,et al.  An Example of Software System Debugging , 1971, IFIP Congress.

[2]  John D. Musa,et al.  Measuring reliability of computation center software , 1978, ICSE '78.

[3]  Barry W. Boehm,et al.  Quantitative evaluation of software quality , 1976, ICSE '76.

[4]  J. D. Musa The use of software reliability measures in project management , 1978, COMPSAC.

[5]  Albert Endres,et al.  An analysis of errors and their causes in system programs , 1975, IEEE Transactions on Software Engineering.

[6]  John D. Musa,et al.  Software reliability measurement , 1984, J. Syst. Softw..

[7]  John D. Musa,et al.  A theory of software reliability and its application , 1975, IEEE Transactions on Software Engineering.