RE: (ROSE) Why only one stereotype per element

[Brian G. Lyons]

hiho,   "Any model element can have at most one stereotype.  This rule may not be logically essential, but it simplifies the semantics of the notation for stereotypes without any real loss in power, as multiple inheritance of stereotypes themselves is permitted.  Stereotypes can be children of other stereotypes" [ Unified Modeling Language Reference Manual by Rumbaugh et al, p450]   So Rose is valid in only supporting one stereotype.  Rose is not valid in that it cannot provide stereotype inheritance.  Now, I suppose you could make a generalization hierarchy of classes stereotyped as <<stereotype>> and then use those class names as your stereotypes.   I mostly see people requesting more than one stereotype when they are using stereotypes where tagged values (properties in Rose) should be used.  In fact, it kills me to see the Visual C++ code generator for Rose use <<Abstract>> as a stereotype on an operation.  What if I wanted to use <<selector>> and <<modifier>> as stereotypes for operations?                      ------- b -- Brian G. Lyons Number Six Software - Voted Rational's Best Complementary Service Provider 1655 North Fort Myer Drive, Suite 1100 Arlington, VA 22209-3196 http://www.numbersix.com -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Alex Goeman Sent: Monday, April 09, 2001 10:15 AM To: [EMAIL PROTECTED] Subject: (ROSE) Why only one stereotype per element Why can there be only one stereotype assigned to a model element ? Is this a design restriction from the rational software ? I though that multiple stereotypes were possible using UML so what is the motivation for restricting it.     Greetings, Alex Goeman