Issue 5056: SA Profile Example (uml-scheduling-ftf)
Source:  (, )
Nature: Uncategorized Issue
Severity: 
Summary: In these examples, the links represent the initial events, and we could represent this concept linking an actor instance to the SAEvent Link. But if we want to represent events that are not originated by external actors (for example a cyclic object executed periodically) other solutions are need (for example a classifier stereotype like SACyclic with a tagged value that identifies the sequence message generated periodically [2]). 

Resolution: see below
Revised Text: In section 6.2.2.3. modify the base classes of "SAtrigger" to include Classifier,
ClassifierRole, Instance, Object, Node, Method.

Actions taken:
March 20, 2002: received issue
September 24, 2004: closed issue
Discussion: 
Create new standalone tag-value called RecurrencePattern, which can be attached to active objects (amongst other things); I will look into this (Bran). This could be solved by allowing SAtrigger to apply to a wider category of UML model elements, in particular it appears, Classifiers. I suggest we do that.

End of Annotations:=====
this is issue # 5056

SA Profile Example

In these examples, the links represent the initial events, and we
could represent this concept linking an actor instance to the SAEvent
Link. But if we want to represent events that are not originated by
external actors (for example a cyclic object executed periodically)
other solutions are need (for example a classifier stereotype like
SACyclic with a tagged value that identifies the sequence message
generated periodically [2]). 


Issue 5056
This could be solved by allowing SAtrigger to apply to a wider category of UML model elements, in particular it appears, Classifiers. I suggest we do that.
Recommendation: Fix in the 1.1 revision