ALMAS 1.0 FTF Avatar
  1. OMG Issue

ALMAS — Definition and behaviour of AlertDistributionNotification is not consistent

  • Key: ALMAS-43
  • Legacy Issue Number: 13169
  • Status: closed  
  • Source: THALES ( Bert Van Der Meer)
  • Summary:

    The name implies that the alert has been distributed, however the description says: "...has been received..." and the sequence diagram also shows that that the alertDistributionNotification is called as soon as the alert command has been received by ALMAS. Proposed solution: Since the intention of the AlertDistributionNotification is to confirm receipt of safety critical alerts, it is logical to include the distribution of the alert because a receiver alert command may effectively not result in a alert. This could happen because it is inhibited or there are no receivers available in the system. Therefore, in Figure 6.7 (Page 30) move sequence 3.1.1 to 3.1.6. Alternatively, alert distribution could be excluded, renaming alertDistributionNotification into alertCmdReceived

  • Reported: ALMAS 1.0b1 — Fri, 19 Dec 2008 05:00 GMT
  • Disposition: Resolved — ALMAS 1.0
  • Disposition Summary:

    Change text for AlertDistributionNotification , section 6.1.1, to be: "This is called as soon as a safety critical alert has been received by the ALMAS system. The onward distribution is notified through the StateChangeNotification callback."

  • Updated: Fri, 6 Mar 2015 20:57 GMT