Consistency Control
Objective
The consistency control allows to detect semantic anomaly in the model. These anomalies can be considered either as errors or as warnings. Depending if they imply an inconsistency of the model or if it is due to borderlline cases but required for specific usecases.
Consistency Control launching
To launch a consistency control:
- In the Project Explorer view, select a project by clicking on one of its files.
- Right Clic or simple clic on Global Analysis then Run control.
- It is also possible to launch the consistency control during the propagation.
- Select:
- The model on which the control must be done
- The different controls to be executed
- The stop condition of the control
- Clic on Finish. The Consistency Control starts. The anomalies detected are displayed in the Info Log view.


Details on executed control
Failure modes lost
This option allows to detect lost failure modes. If 2 ports are linked to eachother, they must have the same failure modes. The control is done from the top-down.
Unreachable feared events
This option allows to detect inaccessible feared events. A feared event must be used as output by a local equation.
Invalid data links
This option allows to detect invalid data links (between ports or different containers).
The rules are:
- If the source port of the link is an input port, the parent must be a container. In addition, the target port must be content by this container.
- If the target port is an output port, the parent must be a container. In addition, the source port must be content by this container.
Invalid propagation links
This option allows to detect propagation links (between failure modes, logic gates, local and global events).The rules are:
- The source can be a logic gate, an event, a failure mode on an input port or on a barrier
- The target can be a logic gate or a failure mode on an output port.
This control detect the duplicate links as well (links with the same input and output).
Feared event on input
This option allows to detect feared events that could be declared on input ports. A feared event must be declared on a failure mode belonging to an output port.
Orphans (barriers, ports and gates)
This option allows to detect oprhan elements.
The rules are :
- A port is considered as orphan if it has no data link.
- A logic gate is orphan if it doesn't have two propagation inputs and one propagation output.
- A barrier is orphan if none of his failure modes is linked with a propagation link.
Stop conditions details
Stop on first error
If this option is checked, the consistency control stops when encounting the first error.
Stop on first warning
If this option is checked, the consistency control stops when the first minor anomaly is detected.
No option checked
If no option is selected, the consistency control will go on for the entire model.
Particular case
If the consistency control is executed from the propagation phase the selected stop conditions would determine if the propagation will be launched or not.