Issue 9960: Association Names in UML Diagrams (sbvr-ftf) Source: Business Rules Group (Mr. John Hall, john.hall@modelsys.com johnhallms@hotmail.com) Nature: Uncategorized Issue Severity: Summary: Location: SBVR Annex H Issue: Is it legitimate in UML to have bidirectional association names with black triangles indicating direction, as in Figure H.4? Resolution: none proposed as yet - need to have the question answered first. Resolution: Revised Text: In clauses 8 through 12, the following sentence appears under numerous figures. This diagram is not normative abstract syntax for SBVR, but is for illustration only. Add "See Annex H." to the end of each occurrence so that it looks like this: This diagram is not normative abstract syntax for SBVR, but is for illustration only. See Annex H. On page 315 in the first paragraph of Annex H replace "Part II" with "clauses 8 through 12". Actions taken: July 24, 2006: received issue January 15, 2008: closed issue Discussion: Annex H describes a UML profile for Business Object Models in which sentential forms of fact types are shown using a notation similar to that of UML Associations. UML's profile capability allows for UML to be extended by reusing basic UML notations for new meanings and by adding new notations. The profile described in Annex H takes advantage of this extensibility. The verb phrases that appear in diagrams for a fact type are not names of an association. The arrows do not show an order of association ends, but rather show the direction of reading of the verb phrases with respect to the roles of the fact type. To make clear that the profile of Annex H is used in figures, the disclaimer under the figures is expanded with a reference to Annex H. A small change is made to the introduction to Annex H in order to clarify where the profile is being used. End of Annotations:===== te: Mon, 24 Jul 2006 22:19:35 +0100 From: John Hall Reply-To: john.hall@modelsys.com Organization: Model Systems User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) X-Accept-Language: en-us, en To: Juergen Boldt Subject: [SBVR] FTF issue Hi Juergen, If it's not too late, could I submit this as another issue? Cheers, John Issue Name: Association Names in UML Diagrams Location: SBVR Annex H Issue: Is it legitimate in UML to have bidirectional association names with black triangles indicating direction, as in Figure H.4? Resolution: none proposed as yet - need to have the question answered first. Subject: RE: issue 9960 -- SBVR FTF issue Date: Wed, 2 Aug 2006 10:06:39 -0700 X-MS-Has-Attach: yes X-MS-TNEF-Correlator: Thread-Topic: issue 9960 -- SBVR FTF issue thread-index: AcawFObfC6BppBzWRRyqD4TO6yzMiQGQORIQ From: "Baisley, Donald E" To: X-OriginalArrivalTime: 02 Aug 2006 17:06:40.0255 (UTC) FILETIME=[0582F8F0:01C6B656] See attached proposed resolution. Don Issue9960.doc Disposition: Resolved OMG Issue No: 9960 Title: Association Names in UML Diagrams Source: John Hall (john.hall@modelsys.com) Summary: Is it legitimate in UML to have bidirectional association names with black triangles indicating direction, as in Figure H.4? Resolution: Annex H describes a UML profile for Business Object Models in which sentential forms of fact types are shown using a notation similar to that of UML Associations. UML.s profile capability allows for UML to be extended by reusing basic UML notations for new meanings and by adding new notations. The profile described in Annex H takes advantage of this extensibility. The verb phrases that appear in diagrams for a fact type are not names of an association. The arrows do not show an order of association ends, but rather show the direction of reading of the verb phrases with respect to the roles of the fact type. To make clear that the profile of Annex H is used in figures, the disclaimer under the figures is expanded with a reference to Annex H. A small change is made to the introduction to Annex H in order to clarify where the profile is being used. Revised Text: In clauses 8 through 12, the following sentence appears under numerous figures. This diagram is not normative abstract syntax for SBVR, but is for illustration only. Add .See Annex H.. to the end of each occurrence so that it looks like this: This diagram is not normative abstract syntax for SBVR, but is for illustration only. See Annex H. On page 315 in the first paragraph of Annex H replace .Part II. with .clauses 8 through 12.. Disposition: Resolved