Safety level information is a complete mess
Safety levels (“DO178C-Level A/B/C/D/E, ISO26262 1/2/3/4”) are implemented twice:
- once in mira (model element “SafetyLevel”) which is used in scheduling but is actually not even editable by the user at the moment…
- once in the safety plugin (model element “SafetyIntegrityLevel”) which is the only one really editable by the user
Question is: do we need both? Why are there even two implementations?
Gut feeling: we can remove the one in mira completely and just remove
the dependency on it in scheduling (I guess it’s in practice not used
since the property is not even definable through the UI…).
We could then use only the one in safety.
This one could also be improved in the future, as a second iteration:
- the metamodel allows in the same class SIL and DAL levels…
- the implementation is a little bit too annotation-oriented in my opinion. Meaning a developer discovering this package spontaneously thinks that it’s an “only-annotation” thing, but it can be used anywhere.
(from redmine: issue id 2873, created on 2017-03-09)