Software Implemented Fault Injection using Failure Models

Method Purpose Short description of the method's purpose and main benefits

Method description A detailed description of the method

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.

Method Strengths A listof the strengths of the method

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.

Method Limitations The limitations of the method

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 References Bibliography references to papers about the method.

Method Dimensions

Evaluation Environment Type Type of environment where the method is applied. It can be more than one type of environment. (Dimension 1)

Evaluation Type Type of evaluation performed with that method. If a method is hybrid, more than one type can be selected. (Dimension 2)

Type of Component Under Evaluation Type of components that can be evaluated with that method. It can be more than one type. (Dimension 3)

Evaluation Stage The evaluation stage where the method is used. (Dimension 5)

Purpose of the Component Under Evaluation The type of purpose that can be evaluated by a method. It can be more than one type. (Dimension 6)

Type of Requirement Under Evaluation The type of requirements that a method is able to evaluate. It can be more than one type. (Dimension 7)

Evaluation Performance Indicator The type of evaluation criteria or KPI that a method is able to improve. It can be more than one type. (Dimension 8)

Relations

Related Methods A method could be related to other methods.

Tools A method can use zero or more tools.

Part Method A method (when it is a combination: Combination of method artefact that is a specialization of a V&V Method) could be composed of a set of V&V Methods.

Test Case or Verification and Validation activity Test Case or V&V activity performed in a Use Case. We will link to the method to the test cases where the method is used.

Standards A method can be linked with standards.

Context

Workflow

Contents

There are currently no items in this folder.