An experimental evaluation of the assumption of independence in multiversion programming
IEEE Transactions on Software Engineering
The consistent comparison problem in N-version software
ACM SIGSOFT Software Engineering Notes
Model checking
Fault Tolerance: Principles and Practice
Fault Tolerance: Principles and Practice
Fault Tolerance Via N-Modular Software Redundancy
FTCS '98 Proceedings of the The Twenty-Eighth Annual International Symposium on Fault-Tolerant Computing
Enhancing System Validation with Behavioural Types
HASE '02 Proceedings of the 7th IEEE International Symposium on High Assurance Systems Engineering
Toward Dependable Safety-Critical Software
WORDS '96 Proceedings of the 2nd Workshop on Object-Oriented Real-Time Dependable Systems (WORDS '96)
Design of reliable software via general combination of N-version programming and acceptance testing
ISSRE '96 Proceedings of the The Seventh International Symposium on Software Reliability Engineering
The N-Version Approach to Fault-Tolerant Software
IEEE Transactions on Software Engineering
| Hi-index | 0.00 |
Explicit fault tolerant programs are characterized by proactive efforts to ensure robustness and ability of fault correction. A fault tolerant application is usually realized conforming to one of a collection of standard techniques. Graph based methods can be used to examine existing applications to derive a control flow abstraction with respect to the fault-tolerance architecture. This abstraction, which we call the fault tolerance behavioural type, can be used as basis of structural analysis of the implemented architecture. This paper outlines the basic ideas and demonstrates their application using CTL (Computation Tree Logic) model checking to verify fault tolerance properties of explicit fault-tolerant programs.