Software fault tolerance
This article needs additional citations for verification. (February 2011) (Learn how and when to remove this template message)
- MERGE WITH Fault-tolerant software
The only thing constant is change. This is certainly more true of software systems than almost any phenomenon, not all software change in the same way so software fault tolerance methods are designed to overcome execution errors by modifying variable values to create an acceptable program state. The need to control software fault is one of the most rising challenges facing software industries today. It is obvious that fault tolerance must be a key consideration in the early stage of software development.
There exist different mechanisms for software fault tolerance, among which:
- Recovery blocks
- N-version software
- Self-checking software
- Built-in self-test
- Built-in test equipment
- Immunity-aware programming
- Logic built-in self-test
- N-version programming
- Safety engineering
- Eckhardt, D. E., "Fundamental Differences in the Reliability of N-Modular Redundancy and N-Version Programming", The Journal of Systems and Software, 8, 1988, pp. 313–318.
- Ray Giguette and Johnette Hassell, “Toward A Resourceful Method of Software Fault Tolerance”, ACM Southeast regional conference, April, 1999.