Issue 14183: Need notation option to show type stereotype on typed element (uml2-rtf) Source: International Business Machines (Mr. Jim Amsden, jamsden(at)us.ibm.com) Nature: Uncategorized Issue Severity: Summary: A part (property, port, etc.) of a class is a TypedElement and can of course have applied stereotypes of its own. However, it is often useful to know not only the Type of a TypedElement, but how that type is stereotyped. This would provide more complete information about the type that helps communicate the meaning of the model. Some tools by default show the stereotypes of a type on parts typed by that type. For example, if Interface Purchasing is stereotyped as <<Provider>>, a port typed by that Interface might be displayed as <<Provider>>purchaser: Purchasing. But this is actually incorrect because it shows <<Provider>> extending a Port while the stereotype is defined to extend Inteface, not Property. UML2 should provide a notation option to allow Type stereotype names to be displayed in TypedElements. The example above could be more correctly shown as purchaser: <<Provider>> Purchasing - the stereotype for the interface is next to the interface, on the other side of the colon. If the Port is a <<Service>> port, then that would be shown as <<Service>>purchaser: <<Provider>>Purchasing. Resolution: Revised Text: Actions taken: August 6, 2009: received issue Discussion: End of Annotations:===== ubject: UML2 Issue: Need notation option to show type stereotype on typed element X-KeepSent: 50C8603A:4C2649A4-8525760A:006A1261; type=4; name=$KeepSent X-Mailer: Lotus Notes Build V851_07072009[dod_195462] July 16, 2009 From: Jim Amsden Date: Thu, 6 Aug 2009 15:32:58 -0400 X-MIMETrack: Serialize by Router on D03NM118/03/M/IBM(Build V851_07072009|July 07, 2009) at 08/06/2009 13:36:03, Serialize complete at 08/06/2009 13:36:03 A part (property, port, etc.) of a class is a TypedElement and can of course have applied stereotypes of its own. However, it is often useful to know not only the Type of a TypedElement, but how that type is stereotyped. This would provide more complete information about the type that helps communicate the meaning of the model. Some tools by default show the stereotypes of a type on parts typed by that type. For example, if Interface Purchasing is stereotyped as <>, a port typed by that Interface might be displayed as <>purchaser: Purchasing. But this is actually incorrect because it shows <> extending a Port while the stereotype is defined to extend Inteface, not Property. UML2 should provide a notation option to allow Type stereotype names to be displayed in TypedElements. The example above could be more correctly shown as purchaser: <> Purchasing - the stereotype for the interface is next to the interface, on the other side of the colon. If the Port is a <> port, then that would be shown as <>purchaser: <>Purchasing. Jim Amsden, Senior Technical Staff Member Rational Enterprise Architecture Management 919-461-3689 Subject: About 14183 Date: Thu, 20 Aug 2009 16:49:25 +0200 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: About 14183 thread-index: AcohpWkf3jzBQw1yR5yyJtLxNzR1xg== From: "BERNARD, Yves" To: X-OriginalArrivalTime: 20 Aug 2009 14:49:25.0460 (UTC) FILETIME=[695E7940:01CA21A5] X-MIME-Autoconverted: from quoted-printable to 8bit by amethyst.omg.org id n7KEiFoa014043 Jim, I think the issue you raised cannot be restricted to the management of stereotypes. It should include the identification of the meta-class corresponding to the type too. According to the exemple you give, it seems strange to me that those tools show the stereotype: <> (even if it would be on the "type name side" ) without the meta-class of which it is applied. Formaly, the notation should be something like: <>purchaser: <>Purchasing. The principle would apply also if there is no stereotype. For instance, if i define a block named "T1" and an interface named "T2", i can type a port (myPort) either by T1 or T2. The "complete" notation would be: myPort:T1 or myPort:T2 Yves The information in this e-mail is confidential. The contents may not be disclosed or used by anyone other than the addressee. Access to this e-mail by anyone else is unauthorised. If you are not the intended recipient, please notify Airbus immediately and delete this e-mail. Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately. All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you should take whatever measures you deem to be appropriate to ensure that this message and any attachments are virus free.