Software Implemented Fault Injection using Failure Models

The purpose of software implemented fault injection using failure models is the same as that of its base model, software implemented fault injection. Their purpose is to evaluate system behaviour in the presence of faults or to validate specific fault tolerance mechanisms in the target system.

Software-implemented fault injection using failure models uses a variety of software-based techniques for inserting failures in a system-under-study. The main difference to its base method is the emulation of failures instead of faults or errors, which enables a reduction in the time taken for the evaluation. Emulating failures may require, in terms of implementation, a slightly different approach. However, the usual software-based methods that are used for software implemented fault injection can be repurposed.

  • Capable of evaluating the dependability of real systems and validating fault tolerance mechanisms  
  • Can significantly accelerate the generation of failure data 
  • Can be ported to different hardware architectures, operating systems, etc. 
  • Requires the existence of a prototype or a real system for evaluation  
  • The used fault models should be realistic and represent faults that the system may experience  
  • Intrusiveness in the system because of the fault injection tool may skew the results  
Method Dimensions
In-the-lab environment
Experimental - Testing
Hardware, Software
System testing, Acceptance testing
Thinking
Non-Functional - Safety, Non-Functional - Other
V&V process criteria, SCP criteria
Relations
Contents

There are currently no items in this folder.