-
Key: BACM11-75
-
Status: closed
-
Source: Thematix Partners LLC ( Mr. James Rhyne)
-
Summary:
The text of incorporates_3 states that it "refines the incorporates_0 association". However, there is no syntactic indication of this and no tagged value. Consequently, the generalization assertion that should appear in both the MOF and the OWL is missing. This is also the case for incorporates_4 in the OutsourcedServiceOffering diagram.
-
Reported: BACM 1.0b2 — Thu, 22 Aug 2024 18:30 GMT
-
Disposition: Resolved — BACM 1.1b1
-
Disposition Summary:
Add code to BACM2MOF.py to fix the generated XMI
A <<class>> association may specialize another <<class> association by redefining the ownedEnds of the specialized association to reference the ownedEnds of the generalizing association. However, both associations are transformed to a class with the same name and a "from" association and a "to" association. After this transformation, the class generated for the specializing association needs to specialize the class generated for the generalizing association. Additionally, the "from" association needs to specialize the generalizing "from" association, and the "to" association needs to specialize the generalizing "to" association. The change is to be added to BACM2MOF.py, the program that converts the EA generated XMI file into a MOF XMI file.
-
Updated: Mon, 24 Mar 2025 13:38 GMT
-
Attachments:
- OutsourcedServiceOffering_20240822.png 56 kB (image/png)
- ServiceOffering_20240822.png 33 kB (image/png)
BACM11 — No specialization of incorporates_3 from incorporates_0 in MOF or OWL
- Key: BACM11-75
- OMG Task Force: Business Architecture Core Metamodel (BACM) 1.1 RTF