Issue 5418: Chapter 3, Section 4.2.2.7 "NotificationRule (uml-edoc-ftf)
Source: Distributed Models Pty Ltd (Mr. Keith Duddy, keith.duddy(at)gmail.com)
Nature: Uncategorized Issue
Severity: 
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.

Resolution: 
Revised Text: 
Actions taken:
June 13, 2002: received issue
Discussion: 

End of Annotations:=====
X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 
To: issues@omg.org 
Subject: EDOC Issue 
X-face:
*A\_v+D,~Jx_g]`m,s61-x|*;H4hgZeE=<s8=ep^q96kcoR,N|3]/;|F"C);wi^I6"-X}\# 
 NxV@i.&hb;o3+@m{cTE\D;uA&N`N2kHXc"<\2N8-+GJJSsAk3DcF6I@fM8[k,t$)^*YO=1F)A&[+-m 
  Jivdt{kFM4&a"}5Mi08HK6J8\W!tYX//<Jr4nX"u~65X0<R5172|K7-I"9/HcB}ENVsBq{lq 
Date: Thu, 13 Jun 2002 13:39:02 +1000 
From: Keith Duddy <dud@dstc.edu.au> 
X-Scanned-By: MIMEDefang 1.0
(http://www.roaringpenguin.com/mimedefang/) 


Chapter 3, Section 4.2.2.7 "NotificationRule"


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.


|<
--
[[[[=================================================================]]]]
Keith Duddy  : dud at dstc.edu.au  :
http://www.dstc.edu.au/AU/staff/dud
       CRC for Enterprise Distributed Systems Technology (DSTC)
   General Purpose South, University of Queensland, 4072, Australia
            ph: +61 7 336 5 4310  ::  fx: +61 7 336 5 4311
                    DSTC is the Australian W3C Office
[[[[[[[[[[[[=================================================]]]]]]]]]]]]
        EDOC 2002 Conference    :     http://edocconference.org
6th IEEE International Enterprise Distributed Object Computing
Conference
                        September 17-20, 2002
[[[[=================================================================]]]