This section describes requirements that should be included in the specification documents in order to assure the system resilience. Use it as an integral part of the system requirement specification.

When to use

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

How to use

  Proactive requirements are based on the functional requirements and on risk analysis. It should include requirements about both the primary and secondary protection layers.

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, such as sensors and indicators, required for hazard detection and identification
• Interaction styles : interaction styles optimized according to the operational situation
• Resilience modules ... : specification of 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 08 Mar 2017.