Abstract
Software design techniques for tolerating both hardware and software faults have been developed over the past few decades. Paradoxically, it is essential that fault-tolerant software is designed with the highest possible rigour to prevent faults in itself. Such rigour is provided by formal methods and aided by model checking. We illustrate an approach to fault-tolerant software design based on communicating sequential processes through a running example.
Original language | English |
---|---|
Pages (from-to) | 197-209 |
Number of pages | 13 |
Journal | Microprocessors and Microsystems |
Volume | 29 |
Issue number | 5 |
DOIs | |
Publication status | Published - 1 Jun 2005 |
Bibliographical note
We would like to thank Iain Bate and the anonymous reviewers for their comments and suggestions. The first author would like to thank the staff and research students of the Formal Methods Group at Royal Holloway for their interesting and helpful discussion during his visit there when completing this work. The visit is supported by a study leave from Lingnan University, Hong Kong.Keywords
- Fault tolerance
- Formal verification
- Model checking
- Software design