Abstract
A fault-tolerant program is one that can continue service after faults have adversely affected the state of the program. The process by which a program can tolerate faults is divided into four phases: error detection, when the fault is first detected; damage assessment, when the damage caused by the fault is assessed; fault removal, when the fault is diagnosed, then removed; finally, error recovery, when the impact of the fault on the state of the program is corrected. In this article, we are interested in the first two phases. We discuss means to carry these phases out, using executable assertions. Appropriate executable assertions are derived by solving algebraic equations in the Tarski calculus of relations.
| Original language | English (US) |
|---|---|
| Pages (from-to) | 15-37 |
| Number of pages | 23 |
| Journal | The Journal of Systems and Software |
| Volume | 12 |
| Issue number | 1 |
| DOIs | |
| State | Published - Apr 1990 |
| Externally published | Yes |
All Science Journal Classification (ASJC) codes
- Software
- Information Systems
- Hardware and Architecture
Fingerprint
Dive into the research topics of 'The use of executable assertions for error detection and damage assessment'. Together they form a unique fingerprint.Cite this
- APA
- Author
- BIBTEX
- Harvard
- Standard
- RIS
- Vancouver