Issue 5047: concepts introduced can be redundant with UML (uml-scheduling-ftf)
Source:  (, )
Nature: Uncategorized Issue
Severity: 
Summary: Other concepts introduced can be redundant with UML modeling elements or attributes; for example SynchronousInvoke and AsynchronousInvoke are redundant with attributes of methods and operation attributes in UML metamodels

Resolution: 
Revised Text: 
Actions taken:
March 20, 2002: received issue
Discussion: 
This was intentional, but may need to be looked into; the problem is that some of the existing UML models of such things tended to be rather naïve and did not fit well into the more sophisticated models required here; however, I will revisit this and see if something can be done (Bran). Valid comment but it should be taking into account in the context of an alignement work with UML2.0. It implies, it is out of the scope of this RTF.

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

concepts introduced can be redundant with UML

Other concepts introduced can be redundant with UML modeling elements
or attributes; for example SynchronousInvoke and AsynchronousInvoke
are redundant with attributes of methods and operation attributes in
UML metamodels