
Software Fault Tolerance Techniques And Implementation
Description
Alles über E-Books | Antworten auf Fragen rund um E-Books, Kopierschutz und Dateiformate finden Sie in unserem Info- & Hilfebereich.
More details
Other editions
Additional editions

Content
- Intro
- Contents
- Preface
- Acknowledgments
- 1 Introduction
- 1.1 A Few Definitions
- 1.2 Organization and Intended Use
- 1.3 Means to Achieve Dependable Software
- 1.3.1 Fault Avoidance or Prevention
- 1.3.2 Fault Removal
- 1.3.3 Fault/ Failure Forecasting
- 1.3.4 Fault Tolerance
- 1.4 Types of Recovery
- 1.4.1 Backward Recovery
- 1.4.2 Forward Recovery
- 1.5 Types of Redundancy for Software Fault Tolerance
- 1.5.1 Software Redundancy
- 1.5.2 Information or Data Redundancy
- 1.5.3 Temporal Redundancy
- 1.6 Summary
- References
- 2 Structuring Redundancy for Software Fault Tolerance
- 2.1 Robust Software
- 2.2 Design Diversity
- 2.2.1 Case Studies and Experiments in Design Diversity
- 2.2.2 Levels of Diversity and Fault Tolerance Application
- 2.2.3 Factors Influencing Diversity
- 2.3 Data Diversity
- 2.3.1 Overview of Data Re- expression
- 2.3.2 Output Types and Related Data Re- expression
- 2.3.3 Example Data Re- expression Algorithms
- 2.4 Temporal Diversity
- 2.5 Architectural Structure for Diverse Software
- 2.6 Structure for Development of Diverse Software
- 2.6.1 Xu and Randell Framework
- 2.6.2 Daniels, Kim, and Vouk Framework
- 2.7 Summary
- References
- 3 Design Methods, Programming Techniques, and Issues
- 3.1 Problems and Issues
- 3.1.1 Similar Errors and a Lack of Diversity
- 3.1.2 Consistent Comparison Problem
- 3.1.3 Domino Effect
- 3.1.4 Overhead
- 3.2 Programming Techniques
- 3.2.1 Assertions
- 3.2.2 Checkpointing
- 3.2.3 Atomic Actions
- 3.3 Dependable System Development Model and N- Version Software Paradigm
- 3.3.1 Design Considerations
- 3.3.2 Dependable System Development Model
- 3.3.3 Design Paradigm for N- Version Programming
- 3.4 Summary
- References
- 4 Design Diverse Software Fault Tolerance Techniques
- 4.1 Recovery Blocks
- 4.1.1 Recovery Block Operation
- 4.1.2 Recovery Block Example
- 4.1.3 Recovery Block Issues and Discussion
- 4.2 N- Version Programming
- 4.2.1 N- Version Programming Operation
- 4.2.2 N- Version Programming Example
- 4.2.3 N- Version Programming Issues and Discussion
- 4.3 Distributed Recovery Blocks
- 4.3.1 Distributed Recovery Block Operation
- 4.3.2 Distributed Recovery Block Example
- 4.3.3 Distributed Recovery Block Issues and Discussion
- 4.4 N Self- Checking Programming
- 4.4.1 N Self- Checking Programming Operation
- 4.4.2 N Self- Checking Programming Example
- 4.4.3 N Self- Checking Programming Issues and Discussion
- 4.5 Consensus Recovery Block
- 4.5.1 Consensus Recovery Block Operation
- 4.5.2 Consensus Recovery Block Example
- 4.5.3 Consensus Recovery Block Issues and Discussion
- 4.6 Acceptance Voting
- 4.6.1 Acceptance Voting Operation
- 4.6.2 Acceptance Voting Example
- 4.6.3 Acceptance Voting Issues and Discussion
- 4.7 Technique Comparisons
- 4.7.1 N- Version Programming and Recovery Block Technique Comparisons
- 4.7.2 Recovery Block and Distributed Recovery Block Technique Comparisons
- 4.7.3 Consensus Recovery Block, Recovery Block Technique, and N- Version Programming Comparisons
- 4.7.4 Acceptance Voting, Consensus Recovery Block, Recovery Block Technique, and N- Version Programming Comparisons
- References
- 5 Data Diverse Software Fault Tolerance Techniques
- 5.1 Retry Blocks
- 5.1.1 Retry Block Operation
- 5.1.2 Retry Block Example
- 5.1.3 Retry Block Issues and Discussion
- 5.2 N- Copy Programming
- 5.2.1 N- Copy Programming Operation
- 5.2.2 N- Copy Programming Example
- 5.2.3 N- Copy Programming Issues and Discussion
- 5.3 Two- Pass Adjudicators
- 5.3.1 Two- Pass Adjudicator Operation
- 5.3.2 Two- Pass Adjudicators and Multiple Correct Results
- 5.3.3 Two- Pass Adjudicator Example
- 5.3.4 Two- Pass Adjudicator Issues and Discussion
- 5.4 Summary
- References
- 6 Other Software Fault Tolerance Techniques
- 6.1 N- Version Programming Variants
- 6.1.1 N- Version Programming with Tie- Breaker and Acceptance Test Operation
- 6.1.2 N- Version Programming with Tie- Breaker and Acceptance Test Example
- 6.2 Resourceful Systems
- 6.3 Data- Driven Dependability Assurance Scheme
- 6.4 Self- Configuring Optimal Programming
- 6.4.1 Self- Configuring Optimal Programming Operation
- 6.4.2 Self- Configuring Optimal Programming Example
- 6.4.3 Self- Configuring Optimal Programming Issues and Discussion
- 6.5 Other Techniques
- 6.6 Summary
- References
- 7 Adjudicating the Results
- 7.1 Voters
- 7.1.1 Exact Majority Voter
- 7.1.2 Median Voter
- 7.1.3 Mean Voter
- 7.1.4 Consensus Voter
- 7.1.5 Comparison Tolerances and the Formal Majority Voter
- 7.1.6 Dynamic Majority and Consensus Voters
- 7.1.7 Summary of Voters Discussed
- 7.1.8 Other Voters
- 7.2 Acceptance Tests
- 7.2.1 Satisfaction of Requirements
- 7.2.2 Accounting Tests
- 7.2.3 Reasonableness Tests
- 7.2.4 Computer Run- Time Tests
- 7.3 Summary
- References
- List of Acronyms
- About the Author
- Index
System requirements
File format: PDF
Copy-Protection: Adobe-DRM (Digital Rights Management)
System requirements:
- Computer (Windows; MacOS X; Linux): Install the free reader Adobe Digital Editions prior to download (see eBook Help).
- Tablet/smartphone (Android; iOS): Install the free app Adobe Digital Editions or the app PocketBook before downloading (see eBook Help).
- E-reader: Bookeen, Kobo, Pocketbook, Sony, Tolino and many more (only limited: Kindle).
The file format PDF always displays a book page identically on any hardware. This makes PDF suitable for complex layouts such as those used in textbooks and reference books (images, tables, columns, footnotes). Unfortunately, on the small screens of e-readers or smartphones, PDFs are rather annoying, requiring too much scrolling.
This eBook uses Adobe-DRM, a „hard” copy protection. If the necessary requirements are not met, unfortunately you will not be able to open the eBook. You will therefore need to prepare your reading hardware before downloading.
Please note: We strongly recommend that you authorise using your personal Adobe ID after installation of any reading software.
For more information, see our eBook Help page.