Formal methods for the validation of fault tolerance in autonomous spacecraft

Analysis of the effects of real and injected software faults: Linux as a case study

“…Fault injection has long been recognized as a pragmatic means to assess the dependability of computer systems [1], in some cases in complement with other more formal approaches (e.g., see [2][3][4]). Numerous techniques and tools were proposed [5,6] that have been widely applied both in research projects and industry.…”

An investigation on mutation strategies for fault injection into RDD-100 models

“…This is why we have tried to attack this issue from a different perspective, i.e., to study instead how several existing design tools can be enhanced to support such an early dependability validation analysis. In contrast to the work reported in [1], that dealt with formal techniques (in particular, SDL), we focus here on a more pragmatic approach aimed at elaborating on the modeling and simulation capabilities of system engineering tools used in the industrial world by system designers. Statemate [7] and RDD-100 are among the various commercial tools that are currently used in industry.…”

“…However, besides evaluations based on probabilistic modeling or FMECA (Failure Modes Effects and Criticality Analysis), the consideration in the early phases of the development process of dependability issues encompassing detailed behavioral analysis is still hardly supported in practice in industry, with few exceptions such as [1,10]. Accordingly, we have developed a method to assist fault-tolerant systems designers by incorporating the explicit analysis of the faulty behavior of such systems, in the early phases of the development process.…”

A formal software verification concept based on automated theorem proving and reverse engineering

“…In our paper we use logic-based wffs. An example of SDL usage is given in [21]. In that paper Ayache et al present formal methods for the validation of fault tolerance in autonomous spacecraft.…”

“…We use SDL, too, but as the standardized specification language only. In contrast to [21], we do formal verification using the specification extracted from the software.…”