osate / osate2

Open Source AADL2 Tool Environment
http://osate.org
Eclipse Public License 2.0
40 stars 8 forks source link

EMV2: validation that all features have error propagations #965

Open reteprelief opened 6 years ago

reteprelief commented 6 years ago

There should be an error propagation for each feature in a classifier. A quickfix can prefill the subclause with propagations. Currently there is no consistency rule in the standard that states the above.

lwrage commented 6 years ago

Even though this is not required by the standard we could implement it as an analysis under semantic checks.

reteprelief commented 6 years ago

We already have the ability to specify flows to go from all incoming propagations to all outgoing propagations. This is the default if no flows are specified. We could extend the default to say from all incoming features to all outgoing features.

We could have several consistency/completeness checks, one of which would make sure all the error types are covered. Another would make sure that all features have explicitly defined error propagations. Similarly all error propagations should be mentioned by flows if we want to ensure users specify flows explicitly. There is also the case where all flows should have an equivalent out propagation condition, i.e., we have component error behavior specification for all flows (note the latter I am now checking to interpret flows in those cases where an outgoing propagation condition does not exist.