Issue 5014: GRM Profile issue (02) (uml-scheduling-ftf)
Source:  (, )
Nature: Uncategorized Issue
Severity: 
Summary: The stereotype GRMconxtet is limited to collaboration, package and instance, but most of examples included in the proposal associate a diagram to collaborations or packages and stereotype the collaboration or package. An alternative would be to stereotype the diagrams, but it is not possible in UML 1.3. May be in UML 1.4. An alternative would be a configuration based on diagrams. If we represent the same collaboration with two alternative collaboration diagrams (two possible solutions) we can configure the analysis for a specific solution. If we stereotype the collaboration, what are we going to do? do we include both diagrams with all its elements?

Resolution: Closed, no change
Revised Text: 
Actions taken:
March 20, 2002: received issue
June 30, 2003: closed issue
Discussion: 
Agree - this is a UML problem. This is possible, based on a single coherent description, using Analysis Context. There is a misunderstanding of UML underlying this comment

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

GRM Profile issue (02)

The stereotype GRMconxtet is limited to collaboration, package and
instance, but most of examples included in the proposal associate a
diagram to collaborations or packages and stereotype the collaboration
or package. An alternative would be to stereotype the diagrams, but it
is not possible in UML 1.3. May be in UML 1.4. An alternative would be
a configuration based on diagrams. If we represent the same
collaboration with two alternative collaboration diagrams (two
possible solutions) we can configure the analysis for a specific
solution. If we stereotype the collaboration, what are we going to do?
do we include both diagrams with all its elements?