Issue 5059:  SAStep issue (uml-scheduling-ftf)
Source:  (, )
Nature: Uncategorized Issue
Severity: 
Summary: If we include SAStep in the objects to represent the messages sequences we will not respect the method used in UML 1.3, because the element stereotyped are the objects and not the messages, and we can not use the sequence activator-predecessor to define the response sequence with steps associated to objects. Another problem: If we associate more than one SAStep to the object, who defines the order? we need some kind of tagged value in the stereotype to do this.

Resolution: Closed, no change
Revised Text: 
Actions taken:
March 20, 2002: received issue
June 30, 2003: closed issue
Discussion: 
The order will be defined by the ordering of the underlying actions

End of Annotations:=====
This is issue # 5059

 SAStep issue

If we include SAStep in the objects to represent the messages
sequences we will not respect the method used in UML 1.3, because the
element stereotyped are the objects and not the messages, and we can
not use the sequence activator-predecessor to define the response
sequence with steps associated to objects. Another problem: If we
associate more than one SAStep to the object, who defines the order?
we need some kind of tagged value in the stereotype to do this.