Communicating sequential processes
Communicating sequential processes
Error recovery in asynchronous systems
IEEE Transactions on Software Engineering
ACM Transactions on Programming Languages and Systems (TOPLAS)
The B-book: assigning programs to meanings
The B-book: assigning programs to meanings
Alloy: a lightweight object modelling notation
ACM Transactions on Software Engineering and Methodology (TOSEM)
ACM SIGOPS Operating Systems Review
Rigorous Development of an Embedded Fault-Tolerant System Based on Coordinated Atomic Actions
IEEE Transactions on Computers - Special issue on fault-tolerant embedded systems
The Theory and Practice of Concurrency
The Theory and Practice of Concurrency
Fault Tolerance: Principles and Practice
Fault Tolerance: Principles and Practice
Action-oriented exception handling in cooperative and competitive concurrent object-oriented systems
Advances in exception handling techniques
Exception Handling in Component-Based System Development
COMPSAC '01 Proceedings of the 25th International Computer Software and Applications Conference on Invigorating Software Development
System structure for software fault tolerance
Proceedings of the international conference on Reliable software
Architecture-based Exception Handling
HICSS '01 Proceedings of the 34th Annual Hawaii International Conference on System Sciences ( HICSS-34)-Volume 9 - Volume 9
Fault Tolerance in Concurrent Object-Oriented Software through Coordinated Error Recovery
FTCS '95 Proceedings of the Twenty-Fifth International Symposium on Fault-Tolerant Computing
Reo: a channel-based coordination model for component composition
Mathematical Structures in Computer Science
Verification of coordinated exception handling
Proceedings of the 2006 ACM symposium on Applied computing
Hi-index | 0.00 |
Architectures based on Coordinated Atomic action (CA action) concepts have been used to build concurrent fault-tolerant systems. This conceptual model combines concurrent exception handling with action nesting to provide a general mechanism for both enclosing interactions among system components and coordinating forward error recovery measures. This article presents an architectural model to guide the formal specification of concurrent fault-tolerant systems. This architecture provides built-inCommunicating Sequential Processes (CSPs) and predefined channels to coordinate exception handling of the user-defined components. Hence some safety properties concerning action scoping and concurrent exception handling can be proved by using the FDR (Failure Divergence Refinement) verification tool. As a result, a formal and general architecture supporting software fault tolerance is ready to be used and proved as users define components with normal and exceptional behaviors.