L. Chen and A. Avizienis. "N-Version Programming: A faulttolerance approach to reliability of software operation," in Proc. 8th IEEE Int. Symp. on FaultTolerant Computing (FTCS-8), pp. 3-9, Toulouse, France, 1978.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....Computer (PFC) system in Boeing 777 [Riter 95] The Boeing 777 used three different processors from AMD, Intel and Motorola to avoid a common failure among three processor modules. Design diversity also has been applied to software systems [Lyu 91] N version programming (NVP) Avizienis 77] Chen 78] Avizienis 85] and Consensus recovery block [Scot 83] Scot 87] are examples of the design diversity in software. N self checking programming, a variant of NVP, is another data diversity technique and is used in the Airbus A310 system [Laprie 90] Dugan 93] I will be described in Chapter 5. In ....

L. Chen and A. Avizienis, "N-version programming: A fault-tolerance approach to reliability of software operation," IEEE 8th FTCS, pp. 3-9, 1978.

....issue in such systems. In real time multiprocessor systems, fault tolerance can be provided by scheduling multiple versions of tasks on different processors. Four different models (techniques) have evolved for fault tolerant scheduling of real time tasks, namely, i) N version programming [1], ii) Primary Backup (PB) model [2, 12] iii) Im precise Computational (IC) model [8] and (iv) m, k) firm deadline model [16] In the N version programming approach, N versions of a task are executed concurrently and the results of these versions are voted on. If N is 2, single fault can be ....

L. Chen and A. Avizienis, "N-version programming: A fault tolerance approach to reliability of software operation," In Proc. IEEE Fault-Tolerant Computing Syrup, pp.3-9, 1978.

....timely manner even in the presence of faults. This makes fault tolerance an inherent requirement of any real time system. The basic principle of fault tolerant design is redundancy. Four different techniques have evolved for fault tolerant scheduling of real time tasks: N Version Programming (NVP) [17], Recovery Blocks (RB) 87] Imprecise Computations (IC) 58] and (m; k) firm deadline model [33, 85] 1.4.1 Space Time Tradeoff Redundancy costs both money and time. Therefore, a fault tolerant system should optimise the design by trading off the amount of redundancy used and the desired level ....

L. Chen and A. Avizienis, "N-version programming: A fault-tolerance approach to reliability of software operation," Fault-tolerant Computing Symposium, pp.15-22, 1988.

....testing per se is in the area of assessing implementation diversity for multi version systems. One way to improve dependability is to use multiple, independently developed versions of software in the hope that different versions are diverse in nature, and thus have differing failure modes [8][1] This is a way of exploiting inherent design diversity in separately designed systems, in an analogy to exploiting diversity among multiple independently manufactured hardware subsystems. One issue with using multi version software is whether or not such software is truly diverse. There are ....

Chen, L., Avizienis, A., "N-Version Programming: A Fault Tolerance Approach to Reliability of Software Operation," The Eighth International Synposiun on Fault Tolerant Conputing, p. 3-9, 1978.

....results [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 ....

Chen, L. and Avizienis, A. "N-version programming: a fault-tolerance approach to reliability of software operation." Proceedings of the 8th Annual International Symposium on Fault-Tolerant Computing (FTCS-8). Los Alamitos, CA: IEEE Computer Society Press. Tolouse, France (June 1978) 3-9.

....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 ....

L. Chen and A. Avizienis, "N-Version Programming: a Fault Tolerance Approach to Reliability of Software Operation", Proc. 8th Int. Symp. Fault-Tolerant Computing (FTCS-8), Toulouse, France, 1978, pp. 3-9.

....84] Thus, the basic idea behind using design diversity is that, with different implementations, the error effects of a CMF will possibly be different so that error detection is possible. The concept of design diversity has been used in both software and hardware systems. N version programming [Chen 78] is a technique in which three different versions of the same software (generated independently) are used to design a redundant software system. In addition to N version programming, there are other diversity techniques (e.g. data diversity, functional diversity, etc. for protecting redundant ....

Chen, L. and A. Avizienis, "N-Version Programming: A Fault-Tolerance Approach to Reliability of Software Operation," Proc. FTCS, pp. 3-9, 1978.

....issue in such systems. In real time multiprocessor systems, fault tolerance can be provided by scheduling multiple versions of tasks on different processors. Four different models (techniques) have evolved for fault tolerant scheduling of real time tasks, namely, i) N version programming [1], ii) Primary Backup (PB) model [2, 12] iii) Imprecise Computational (IC) model [8] and (iv) m; k) firm deadline model 1 [16] In the N version programming approach, N versions of a task are executed concurrently and the results of these versions are voted on. If N is 2, single fault can be ....

L. Chen and A. Avizienis, "N-version programming: A fault tolerance approach to reliability of software operation," In Proc. IEEE Fault-Tolerant Computing Symp., pp.3-9, 1978.

....programming, Multiversion software, Software Reliability, Software reliability models, Mean time to failure, Correlation Coefficient. 1 All correspondence should be directed to the first author jalote iitk.ernet.in, Fax: 91 512250007 250260. 1 Introduction N Version Programming (NVP) [9, 4] and recovery blocks [25] are the two well known techniques that have been proposed for providing fault tolerance against software design faults. For providing fault tolerance, they employ N independently developed versions of the software. In NVP the versions are invoked with the same input, and ....

L. Chen and A. Avizienis, "N-version programming: a fault tolerance approach to reliability of software operation", Dij. Papers, FTCS-18, Tokyo, Japan, 1988, pp. 1522.

....has been addressed to the formation of a set of guidelines for systematic design approach to implement NVS systems, in order to achieve efficient tolerance of design faults in computer systems. The gradual evolution of these rigorous guidelines was revealed in several previous research activities[4], 5] 6] which have investigated a total of 81 programs in four different applications. This evolving methodology was most recently formulated in[7] as an NVS design paradigm by integrating the knowledge and experience obtained from both software engineering techniques and fault tolerance ....

....software engineering, prototyping, computer aided software engineering, or even the clean room approach[14] A qualitative design diversity metric is proposed in Table 1. This assessment of diversity is an initial effort based on the experiences gained from previous experiments at UCLA[4], 5] 15] and published work from other sites[12] 13] 16] 17] ###################################################### imple lan algo methodmentors guages tools rithms ologies ###################################################### ....

[Article contains additional citation context not shown here]

L. Chen and A. Avizienis, "N-Version Programming: A Fault-Tolerance Approach to Reliability of Software Operation," Digest of 8th Annual International Symposium on Fault-Tolerant Computing, pp. 3-9, Toulouse, France, June 1978.

....Software engineers assume that the various programs are sufficiently different that they contain different faults. Fault tolerant software built in this manner is referred to as design diverse software. A well known method for building design diverse software is N version programming [6,11]. N version programming requires multiple (i.e. N ) programs (i.e. versions) to be built for a given specification, a decision algorithm or voter for choosing which outputs to use (the majority for example) and a monitor or execution time support system to manage the versions. The versions ....

Chen, L., and A. Avizienis, "N-version Programming: A Fault-Tolerance Approach to Reliability of Software Operation," in Digest of papers of the 8th International Symposium on Fault-Tolerant Computing, Tolouse, France, 1978, pp. 3-9.

....reaching the pump) This impact was represented graphically through the use of the PMS notation and informally through the description of the mapping. Reliability can also be introduced through the use of more explicit techniques (as against design mapping decisions) such as N modular redundancy [27]. Here a logical component is replicated a number of times to produce a number of physical components that must be implemented individually. These physical components can then be mapped onto separate processors to provide the actual redundancy. The results of each physical component can then be ....

Chen, L and Avizienis, A, "N-Version Programming: A Fault-Tolerance Approach to Reliability of Software Operation", pp. 3-9 in Digest of Papers, The Eighth Annual International Conference on Fault-Tolerant Computing (June 1978).

No context found.

L. Chen and A. Avizienis. "N-Version Programming: A faulttolerance approach to reliability of software operation," in Proc. 8th IEEE Int. Symp. on FaultTolerant Computing (FTCS-8), pp. 3-9, Toulouse, France, 1978.

No context found.

Chen, L., and A. Avizienis, "N version Programming: A Fault-Tolerance Approach to Reliability of Software Operation," Proceedings of the 8th Intl. Symposium on Fault-Tolerant Computing, pp. 3-9, Toulouse, France, 1978.

No context found.

L. Chen and A. Avizienis, "N-version programming: A fault tolerance approach to reliability of software operation," In Dig. Papers, FTCS-8, 1978, pp. 3-9.

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