Software Fault Tolerance Methods
by Nataliia Vasylyna | December 9, 2011 12:30 pm
Software fault tolerance methods initiate from fault tolerance designs in traditional hardware systems that require higher levels of dependability, reliability and availability.
In such systems, spare areas and backup units are generally used to keep the systems in operational conditions.
The primary software fault tolerance methods comprise N-version programming, recovery blocks and their variations.
There are some fundamental aspects of software fault tolerance methods:
- N-version programming uses parallel superfluity. In this case N copies, each of a different version of programs performing the identical functionality are running in parallel. The decision algorithm assures that local failures in limited quantity of such parallel versions will not compromise global implementation results.
- Recovery blocks use recurring implementations as the main mechanism for fault tolerance. If dynamic failures in some local parts are identified, a helping of the latest implementation is repeated, in the hope that this repeated implementation will not lead to the identical failure. Consequently, local failures will not spread to global failures.
In the majority of fault tolerance methods faults are not characteristically detected, consequently not removed, but just tolerated dynamically.
This is extremely different to software bugs[1] identifying and removal activities such as inspection and software testing[2].
Learn more from QATestLab
Related Posts:
- software bugs: https://qatestlab.com/services/sample-deliverables/bug-reports-examples/
- software testing: https://qatestlab.com/services/our-qa-services/software-product-testing/
Source URL: https://blog.qatestlab.com/2011/12/09/software-fault-tolerance-methods/