Computing Reviews
Today's Issue Hot Topics Search Browse Recommended My Account Log In
Review Help
Search
Detecting Unsafe Error Recovery Schedules
Lutz R., Wong J. IEEE Transactions on Software Engineering18 (8):749-760,1992.Type:Article
Date Reviewed: Feb 1 1994

Interaction between concurrently executing processes gives rise to special considerations that do not apply to sequential processes. Program correctness needs to be considered with respect to safety properties and liveness properties. This paper considers these issues in the context of autonomous error-recovery strategies on the Galileo spacecraft.

Safety properties arise from timing constraints (which prevent a given command being issued within t seconds of some other command); precedence constraints (which ensure that a given command occurs only after some other command has been issued); and data consistency constraints (which restrict simultaneous access to data by concurrent processes). Data consistency may be ensured by constraining the sequencing of the relevant access operations, so data consistency constraints are modeled as precedence constraints. Since precedence constraints guarantee, on the issuing of a given command, that some other command has been issued, they determine the liveness property of the precedent command.

The paper presents a tool for detecting violations of a set of constraints, expressed as a constraint graph. The commands are nodes of the graph, and constraints (relating two commands) are represented by edges. Interacting processes may, in general, yield event interleavings of arbitrary complexity, but, the authors claim, the control structure of spacecraft processes is sufficiently simple that it lends itself to analysis by the constraints checker. The algorithm for the constraints checker is described, and an example (with 40 constraint edges) is presented.

This work is a useful contribution to the verification of concurrent systems. The existence of this tool should enable improved analyses of concurrent systems, especially if it can be generalized to handle a greater variety of constraints.

Reviewer:  P. Mett Review #: CR117058
Bookmark and Share
 
Error Handling And Recovery (D.2.5 ... )
 
 
Real-Time Systems And Embedded Systems (D.4.7 ... )
 
 
Scheduling (D.4.1 ... )
 
 
Organization And Design (D.4.7 )
 
 
Process Management (D.4.1 )
 
 
Software/ Program Verification (D.2.4 )
 
Would you recommend this review?
yes
no
Other reviews under "Error Handling And Recovery": Date
(N,K) concept fault tolerance
Krol T. IEEE Transactions on Computers 35(4): 339-350, 1986. Type: Article
Nov 1 1987
Error recovery in asynchronous systems
Campbell R., Randell B. IEEE Transactions on Software Engineering SE-12(9): 811-826, 1986. Type: Article
Jul 1 1987
Static analysis to support the evolution of exception structure in object-oriented systems
Robillard M., Murphy G. ACM Transactions on Software Engineering and Methodology 12(2): 191-221, 2003. Type: Article
Nov 25 2003
more...

E-Mail This Printer-Friendly
Send Your Comments
Contact Us
Reproduction in whole or in part without permission is prohibited.   Copyright 1999-2024 ThinkLoud®
Terms of Use
| Privacy Policy