Resilience assurance in this guide is based on the iterative approach, integrating the proactive with the reactive approach (learning cycles ... ).

System definition by iterations

System definition is an iterative process as illustrated in the chart. The definition starts with concept definition and requirements specification . Then, a first version of the system is developed. The definition at this stage is proactive. When ready, the first version is deployed and operation begins.

A critical incidence might instigate an investigation, intended to identify changes in the requirements. The definition at this stage is reactive.

The proactive part

Proactive resilience assurance focuses on preventing incidences by design. The guidelines are based on a resilience model .... According to the model, mishaps may be prevented by three primary firewalls.

The reactive part

Reactive resilience assurance focuses on learning from incidences. The guidelines are about capturing, recording, reporting and tracking the measures taken to prevent repeating the incidences.

The iterative approach to system design is described here ...

Guidelines

The guidelines of this guide should be integrated in the procedures of system development.

• The guidelines intended for proactive assurance  may help you with the primary development activities, about the requirement specification, design and testing.
• The guidelines intended for reactive assurance may help you with the auxiliary development activities, regarding the logging, analysis and reporting about incidences.

Updated on 25 May 2017.