Abstract

The process of software development is usually described in terms of a progression from user requirements to the final code, passing through intermediate stages such as specification, design, and validation. Of course, progress through these stages is rarely unidirectional, and “final code” must be considered to be a misnomer given the demand for subsequent software maintenance. An engineering approach to software development should enable software to be produced on time, within budget, and in accordance with user requirements. One important aspect of these requirements concerns the reliability of the software. Software reliability requirements can be expressed in a number of ways, of which the simplest, perhaps, is to impose an upper limit on the measured rate of failure over a specified interval.

Keywords

Acceptance Test Software Reliability Control Software Mean Time Between Failure State Restoration

These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.

Preview

References

[Anderson 1985]

T. Anderson and P. A. Barrett, “Fault Tolerance Project Report: Results and Conclusions from the Second and Third Experimental Programmes”, University of Newcastle upon Tyne, Proj. Rep. 4844/DD.17/3,1985.Google Scholar