Algirdas Avizienis. The n-version approach to fault-tolerant software. IEEE Transactions on Software Engineering, 11(12):1491-- 1501, 1985.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....such as failures and repairs, or to voluntary requests to join or disjoin the group. Object groups can also be used to gather objects which implement the same interface, but whose methods have a different semantics, to realize processor farm parallelism [10] or to prevent from logical failures [2]. Nowadays, Java and its class library are one of the most used frameworks to realize distributed applications. It well supports point to point communication through the native RMI mechanism, but it is not enough powerful to deal with the increasing necessity of reliability and availability of ....

....section we will face some simple examples showing how to use our approach to develop applications and their features. 6.1. Fault Tolerant Servers. A classical object group application consists of managing system software fault tolerance through either object replication [19, 8] or versioning [2]. In this kind of application, groups are used to improve the reliability of the provided services. They mask the fact that the server is replicated (or versioned) insuring the client against server failures. Many frameworks providing object groups support (e.g. ISIS [5] and Totem [16] focus ....

A. Avi zienis. The N-Version Approach To Fault Tolerant Software. IEEE Trans. Softw. Eng., 11(12):1491--1501, Dec. 1985.

....using the checkpointed data structures and message log. ffl The application is connected to the replicated files on the backup node if the application restarts on the backup. Observe that these software fault tolerance tasks can be used in addition to other methods such as N version programming[Avi85] or recovery blocks [Ran75] inside an application program. Observe also that the application process on the backup node need not be running until it is started by the watchdog process and hence there are no consistency and concurrency concerns; this is unlike in the process pair model [Gra91] ....

A. Avi zienis. The n-version approach to fault-tolerant software. IEEE Transactions on Software Engineering, 11(12):1491--1501, 1985.

....tries to combine the best features of the passive and active techniques. Fault masking is used to prevent erroneous results and fault detection and recovery are used to reconfigure the system. N version programming: N version programming was designed to tolerate design and coding flaws in software[Avizienis85]. The basic concept is to design and code a software module N times and to vote the N results produced by the modules. It is hoped that by performing the N designs independently, the same mistakes will not be made in all the modules The voting module will be able to detect a fault because the same ....

....application. This includes techniques where the programmer makes calls to fault tolerance libraries or reconstructs part of the program state during recovery. An extreme example of application specific recovery is N version programming, which uses N independent implementations of the same program [Avizienis85]. Recovery blocks also use multiple implementations of a block of code, but use a passive replication style with error checking and rollback to avoid running multiple versions at the same time. Application specific recovery can be very effective, but is often prohibitively expensive to implement. ....

[Article contains additional citation context not shown here]

Algirdas Avizienis. The N-Version Approach to Fault-Tolerant Software. IEEE Transactions on Software Engineering, SE-11(12):1491-- 1501, December 1985.

....design is difficult (if not impossible) and is based mostly on qualitative arguments. Perhaps the most comprehensive effort to develop the methodology of multi version software design was carried out by Algirdas Avizienis and his colleagues at UCLA starting in the 1970s ( Avizienis 85A] Avizienis 85B] Avizienis 86] Avizienis 88] Avizienis 89] Avizienis 95A] Avizienis 95B] Avizienis 97] Although focused mainly on software, their research considered the use of design diversity concepts for other aspects of systems like the operating system, the hardware, and the user interfaces. ....

Algirdas Avizienis, The N-Version Approach to Fault-Tolerant Software, IEEE Transactions on Software Engineering, Vol. SE-11, No. 12, December 1985, pp. 290 - 300.

....techniques are used in software systems to tolerate design faults and operational faults. The techniques used to tolerate design faults, i.e. bugs in the software, are called software fault tolerance techniques. These techniques include recovery block schemes [Ran75] and N version programming [Avi85] In the recovery block scheme, programs are structured as a sequence of recovery blocks, which are program structuring units like procedures, modules, blocks, etc. Each recovery block has associated with it an acceptance test and zero or more alternate blocks. The acceptance test is a logical ....

Algirdas Avi zienis. The N-version approach to fault-tolerant software. IEEE Transactions on Software Engineering, SE-11(12):1491--1501, December 1985.

....and r point; and (7) the response to each possible outcome of an NVX decision, including absence of consensus. The NVX decision algorithm applies generic consensus rules to determine a consensus result from all valid version outputs. It has separate variants for real numbers, integers, text, etc. [Avi85b, Avi88b]. The parameters of this algorithm describe the allowable range of variation between numerical results, if such a range exists, as well as any other acceptable differences in the results from member versions, such as extra spaces in text output or other cosmetic variations. The limiting case of ....

.... about f t software are growing in numbers and in depth of understanding, and at least three long term academic hands on efforts are in their second decade: recovery blocks at Newcastle [Ran87, And88] distributed recovery blocks at UC Irvine [Chu87, Kim88] and N version software at UCLA [Avi85b, Avi88a, Avi88b]. Why should we pursue these goals Every day, humans depend on computers more and more to improve many aspects of their lives. Invariably, we find that those applications of computers that can deliver the greatest improvements in the quality of life or the highest economic benefits also can ....

A. Avi zienis. The N-version approach to fault-tolerant software. In IEEE Transactions on Software Engineering, SE-11(12):1491--1501, December 1985.

No context found.

Algirdas Avizienis. The n-version approach to fault-tolerant software. IEEE Transactions on Software Engineering, 11(12):1491-- 1501, 1985.

No context found.

Algirdas Avizienis. The N-version approach to fault-tolerant software. IEEE Transactions on Software Engineering, SE-11(12):1491--1501, December 1985.

No context found.

Algirdas Avizienis. The N -Version approach to fault-tolerant software. IEEE Transactions on Software Engineering, SE-11(12):1491-- 1501, December 1985.

No context found.

Algirdas Avizienis. The N-Version approach to fault-tolerant software. IEEE Transactions on Software Engineering, SE-11(12):1491--1501, December 1985.

No context found.

Algirdas Avizienis. The N-Version approach to fault-tolerant software. IEEE Transactions on Software Engineering, SE-11(12):1491--1501, December 1985.

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