Issue 5078: concepts that already exists in UML (uml-scheduling-ftf)
Source: Commissariat a l Energie Atomique-CEA (Dr. Sebastien Gerard, sebastien.gerard(at)cea.fr)
Nature: Uncategorized Issue
Severity: 
Summary: We think it is not possible to forget some concepts that already exists in UML and that are very closed to some of the previous one. More precisely I think about three following issues:
1.       The isActive meta-attribute of the Class meta-class è Active/passive object which are particular case of active/passive resource; So, according to me they are specialization of the stereotype <<GRMactiveRessource>>.
2.       The concurrency meta-attribute of the Operation meta-class which is a kind of concurrency policy on operations;
3.       The isQuery meta-Attribute of BehavioralFeature may be connected to the Service concept.
4.       Both stereotypes <<Thread>> and <<Process>> of the Classifier meta-class I deem that they are outside the scope of UML core and could be placed in the RT profile. There are indeed specialization of the stereotype <<GRMactiveResource>>.
To conclude, we think that the links between this profile and UML meta-model is not so simple. Today we have no precise solution. One way to proceed could be to remove from UML all concepts pertaining to concurrency and put them in the concurrency profile for UML è to remove isActive, concurrency and isQuery meta-attributes and <<Thread>> , <<Process>>  stereotypes;

Resolution: 
Revised Text: 
Actions taken:
March 20, 2002: received issue
Discussion: 
We should at least map the concepts over.

End of Annotations:=====
This is issue # 5078
 to remove isActive, concurrency and isQuery meta-attributes and
 <<Thread>> , <<Process>>  stereotypes;
concepts that already exists in UML
 Active/passive object which are particular case of active/passive
 resource; So, according to me they are specialization of the
 stereotype <<GRMactiveRessource>>.
2.       The concurrency meta-attribute of the Operation meta-class
 which is a kind of concurrency policy on operations;
3.       The isQuery meta-Attribute of BehavioralFeature may be
 connected to the Service concept.
4.       Both stereotypes <<Thread>> and <<Process>> of the Classifier
 meta-class I deem that they are outside the scope of UML core and
 could be placed in the RT profile. There are indeed specialization of
 the stereotype <<GRMactiveResource>>.
To conclude, we think that the links between this profile and UML
 meta-model is not so simple. Today we have no precise solution. One
 way to proceed could be to remove from UML all concepts pertaining to
 concurrency and put them in the concurrency profile for UML 
We think it is not possible to forget some concepts that already
exists in UML and that are very closed to some of the previous
one. More precisely I think about three following issues:
1.       The isActive meta-attribute of the Class meta-class