Re: (ROSE) Why only one stereotype per element

[Francois Toubol \(Private Mail\)]

Right, I missunderstood, really, I was speaking about metamodel element, not model element. You're right, I was wrong. ----- Original Message ----- From: Aker, Eric To: 'Francois Toubol (Private Mail)' ; Alex Goeman ; [EMAIL PROTECTED] Sent: Monday, April 09, 2001 12:27 Subject: RE: (ROSE) Why only one stereotype per element 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