The section describes requirements that should be included in the specification documents in order to assure the system resilience.

When to use

  This section presents a description of resilience-oriented requirement specification. Use it as part of the requirement specification.

  The resilience requirements should affect the system design, therefore, you should use this section prior to the system design.

The specification documents for resilience assurance

  The specification document should include:

• Hazard definition : a list of expected hazards, typically, due to unit failure.  The list can be obtained using traditional methods of root-cause-analysis.
• Functional add-ons : a list of features included in the functional unit, such as sensors and state indicators, required for hazard detection and identification
• Interaction styles : definition of interaction styles optimized according to the operational situation
• Resilience modules ... : guidelines for designing the units included in the architecture.
• A description of the operational rules, as follows.

The operational rules

The operational rules should define the design scope. They should describe the procedures used in normal (routine and under hazard ) operations, and conditions for normal scenarios and for scenario-situation matching

The operational rules should be arranged according to the knowledge bases, as follows:

• Scenario knowledge base
• Situation knowledge base
• Activity knowledge base

Updated on 23 Oct 2016.