J.C. Laprie. Dependability: Basic Concepts and Terminology. Springer Verlag, Vienna, Austria, 1992.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....safety may still be distinguished: a recognition light on the underbelly is a safety critical item; a reading lamp in passenger class is not. The reliability of the latter is not a safety issue. 3.9. 2 Avoidance Of The Problematic Notions The IFIP WG 10.4 De nitions The series of de nitions in [Lap92] concerned with dependability, which is taken by members of the IFIP WG 10.4 to include safety, does not include the concepts of hazard and risk at all. 3.9.3 Classifying Risk Through Statistics An obvious way to avoid the problem is to have had the misfortune to have had suciently many ....

J.-C. Laprie, editor. Dependability: Basic Concepts and Terminology, in English, French, German, Italian and Japanese, volume 5 of Dependable Computing and Fault Tolerance. Springer-Verlag, Wien, New York, 1992. Prepared by IFIP Working Group 10.4 on Dependable Computing and Fault Tolerance.

....system that could rate systems in each of the dimensions that affect dependability. 2. Dimensions of Dependability Unlike performance benchmarks, which need to compare only the rate at which specific, pre defined work gets done, dependability comparisons must consider many different aspects [12]. Is the system accessible when needed Are the results correct Is the data protected from physical hazards and unauthorized access To simplify the creation of comparison classes, it is useful to separate the various threats to dependability and treat them as different dimensions of the problem ....

J.-C. Laprie, Ed., "Dependability: Basic Concepts and Terminology", (Dependable Computing and Fault Tolerance, vol. 5, A. Avizienis, H. Kopetz and J.-C. Laprie, Eds.), Vienna: SpringerVerlag, 1992.

....and in doing so, obfuscate or eliminate evidence relating to malicious activity. To begin the process of learning from experience, and for users, operators, owners, and law enforcement to recover from a violation of law or policy, experts must demystify these faults, errors and failures [12]. Formalizing this process for consistent repeatability purposes and automating it for practical ones is critical. While work has been done to frame the problem of digital forensics, most of the advances have been at the evidence collection and preservation stages of an investigation. Yet it makes ....

....interacting or interfering, or likely to interact or interfere with other entities. a component is another system, etc. The recursion stops when a system is considered being atomic: any further internal structure cannot be discerned, or is not of interest and can be ignored. Laprie [12] Independent components that have redundant data could be considered to be in separate administrative domains at that level of abstraction in the system. In the HACQIT [32] architecture for example, redundant hosts are independent. This independence aids the detection of semantic incongruities ....

[Article contains additional citation context not shown here]

Jean-Claude Laprie editor. Dependability: Basic Concepts and terminology. IFIP WG 10.4, August 1994 draft.

....concepts of the AIRBUS flight control system [7] In 1992 the first paper on SAFEbus [8] the architecture that was later deployed in the Boeing 777 aircraft for flight control, became available. In excellent publications by Lala [9] Avizienis [10] and the books by Rechtin [11] and Laprie [12], the fundamental concepts and architectural principles for the design of dependable systems are clarified at about that time. For example, Lala states that field experience with approximate voting was not at all satisfying. At about the same time a heated debate started concerning the ....

J. C. Laprie. Dependability: Basic Concepts and Terminology. Springer Verlag, 1992.

....of the system should allow fault tolerant mechanisms to operate in an orchestrated way with the system functions, without unnecessarily increasing the complexity of the system [17] 2.1. Fault Tolerance The basic strategy to achieve fault tolerance in a system can be divided into two steps [13]. The first step, called error processing, is concerned with the system internal state, aiming to: detect errors that are caused by activation of faults, the diagnosis of the erroneous states, and recovery to error free states. The second step, called fault treatment, is concerned with the sources ....

J. C. Laprie. Dependability: Basic concepts and terminology. In Special Issue of the Twenty-Fifth International Symposium on Fault-Tolerant Computing (FTCS- 25). IEEE Computer Society Press, 1995.

....overwhelming and, therefore, insufficiently understood software and hardware are often used. However implemented, we require that safety critical systems are dependable. There are many terms associated with dependability, and considerable international effort has been expended to standardize these [83]. The accepted definition of the overall concept is [82] Dependability is that property of a computing system which allows reliance to be justifiably placed on the service it delivers. The life of a system is perceived by its users as an alternation between proper and improper service. Delivery ....

LAPRIE, J.C. (Ed.): `Dependability: basic concepts and terminology' (Springer-Verlag, 1991)

....the methods and the tools that support it. Section 5 describes the B development process and the internal veri cation that is ensured by the method: it is shown that additional veri cations are still required at the various steps of the The terminology adopted in this paper is consistent with [17]. In particular, the word veri cation refers to the process of checking whether the system adheres to properties termed the veri cation conditions. Both static (e.g. inspections, proofs) and dynamic (e.g. testing) techniques are included in this de nition. development process, whether ....

....is the possibility of establishing properties on them. Hence, it can be veri ed that a speci cation ful ls some safety requirements, or that a design is correct with respect to its speci cation (if both are expressed formally) Then the problem is that of the validation of the validation [17], or how to reach con dence in the methods and tools used in building con dence in the system. The formal system underlying the method may be wrong . It is well known that proofs may be faulty: the use of computerized tools signi cantly alleviates the problem, but there is still the issue of ....

J-C. Laprie. Dependability: basic concepts and terminology. Springer Verlag, Vienna, 1992.

....overwhelming and, therefore, insufficiently understood software and hardware are often used. However implemented, we require that safety critical systems are dependable. There are many terms associated with dependability, and considerable international effort has been expended to standardize these [75]. The accepted definition of the overall concept is [74] Dependability is that property of a computing system which allows reliance to be justifiably placed on the service it delivers. The life of a system is perceived by its users as an alternation between proper and improper service. Delivery ....

LAPRIE, J.C. (Ed.): `Dependability: basic concepts and terminology' (Springer-Verlag, 1991)

....that the system s correct operation will be threatened by a single component failure also increases. This fact has made it necessary to build dependable distributed systems. A system s dependability is de ned as the degree to which reliance can justi ably be placed on the service it delivers [1]. Fault tolerance is an important aspect of dependability. It is the ability for a system to provide its speci ed service in spite of component failure [1] Fault tolerance is needed in many di erent dependable distributed applications. These applications include large critical systems (such ....

....systems. A system s dependability is de ned as the degree to which reliance can justi ably be placed on the service it delivers [1] Fault tolerance is an important aspect of dependability. It is the ability for a system to provide its speci ed service in spite of component failure [1]. Fault tolerance is needed in many di erent dependable distributed applications. These applications include large critical systems (such as air trac control systems) smaller critical systems (such as medical systems) communication systems (such as telephony systems) and enterprise ....

[Article contains additional citation context not shown here]

J.-C. Laprie, ed., Dependability: Basic Concepts and Terminology. Vienna: SpringerVerlag, 1992.

....this situation are C 12 for proc1 and C 21 for proc2. 19 2.2 FAULT ENVIRONMENT DESCRIPTION Faults in a computer system can be permanent, intermittent or transient. A permanent (hard) fault is a fault whose presence is not related to pointwise conditions of the system, either internal or external [31]. It is continuous and stable. An intermittent fault is a fault that is only occasionally present due to an unstable hardware condition. A transient (soft) fault is a fault resulting from a temporary environment (external) condition. Some examples of outside disturbances that might produce a ....

J.C. Laprie, "Dependability: Basic Concepts and Terminology", WG 10.4 - Dependability Computing and Fault Tolerance, August 1994.

No context found.

Laprie, J.-C. Ed. 1992. Dependability: Basic concepts and Terminology, Volume 5 of Dependable Computing and Fault-Tolerant Systems.

No context found.

J.-C. Laprie, editor, Dependability: Basic Concepts and Terminology, Springer-Verlag, 1992.

No context found.

J.C. Laprie. Dependability: Basic Concepts and Terminology. Springer Verlag, Vienna, Austria, 1992.

No context found.

J. C. Laprie. Dependability: Basic concepts and terminology. In Dependable Computing and Fault Tolerant Systems, volume 5, pages 257--282. Springer Verlag, Vienna, 1992.

No context found.

Laprie, J.-C. Ed. 1992. Dependability: Basic concepts and Terminology, Volume 5 of Dependable Computing and Fault-Tolerant Systems.

No context found.

Laprie, J.-C. Ed. 1992. Dependability: Basic concepts and Terminology, Volume 5 of Dependable Computing and Fault-Tolerant Systems.

No context found.

Laprie, J.-C. (1992). Dependability: Basic Concepts and Terminology. Springer-Verlag Wien, New York.

No context found.

J.C. Laprie (Ed.), Dependability: Basic Concepts and Terminology, Springer Verlag, Wien, 1992.

No context found.

Laprie J.-C. (ed.), "Dependability: Basic Concepts and Terminology", Dependable Computing and Fault-Tolerant Systems series, Vol. 5, Springer-Verlag, 1992

No context found.

J.C.Laprie. Dependability: Basic Concepts and Terminology. SpringerVerlag, 1992.

No context found.

J.C.Laprie. Dependability: Basic Concepts and Terminology. Springer-Verlag, 1992.

No context found.

J.C. Laprie: Editor, "Dependability: Basic Concepts and Terminology," Springer-Verlag, Berlin, 1992.

No context found.

J.C. Laprie (Ed). "Dependability: Basic Concepts and Terminology. " Volume 5 of Dependable Computing and FaultTolerant Systems, chapter 5.2, Fault-Tolerance. Springer Verlag. Wien, New York. 1992, pages 23--28.

No context found.

J.C. Laprie, editor. Dependability: Basic Concepts and Terminology. Springer-Verlag, 1992.

No context found.

J.C. Laprie, editor. Dependability: Basic Concepts and Terminology. Springer-Verlag, 1992.

First 50 documents  Next 50

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC