Scenario Space Exploration with Support for Fault Injection

[gitting-around]

We are interested in defining different scenarios that can be run as a batch automatically from the app, and generate some sort of report at the end. These scenarios are configured through different parameters with the goal of evaluating the behaviour and performance of the desired system.
Let's assume that the desired system is the line follower robot. Let's also assume that we want to verify whether this robot behaves as we expect in different conditions, e.g. avoiding an obstacle. Different scenarios could be created by manipulating for e.g. the number of obstacles, whether they're static or dynamic, the size of the area the robot moves around, its speed, and even the number of robots. In one scenario we could have one robot going at a certain speed in an area with one static obstacle. In another scenario we could have 3 robots, each performing some sort of task, at different speeds going around. Additionally, we want to be able to play with scenarios in which we inject different kinds of faults.

Exploring different scenarios, is basically sweeping through different given parameters. Very much similar to what the DSE does. However, there are some key differences. First, the purpose of the scenario exploration is to verify the behaviour of the system, rather than finding an optimal design. Second, the fault injection aspect takes the contribution further and makes it possible to perform a wider range of experiments and analysis.

Our solution will be based on the dse-scripts but has to cover for the functionality needed for the scenario exploration and fault injection. We are circulating some ideas, which we can document here. For example:

• If we want to create 5 robots in the scenario. First we'd need to define what a robot is (which fmus would consist of the robot), their connections. Then we'd replicate that 5 times, if the 5 robots ought to be homogeneous. Otherwise we'd need to allow the specification of different robots, in terms of parameters, as well as fmus.
• Visualise through the app the period in which the fault is active.