Component error behaviour allows propagation of too many failure states

[fletchwsf]

The intent of the component error behaviour is to only propagate {badData} when the error state is Critical Mode Failure, and {noData} when the error state is Non-Critical Mode Failure. The Fault Impact Report shows the {badData}, {noData} condition is propagated under all failure states.

See the package, computer for a complete code listing.

component error behaviour
events
cpuMad : error event {badData};
detectedFault : error event {noData};
transitions
Operational -[powerIn{NoPower}]-> NonCriticalModeFailure; -- no power serivce omission
Operational -[cpuMad{badData}]-> CriticalModeFailure; -- mad processor transmitting erroneous data
Operational -[detectedFault]-> NonCriticalModeFailure;

propagations
CriticalModeFailure -[]-> flightControlDataOut(badData);
NonCriticalModeFailure -[]-> flightControlDataOut(noData);
end component;

https://github.com/fletch787/Models.git
See branch Bug Repot 2014-07-20