EDOC 1.0 NO IDEA Avatar
  1. OMG Issue

EDOC — Chapter 3, Section 4.2.2.7 "NotificationRule

  • Key: EDOC-43
  • Legacy Issue Number: 5418
  • Status: open  
  • Source: Distributed Models Pty Ltd ( Keith Duddy)
  • Summary:

    It is not clear whether the EventCondition guarding a NotificationRule
    needs to be satisfied before or after the NotificationRule Condition
    Expression, or whether it is simply an AND relationship with no ordering.

    Also, as the guardedBy association has 0..n multiplicity at the
    EventCondition end, there needs to be text explaining how multiple
    guards are treated. The text currently says that "one or more
    EventConditions calling for the receipt of additional events before
    this NotificationRule will 'fire' successfully". Are there time bounds
    on the receipt of these additional event notifications? Do all guards
    'reset' once the NotificationRule'fires'?

    Suggested Resolution: Guard(s) should be satisfied first. Add text to
    Section 4.2.2.7 "Related Elements - EventCondition" stating that the
    EventCondition(s) associated with the NotificationRule by the guardedBy
    Association must be satisfied before the NotificationRule's Condition
    is evaluated.

    Also: some text suggesting a timeout mechanism that could be included
    in the condition expression of the guarding EventCondition.

  • Reported: EDOC 1.0b1 — Thu, 13 Jun 2002 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT