RE: (ROSE) Why only one stereotype per element

[Don Bate]

Title: RE: (ROSE) Why only one stereotype per element

Eric,

Please cite where in the UML 1.3 standard where it states that. I can't find any such restriction.

Regards,

Don Bate

At 9:27 AM -0700 4/9/01, Aker, Eric wrote:

Any one model element ( a specific class for instance ) can only have one stereotype.

Yes it is a UML restriction.

 

Eric

-----Original Message-----
From: Francois Toubol (Private Mail) [mailto:[EMAIL PROTECTED]]
Sent: Monday, April 09, 2001 8:45 AM
To: Alex Goeman; [EMAIL PROTECTED]
Subject: Re: (ROSE) Why only one stereotype per element

    There is no restriction regarding how many stereotypes can be associated with a model element in the UML specification.

    I dont know about Rose, but anyway if there is a limitation, this is not 1 only, since for e.g. Rose comes with various class stereotypes (eg. control, boundary, entity......).

    You can even assign a graphical representation to the stereotypes you defines (as specified by the UML spec.). If you want to do so, you can have a look at the REI section of the Rose help.

 

Regards,

Francois.

----- Original Message -----

From: Alex Goeman

To: [EMAIL PROTECTED]

Sent: Monday, April 09, 2001 10:15

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

--
Don Bate               | Specializing in Consulting and Mentoring in
Bate Consulting, Inc   | Object-Oriented Technologies,
                       | Software Architecture, and Software Process
(972) 618-0208 voice
(972) 618-0216 fax
[EMAIL PROTECTED]