Erudine

Behaviour Validator

Erudine’s behaviour authoring suite includes a Behaviour Validator tool that ensures system behaviour is never broken.

When the user requests behavioural changes or additions, the Behaviour Validator tool ensures that each modification is checked against the existing system behaviour model and vetted to find any potential clashes with other sets of behaviour. Should any clashes appear, the user is made aware what behavioural conflicts need to be resolved before the proposed addition or change can be introduced.

The behaviour validation process protects old behaviour from becoming inconsistent, violated or overwritten by new behaviour.

Modifying the code base is automated, with robust safeguards that alert users to any conflicts. Users can work with the confidence that overall system behaviour is under constant watch, easing the burdens of system modification: time, cost and risk.

Behaviour Validation

Here is an example of changing behaviour in a border control system. Behaviour needs to be changed so that ‘Allow Entry’ is the conclusion for a diplomat when crossing a border. You will see four tabs in the bottom panel. Each tab represents a previous set of behaviour that will conflict with this rule and clarification is needed before the proposed change can be accepted into the behaviour base.

Behaviour Validation

Here the user has resolved the conflict by informing the Erudine Behaviour Engine of the differences between the new behaviour and the previous behaviour. These differences are used to refine the rules. Once the Behaviour Validator is satisfied the justifications adequately explain the difference between the new and old behaviour, the screen turns green and the user is free to accept the proposed behaviour change.

Features

Benefits