Dynamically detecting faults via integrity constraints

Hayes, Ian J. (2009). Dynamically detecting faults via integrity constraints. In Michael Butler, Cliff Jones, Alexander Romanovsky and Elena Troubitsyna (Ed.), Methods, Models, and Tools for Fault Tolerance (pp. 85-103) Berlin, Germany: Springer Verlag. doi:10.1007/978-3-642-00867-2_5

Attached Files (Some files may be inaccessible until you login with your UQ eSpace credentials)
Name Description MIMEType Size Downloads

Author Hayes, Ian J.
Title of chapter Dynamically detecting faults via integrity constraints
Title of book Methods, Models, and Tools for Fault Tolerance
Place of Publication Berlin, Germany
Publisher Springer Verlag
Publication Year 2009
Sub-type Research book chapter (original research)
DOI 10.1007/978-3-642-00867-2_5
Open Access Status
Year available 2009
Series Lecture Notes in Computer Science
ISBN 978-3-642-00866-5
ISSN 0302-9743
Editor Michael Butler
Cliff Jones
Alexander Romanovsky
Elena Troubitsyna
Volume number 5454 LNCS
Chapter number 5
Start page 85
End page 103
Total pages 19
Total chapters 15
Collection year 2010
Language eng
Subjects 890299 Computer Software and Services not elsewhere classified
080309 Software Engineering
Abstract/Summary Control programs for safety-critical systems are required to tolerate faults in the devices they control. In this paper we examine a systematic approach to devising code to detect faulty devices at runtime. The approach is centred around the use of integrity constraints, which are invariants on the state of a system's variables, including its inputs and outputs. Under normal operation integrity constraints should always hold, but they are designed to fail to hold if there is a fault. By adding variables to capture the previous state of variables or the time of significant events, additional integrity constraints can be devised to check for faults in state transitions or faults with the rate of progress of the system. We discuss techniques for devising integrity constraints as well as efficiently evaluating the constraints. When an error is detected via the failure of an integrity constraint, the integrity constraint(s) that failed can help diagnose the likely fault. We illustrate the approach using controller software written in the action system style, but it is equally applicable to other state machine approaches such as Event-B and TLA.
Keyword Fault tolerance
Q-Index Code B1
Q-Index Status Confirmed Code

Version Filter Type
Citation counts: Scopus Citation Count Cited 2 times in Scopus Article | Citations
Google Scholar Search Google Scholar
Created: Mon, 29 Mar 2010, 15:38:23 EST by Ian Hayes on behalf of School of Information Technol and Elec Engineering