RU ITEC421 - Dealing with Faults

Edit Answers
1234567891011121314151617181920
Across
  1. 2. A commonly used example of redundant systems (contains -)
  2. 3. Determining the extent to which the current state is in error (uses -)
  3. 7. Parity bits are an example of this method of dealing with faults.
  4. 12. Returning to normal use after an error is caught and replaced (uses -)
  5. 13. In a TMR system the Byzantine Generals problem _ be solved algorithmically
  6. 14. Any device has a _ probability of failure (contains -)
  7. 17. Removing and replacing the erroneous state with a good state (uses -)
  8. 19. The randomness of these often makes design faults appear to be triggered randomly
  9. 20. A TMR system can tolerate at most (a) _ fault(s), after which it can only detect but not tolerate further faults.
Down
  1. 1. If a fault cannot be avoided or eliminated, it must be
  2. 4. Computing this is the hardest part of fault forecasting (uses -)
  3. 5. Determining that the current state is in error (uses -)
  4. 6. Average time between failures occurring in a system (contains -)
  5. 8. Degradation faults can be considered _ if their MTTF is significantly higher than the dependability requirement of the system
  6. 9. After a fault has been eliminated, the system must be _ to make sure no new fault has been introduced
  7. 10. Because of this, fault forecasting is not purely mathematical (uses -)
  8. 11. This method admits that faults will happen and will cause failures
  9. 15. To help avoid design faults, always _ variables
  10. 16. Degradation faults are this, but design faults are not (though to users they appear to be)
  11. 18. To help avoid design faults, always include an _ clause with if statements