Re: UML diagram legend & glossary

[Farrukh Najmi - JavaSoft East <Farrukh.Najmi@East.Sun.COM>]

Joe,

This is an excellent suggestion. Since many specs may use UML notation I agree with you that the correct place to put
the information is in the glossary. Thanks for your participation in the f2f. Please send any other comments to the list

--

Regards,
Farrukh

"joebaran@extol.com" <joebaran@extol.com> wrote:
>Date: Fri, 05 Jan 2001 18:18:24 -0500
>
>To the RR team:
>
>In the Tokyo meeting, the RR team invited the QR team for a preliminary 
>review of the RR documents.
>
>One of the comments made at that time was that the use of UML diagrams 
>should be made more understandable for the benefit of those (such as 
>myself!) who have not exactly been immersed in UML.
>
>I understand that the use of UML in the specs is simply that of a 
>documentation convention, and I think it serves the purpose well. As I said 
>in Tokyo, sometimes a picture is really worth a thousand words. However, 
>some participants have continued to be concerned about the use of UML in 
>ebXML specs, even if only as a documentation method.
>
>As a minimum, a "legend" of diagram notation, and a glossary of 
>UML-specific terminology could go a long way towards resolving those 
>concerns.
>
>Attached below is my attempt at providing these. There is a small .gif 
>image showing the notational conventions used in a UML class diagram, and a 
>subset of the Glossary from the UML 1.3 spec. The editing of the Glossary 
>is simply my own (perhaps biased) attempt at shortening it, retaining the 
>terms which appear (at least to me) to be frequently used and/or frequently 
>misunderstood.
>
>Perhaps the inclusion of something such as these as an appendix would be 
>appropriate - or maybe they really belong in the overall ebXML Glossary. In 
>any case, they should (IMHO) be _somewhere_ in the ebXML documents if UML 
>notation is to be used in the ebXML documents.
>
>Joe Baran
>
>Attachments:
>
>"gif" of Class Diagram notation:
>
> 
>
>Excerpt from UML spec glossary (in RTF form):
>
> 
>Plain text copy (for the RTF-challenged):
>
> 
>
>
>
>
>