Software engineering of fault tolerant systems / editors, P. Pelliccione ... [et al.].

Includes bibliographical references.

Introduction -- Fault Tolerance Engineering: From Requirements to Code -- Exploiting Reflection to Enable Scalable and Performant Database Replication at the Middleware Level -- Adding FauIt-Tolerance to State Machine-Based Designs -- Replication in Service-Oriented Systems -- Verification and Validation of Fault Tolerant Systems -- Embedded Software Validation Using On-Chip Debugging Mechanisms -- Error Detection in Control Flow of Event-Driven State Based Applications -- Fault-Tolerant Communication for Distributed Embedded Systems -- Languages and Tools for Engineering Fault Tolerant Systems -- A Model Driven Exception Management Framework -- Runtime Failure Detection and Adaptive Repair for Fault-Tolerant Component-Based Applications -- Extending the Applicability of the Neko Framework for the Validation and Verification of Distributed Algorithms -- Table of Contents provided by Ingram. All Rights Reserved --

When architecting dependable systems, fault tolerance is required to improve the overall system robustness. Many studies have been proposed, but the solutions are usually commissioned late during the design and implementation phases of the software life-cycle (e.g., Java and Windows NT exception handling), thus reducing the error recovery effectiveness. Since the system design typically models only normal behaviors of the system while ignoring exceptional ones, the generated system implementation is unable to handle abnormal events. Consequently, the system may fail in unexpected ways due to some faults. Researchers have advocated that fault tolerance management during the entire life-cycle improves the overall system robustness and that different classes of exceptions must be identified for each identified phase of software development, depending on the abstraction level of the software system being modeled. This book builds on this trend and investigates how fault tolerance mechanisms can be used when engineering a software system. New problems will arise, new models are needed at different abstraction levels, methodologies for mode driven engineering of such systems must be defined, new technologies are required, and new validation and verification environments are necessary.

1