Re: (ROSE) Why only one stereotype per element

[andre]

PLEASE,   DON�T SEND ME MESSAGES ANYMORE !!!!!!!!!!!!!!! ----- Original Message ----- From: Williams, Larry To: Aker, Eric ; 'Francois Toubol (Private Mail)' ; Alex Goeman ; [EMAIL PROTECTED] Sent: Monday, April 09, 2001 3:18 PM Subject: RE: (ROSE) Why only one stereotype per element Before this degrades into a 'yes it is' vs. 'no it is not' argument, here's the facts:   1) UML version 1.3 (and earlier) had the restriction that a model element can have at most one stereotype. 2) UML version 1.4 has removed this restriction.   Rose is not currently based on UML 1.4 (since that version has only recently been finalized), so Rose still has the restriction.   larry. -----Original Message----- From: Aker, Eric [mailto:[EMAIL PROTECTED]] Sent: Monday, April 09, 2001 12:28 PM To: 'Francois Toubol (Private Mail)'; Alex Goeman; [EMAIL PROTECTED] 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