W.R. Elmendorf, "Fault-tolerant programming", in Proc. 2nd IEEE Int. Symp. on Fault-Tolerant Computing (FTCS-2), Newton, Massachusetts, June 1972, pp. 79-83. Home/Search Document Not in Database Summary Related Articles Check |
This paper is cited in the following contexts:
A Transactional Approach to Redundant Disk Array Implementation - Courtright, II (1997) (5 citations) (Correct)
....[Kuehn69] A voting module is used to compare the responses of the three modules. If a discrepancy is found, the faulty module is assumed to be the minority voter. Similarly, software systems employ N version programming to detect faults associated with software design and construction [Chen78, Elmendorf72] In these systems, the outputs of a number of independently developed program modules (N) are compared for inconsistencies. Again, a voting module is used to detect errors and locate failed modules. An alternative to diagnosing faults by voting is to use a single component and monitor its ....
Elmendorf, W. R. "Fault-tolerant programming." Proceedings of the 2nd International Symposium on Fault-Tolerant Computing (FTCS-2). Los Alamitos, CA: IEEE Computer Society Press, Newton, MA (June 19-21, 1972) 79-83.
Malicious- and Accidental-Fault Tolerance for Internet.. - Powell, (eds.) (Correct)
....may be identical, based on the assumption that hardware components fail independently. However, such an approach is not suitable for the tolerance of design faults. To tolerate design faults, the multiple channels have to provide identical services through separate designs and implementations [Elmendorf 1972, Randell 1975, Avizienis 1978] i.e. through design diversity. Design diversity is intended to tolerate permanent design faults. On the other hand, a backward recovery based error processing usually enables temporary design faults to be tolerated [Gray 1986] An important aspect of ....
W. R. Elmendorf, "Fault-Tolerant Programming", in 2nd IEEE Int. Symp. on Fault Tolerant Computing (FTCS-2), (Newton, MA, USA), pp.79-83, IEEE Computer Society Press, 1972.
Diversity against Accidental and Deliberate Faults - Deswarte, Kanoun, Laprie (1998) (4 citations) (Correct)
....of biometric data) Diverse interfaces can also provide back up facilities to cope with physical faults affecting some parts of the interfaces. 3.3 Application software diversity This is the most common form of diversity. The notion of software diversity has been formulated in the seventies [11, 22, 36]. It has been significantly used in safety critical systems to provide either a fail halt property or service continuity. The fail halt property, with respect to design faults, can be simply achieved by selfchecking modules consisting of two parts: a functional part and a monitor part running an ....
W. R. Elmendorf, "Fault-tolerant Programming", Proc. 2nd IEEE Int Symp. Fault-Tolerant Computing, Newton, Massashusetts, 1972, pp. 79-83.
The Methodology of N-Version Programming - Avizienis (1995) (7 citations) (Correct)
....of the software of modern computers relied on the principle of finding and eliminating software design faults either before or during the operational use of the software. Suggestions on the use of multiple versions of software for fault tolerance began appearing in the early and mid 1970 s [Elm72, Gir73, Kop74, Fis75]. The effort to develop a systematic process (a paradigm) for the building of multipleversion software units that tolerate software faults, and function analogously to majority voted multichannel hardware units, such as TMR, was initiated at UCLA in early 1975 as a part of research in reliable ....
W. R. Elmendorf. Fault-tolerant programming. In Digest of 2nd FTCS, pages 79--83, Newton, MA, June 1972.
MAFTIA - reference Model and Use Cases - Cachin, Camenisch, Dacier.. (2000) (Correct)
....may be identical, based on the assumption that hardware components fail independently. However, such an approach is not suitable for the tolerance of design faults. To tolerate design faults, the multiple channels have to provide identical services through separate designs and implementations [Elmendorf 1972, Randell 1975, Avizienis 1978] i.e. through design diversity. Design diversity is intended to tolerate permanent design faults. On the other hand, a backward recovery based error processing usually enables temporary design faults to be tolerated [Gray 1986] 9 Usually, removed faulty ....
W. R. Elmendorf, "Fault-Tolerant Programming", in 2nd IEEE Int. Symp. on Fault Tolerant Computing (FTCS-2), (Newton, MA, USA), pp.7983, IEEE Computer Society Press, 1972.
Dependability and Its Threats: A Taxonomy - Avizienis, Laprie, Randell (Correct)
No context found.
W.R. Elmendorf, "Fault-tolerant programming", in Proc. 2nd IEEE Int. Symp. on Fault-Tolerant Computing (FTCS-2), Newton, Massachusetts, June 1972, pp. 79-83.
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