Issue 5013: GRM Profile issue (uml-scheduling-ftf)
Source:  (, )
Nature: Uncategorized Issue
Severity: 
Summary: The profile some concepts as stereotypes when they are concepts that could be represented with other types of UML extensions, especially constraints. Some examples are GRMqosCharacteristic and GRMaccesControlPolicy. [1,4,8] use extensively constraint to represent these concepts, the represent the concepts like response times, and control policies as constraints. The problem is the formal language for the description of these concepts in the constraints, but we can use stereotyped constraints. This mean stereotypes for constraints, these stereotypes can include the tagged values that represent the constraint parameters and the constraint can represent the characteristic [3]. We can use the stereotype inheritance to represent the inheritance of these types of constraints.

Resolution: Closed, no change
Revised Text: 
Actions taken:
March 20, 2002: received issue
June 30, 2003: closed issue
Discussion: 
Resolve Morgan[2] and revisit.

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

GRM Profile issue

The profile some concepts as stereotypes when they are concepts that
could be represented with other types of UML extensions, especially
constraints. Some examples are GRMqosCharacteristic and
GRMaccesControlPolicy. [1,4,8] use extensively constraint to represent
these concepts, the represent the concepts like response times, and
control policies as constraints. The problem is the formal language
for the description of these concepts in the constraints, but we can
use stereotyped constraints. This mean stereotypes for constraints,
these stereotypes can include the tagged values that represent the
constraint parameters and the constraint can represent the
characteristic [3]. We can use the stereotype inheritance to represent
the inheritance of these types of constraints.