-
Key: BACM-98
-
Status: closed
-
Source: Thematix Partners LLC ( Mr. James Rhyne)
-
Summary:
There are duplicate association names in the EA model. Because nearly all of these associations are stereotyped with <<class>> or <<shortcut>>, they are transformed into a class association pattern in MOF and duplicate names for classes are not allowed. The transformation program de-duplicates these names, but coherence is lost between the UML model of the specification (and the specification document generated from the UML model) and the generated MOF XMI.
-
Reported: BACM 1.0a1 — Thu, 27 Apr 2023 16:13 GMT
-
Disposition: Resolved — BACM 1.0b2
-
Disposition Summary:
Rename duplicate named association in the UML model
Rename the duplicate named associations by suffixing them with an underscore and a number. Add prose to section 7.2 of the document to describe the effective interpretation.
-
Updated: Mon, 2 Oct 2023 12:56 GMT
BACM — Eliminate duplicate association names in EA model
- Key: BACM-98
- OMG Task Force: Business Architecture Core Metamodel (BACM) 1.0 FTF