UC5 Eval Criteria SCP-2/Mapping 1-3

Construction of Event-B model to verify the system design against the formalised requirements
UC5
Modelling of system in Event-B, using a simulink model and natural language requirements as quidance, supporting automated verification tools in detecting safety requirement violations.
Evaluation Criteria for Safety, Cybersecurity, and Privacy (SCP)
Number of safety/security requirement violations

The aerospace use case which is focused on an aircraft engine software controller has not yet detected specific safety/security requirement violations (although work is ongoing). 

Requirement violations can be detected by a number of verification activities including formal methods, simulation, testing and run-time monitoring. However, it is important that when violations are detected that the root cause of the conflict is identified and resolved. One way to detect such violations is to construct a new formal model of the system, which accurately models the system's design and can rigorously check it's behavior against the requirements. Event-B is one formal language which can be used to construct such a model. It is based on set theory, where individual behaviors are modelled as 'events' which can be performed whenever their specified guards are true during runtime. Theorem proving techniques are then used to check that any specified 'invariants' hold over all possible execution traces.

Contents

There are currently no items in this folder.