Automatic specification of reliability models for fault-tolerant computers
Read Online
Share

Automatic specification of reliability models for fault-tolerant computers

  • 871 Want to read
  • ·
  • 33 Currently reading

Published by National Aeronautics and Space Administration, Office of Management, Scientific and Technical Information Program, National Technical Information Service, distributor] in [Washington, DC], [Springfield, Va .
Written in English

Subjects:

  • Fault-tolerant computing.

Book details:

Edition Notes

StatementCarlos A. Liceaga and Daniel P. Siewiorek.
SeriesNASA technical paper -- 3301., NASA technical paper -- 3301.
ContributionsSiewiorek, Daniel P., United States. National Aeronautics and Space Administration. Scientific and Technical Information Program.
The Physical Object
FormatMicroform
Pagination1 v.
ID Numbers
Open LibraryOL14701743M

Download Automatic specification of reliability models for fault-tolerant computers

PDF EPUB FB2 MOBI RTF

Automatic specification of reliability models for fault. Automatic Specification of Reliability Models for FaultTolerant Computers", NASA Techreport By Carlos A. Liceaga, Daniel P. Siewiorek Nasa, Carlos A. Liceaga and Daniel P. Siewiorek Abstract. CiteSeerX - Document Details (Isaac Councill, Lee Giles, Pradeep Teregowda): Semi-Markov Specification Interface to the SURE Tool) program, which uses an abstract language for specifying Markov reliability models, is described in Butler (). The language has statements to specify the state space, by defining the state variables and their range; the start state, by the initial values of the. In this book, bestselling author Martin Shooman draws on his expertise in reliability engineering and software engineering to provide a complete and authoritative look at fault tolerant computing.

CiteSeerX - Document Details (Isaac Councill, Lee Giles, Pradeep Teregowda): Pittsburgh, PennsylvaniaThe use of trademarks or names of manufacturers in this report is for accurate reporting and does not constitute an o cial endorsement, either expressed or implied, of such. To achieve the needed reliability and availability, we need fault-tolerant computers. They have the ability to tolerate faults by detecting failures, and isolate defect modules so that the rest of the system can oper-ate correctly. Reliability techniques have also become of increasing interest to general-purpose computer systems.   8. Quantifies the effect of fault removal and fault tolerance. Fault-removal and fault-tolerant tech- niques are particularly relevant for process safety systems. Thus, reliability models of safety systems must consider the effect of these techniques if you want reliability predictions to reflect field performance. Software Reliability Models Jelinski–Moranda Model Littlewood–Verrall Model Musa–Okumoto Model Model Selection and Parameter Estimation Fault-Tolerant Remote Procedure Calls Primary-Backup Approach The Circus Approach Further Reading Exercises

Basic concepts, motivation, and techniques of fault tolerance are discussed in this paper. The topics include fault classification, redundancy techniques, reliability modeling and prediction, examples of fault-tolerant computers, and some approaches to the problem of tolerating design faults. Lecture 1 Lecture Notes on Introduction to Reliability and Fault Tolerance, by Youmin Zhang (AUE)13 References and Reading Materials † Textbook and references 9William R. Dunn, Practical Design of Safety-Critical Computer Systems, Reliability Press, July 9N. Storey, Safety-Critical Computer Systems, Addison-Wesley, 9Laura L. Pullum: Software Fault Tolerance: Techniques and. Hybrid reliability modeling of fault-tolerant computer systems. Applied computing. a reduction of state space by the behavioral decomposition of a reliability model along temporal lines into fault-occurrence and fault-handling submodels, and (2) the solution of these submodels using appropriate analytic or simulative techniques. The FTMP (Fault-Tolerant Multiprocessor) is a complex multiprocessor computer that employs a form of redundancy related to systems considered by Mathur (), in which each major module can.