Last edited by Zulushicage
Monday, August 10, 2020 | History

3 edition of Second generation experiments in fault tolerant software found in the catalog.

Second generation experiments in fault tolerant software

J. C. Knight

Second generation experiments in fault tolerant software

by J. C. Knight

  • 366 Want to read
  • 5 Currently reading

Published by Dept. of Computer Science, School of Engineering and Applied Science, University of Virginia, National Aeronautics and Space Administration, National Technical Information Service, distributor in Charlottesville, Va, [Washington, DC, Springfield, Va .
Written in English

    Subjects:
  • Applications programs (Computers),
  • Computer programming.,
  • Failure analysis.,
  • Fault tolerance.,
  • Flight simulation.,
  • Software engineering.

  • Edition Notes

    Statementsubmitted by J.C. Knight.
    SeriesNASA contractor report -- NASA CR-180675.
    ContributionsUnited States. National Aeronautics and Space Administration.
    The Physical Object
    FormatMicroform
    Pagination1 v.
    ID Numbers
    Open LibraryOL17683836M

      The simplest approximation of the actual size of the N-version system is k=N Spacek + Space~,oter + Spacedri, er k=l Acknowledgement--The authors would like to thank the referee for helpful comments on an earlier version of this paper. REFERENCES 1. Knight J. C., Second generation experiment in fault-tolerant software. A cost model determines system costs for fault-tolerant software systems. The model finds the optimal number of program versions to achieve minimum system cost of the fault-tolerant software.

    The book is dedicated as an introduction in teaching the field of fault detection and diagnosis, and fault-tolerant systems for graduate students or students of higher semesters of electrical and electronic engineering, mechanical and chemical engineering and computer s: 1. International Conference on Managing Next Generation Software Application (MNGSA), Coimbatore, It is the same as PB method except that exception handlers are executed instead of backup programs. Primary Backup Fault Tolerance This is the traditional fault-tolerant approach wherein both time as well as space exclusions are used.

    fault-tolerance models. 2. Results Reliability of Voting in Fault-Tolerant Software Systems for Small Output Spaces Under a voting strategy in a fault-tolerant software system there is a difference between correctness and agreement. An independent N-version. Software fault tolerance is an immature area of research. As more and more complex systems get designed and built, especially safety critical systems, software fault tolerance and the next generation of hardware fault tolerance will need to evolve to be able to solve the design fault problem.


Share this book
You might also like
Building cooperative movements in developing countries

Building cooperative movements in developing countries

International judicial co-operation

International judicial co-operation

Cyprus Crustal Study Project

Cyprus Crustal Study Project

study of religions

study of religions

Theories of Counselling

Theories of Counselling

An Investment for the Uncertain 1990s

An Investment for the Uncertain 1990s

Petroglyph National Monument, New Mexico

Petroglyph National Monument, New Mexico

short-story

short-story

Batujimbar Bali

Batujimbar Bali

Labor relations law: appendix

Labor relations law: appendix

spark

spark

Joseph A. Lauwerys

Joseph A. Lauwerys

Indian national movement

Indian national movement

Take home fluency

Take home fluency

Creating urban data using AVHRR thermal-infrared data

Creating urban data using AVHRR thermal-infrared data

Artists and writers in Paris

Artists and writers in Paris

Treatise on Government

Treatise on Government

Second generation experiments in fault tolerant software by J. C. Knight Download PDF EPUB FB2

Get this from a library. Second generation experiments in fault tolerant software. [John C Knight; United States. National Aeronautics and Space Administration.].

A second generation experiment in fault-tolerant software: semi-annual progress report, September 1, Decem Author: John C Knight ; United States. the efficacy of fault-tolerant software by conducting two large-scale controlled experiments. In the first, an empirical study of multi-version software is being conducted.

This experiment will be referred to as the “MVS” experiment in this report. The second experiment is an empirical. A second generation experiment in fault-tolerant software.

By J. Knight. Abstract. The primary goal was to determine whether the application of fault tolerance to software increases its reliability if the cost of production is the same as for an equivalent nonfault tolerance version derived from the same requirements specification.

Software Author: J. Knight. A second generation experiment in fault-tolerant software. By J. Knight. Abstract. Information was collected on the efficacy of fault-tolerant software by conducting two large-scale controlled experiments. In the first, an empirical study of multi-version software (MVS) was conducted.

The second experiment is an empirical evaluation of self Author: J. Knight. J.P.J. Kelly, D. Eckhardt, A. Caglayan, J. Knight, D. McAllister, M.

Vouk, A Large Scale Second Generation Experiment in Multi-Version Software: Description and Early Results, 18th Annual International Symposium on Fault-Tolerant Computing, June This book examines fault-tolerance techniques for SRAM-based FPGAs, beginning with modeling of the problem and the upset effects in the programmable architecture.

The Second Generation Experiment is a large scale empirical study of multi-version software systems engaging researchers at six sites.

This paper presents UCLA's perspective of this experiment, its role in the preliminary analysis, and related research at the Dependable Computing and Fault Tolerant Systems Laboratory. Thisreport isan introduction to fault-tolerance concepts and systems, mainly from the hardware point of view.

An introduction to the terminology is given, and different ways of achieving fault-tolerance with redundancy is studied. Knowledge of software fault-tolerance is important, so an introduction to software fault-tolerance is also given.

The second term corresponds to the probability that acceptance test i judges an incorrect result as correct at the ith trial of the n versions.

N-version Programming – NVP is used for providing fault-tolerance in software. In concept, the NVP scheme is similar to the N-modular redundancy scheme used to provide tolerance against hardware faults. Abstract. The N-Version Programming (NVP) approach achieves fault-tolerant software units, called N-version Software (NVS) units, through the development and use of software maximize the effectiveness of the NVP approach, the probability of similar errors that coincide at the NVS decision points should be reduced to the lowest possible value.

Huang, software fault tolerance in the application layer (ch 10) In: Lyu, Ed., Software Fault Tolerance, Wiley & Sons, ; Iyer, software fault tolerance in computer operating systems (ch 11) In: Lyu, Ed., Software Fault Tolerance, Wiley & Sons, A SECOND GENERATION EXPERIMENT IN FAULT-TOLERANT SOFTWARE Submitted to: National Aeronautics and Space Administration Langley Research Center Hampton, Virginia Attention: Dr.

Eckhardt, Jr. FCSD M/S Submitted by: J. Knight Associate Professor Report No. UVA//CS86/ March (NASA-CE) A SECOND GENERATION NU The purpose of this paper is to summarize major issues in providing the capabilities for tolerance of both hardware faults and software faults in real-time computer systems (DCS’s).

The paper starts with several guidelines considered to be highly useful in searching for effective system-level fault tolerance schemes. A Large Scale Second Generation Experiment in Multi-Version Software: Description and Early Results, Digest of F International Symposium on Fault-Tolerant.

Both machines employed hybrid redundancy. The first, designated Software Implemented Fault Tolerance (SIFT), was developed by SRI International. It used off-the-shelf computers and achieved voting and reconfiguration primarily through software.

The second machine, the Fault-Tolerant Multiprocessor (FTMP), developed by the C. Fault-Tolerant Software: Basic Concepts and Terminology: /ch After having described the main characteristics of dependability and fault-tolerance, it is analyzed here in more detail what it means that a program is.

This book introduces the main ideas offault diagnosis and fault-tolerant control. It gives a thorough survey of new methods that have been developed in the recent years and demonstrates them with examples. To the knowledge of the authors, all major aspects of fault-tolerant control are treated for the first time in a single book.

A significant issue in fault injection experiments is that the injected faults are representative of software faults observed in the field. Another important issue is the time used, as we want experiments to be conducted without excessive time spent waiting for the consequences of a fault.

An approach to accelerate the failure process would be to inject errors instead of faults, but this would. It has been argued that fault tolerance management during the entire life-cycle improves the overall system robustness and that different classes of threats need to be identified for and dealt with at each distinct phase of software development, depending on the abstraction level of the software system being modelled.

This book builds on this. B. Littlewood, D. Miller, “A conceptual Model of the Effect of Diverse Software Methodologies on Coincident Failures in Multi-Version Software”, Int.

Conference on Fault-Tolerant Computing Systems, Bremerhaven,Informatik-Fachberichte.A SECOND GENERATION EXPERIMENT IN FAULT-TOLERANT SOFTWARE IM- Submitted to: 3/w7 National Aeronautics and Space Administration Langley Research Center Hampton, VA Attention: Dr.

Dave E. Eckhardt ISD M/S Submitted by: J. C. Knight Associate P rof es sor Report No. UVA//CS87/ August Fault tolerance is the property that enables a system to continue operating properly in the event of the failure of (or one or more faults within) some of its components.

If its operating quality decreases at all, the decrease is proportional to the severity of the failure, as compared to a naively designed system, in which even a small failure can cause total breakdown.