Dependable Computing and Fault Tolerance : Concepts and Terminology

Laprie, Jean-Claude

doi:10.1109/ftcsh.1995.532603

Cited by 324 publications

(180 citation statements)

References 11 publications

Supporting

Mentioning

165

Contrasting

Unclassified

Order By: Relevance

“…The origin of this effort dates back to 1980, when a joint committee on "Fundamental Concepts and [FTCS 1982], and a synthesis was presented at FTCS-15 in 1985 [Laprie 1985] which is a direct predecessor of this paper, but provides a much less detailed classification, in particular of dependability threats and attributes. [Laprie 1992], which contained a 34-page English text with an eight-page glossary and its translations into French, German, Italian, and Japanese.…”

Section: Preceding Work and Goals For The Futurementioning

confidence: 99%

Basic concepts and taxonomy of dependable and secure computing

Avižienis

Laprie

Randell

et al. 2004

IEEE Trans.Dependable and Secure Comput.

4,110

2,435

View full text Add to dashboard Cite

show abstract

Section: Preceding Work and Goals For The Futurementioning

confidence: 99%

Basic concepts and taxonomy of dependable and secure computing

Avižienis

Laprie

Randell

et al. 2004

IEEE Trans.Dependable and Secure Comput.

4,110

2,435

View full text Add to dashboard Cite

show abstract

“…Carter's "... trustworthiness and continuity of computer system service such that reliance can justifiably be placed on this service" [21] has two positive aspects: It takes the time element into account explicitly (continuity) and stresses the need tbr dependability validation (justifiably). Laprie's version of this definition [53] can be considered a step backwards in that it substitutes quality for trustworthiness and continuity. The use of quality and quality assurance, as in other engineering disciplines, is a welcome trend [16,30].…”

Section: Defining Dependabilitymentioning

confidence: 99%

A multi-level view of dependable computing

Parhami

1994

Computers & Electrical Engineering

View full text Add to dashboard Cite

Abstract--This paper serves a dual purpose. It presents a unified framework and terminology for the study of computer system dependability. It also surveys the field of dependable computing in light of the proposed framework. Specifically, impairments to dependability are viewed from six levels, each being more abstract than the previous one. It is argued that all of these levels are useful, in the sense that proven dependability assurance techniques can be applied at each level, and that it is beneficial to have distinct, precisely defined terminology for describing impairments to, and procurement strategies for, computer system dependability at these levels. The six levels are: Briefly, a hardware or software component may be defective (hardware may also become defective due to wear and aging). Certain system states will expose the defect, resulting in the development of faults defined as incorrect signal values or decisions within the system. If a fault is actually exercised, it may contaminate the data flowing within the system, causing errors. Erroneous information or states may or may not cause the affected subsystem to malfunction, depending on the subsystem's design and error tolerance. A subsystem malfunction does not necessarily have a catastrophic, unsafe, or even perceivable service-level effect. Finally, degradation of service could eventually lead to system failure. At each of these six levels, the complementary approaches of prevention (avoidance or removal) and tolerance are discussed in relation to inter-level transitions.

show abstract

“…Before proceeding with a discussion of fault tolerance, it is important to understand the precise definitions of the terms fault, error, and failure [46]: • A failure refers to an occurrence of the delivered service deviating from the specified or expected service.…”

Section: Solution Frameworkmentioning

confidence: 99%

“…It is important to note that there are often many mechanisms available for accomplishing the same goal. From the literature on dependability (survivability being one of the dimensions of dependability), there are four means for providing dependable computing systems: fault avoidance, fault tolerance, error removal, and error forecasting [14], [46]: • Fault avoidance prevents the occurrence of faults by construction.…”

Section: Solution Frameworkmentioning

confidence: 99%

See 1 more Smart Citation

Fault Tolerance in Critical Information Systems

Knight¹,

Elder²

View full text Add to dashboard Cite

Public reporting burden for the collection of information is estimated to average 1 hour per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington VA 22202-4302. Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to a penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number. Critical infrastructure applications provide services upon which society depends heavily; such applications require constant, dependable operation in the face of various failures, natural disasters, and other disruptive events that might cause a loss of service. These applications are themselves dependent on distributed information systems for all aspects of their operation, so survivability of these critical information systems is an important issue. Survivability is the ability of a system to continue to provide service, though possibly alternate or degraded, in the face of various types of failure and disruption. A fundamental mechanism by which survivability can be achieved in critical information systems is fault tolerance. Much of the literature on fault-tolerant distributed systems focuses on tolerance of local faults by detecting and masking the effects of those faults. I describe a direction for fault tolerance in the face of non-local faults-faults whose effects have significant non-local impact, sometimes widespread and sometimes catastrophic-where often the effects of these faults cannot be masked using available resources. The goal is to recognize these non-local faults through detection and analysis, then to provide continued service (possibly alternate or degraded) by reconfiguring the system in response to these faults.A specification-based approach to fault tolerance, called RAPTOR, is presented that enables systematic structuring of formal specifications for error detection and recovery, utilizes a translator to synthesize portions of the implementation from the formal specifications, and provides an implementation architecture supporting fault-tolerance activities. The RAPTOR approach consists of three specifications describing the fault-tolerant system, the errors to be detected, and the actions to take to recover from those errors. The RAPTOR System includes a synthesizer, the Fault Tolerance Translator, to generate implementation of code components from the specifications to perform error detection and recovery activities. In addition, a novel implementation architecture incorporates the generated code as part of an infrastructure supporting fault tolerance at both the node and syst...

show abstract

Dependable Computing and Fault Tolerance : Concepts and Terminology

Cited by 324 publications

References 11 publications

Basic concepts and taxonomy of dependable and secure computing

Basic concepts and taxonomy of dependable and secure computing

A multi-level view of dependable computing

Fault Tolerance in Critical Information Systems

Contact Info

Product

Resources

About