1. OMG Mailing List
  2. Business Architecture Core Metamodel 1.0 Finalization Task Force

Open Issues

  • Issues not resolved
  • Name: bacm-ftf
  • Issues Count: 5

Issues Descriptions

Dispose of the content from Annex B

  • Key: BACM-9
  • Status: open  
  • Source: Thematix Partners LLC ( James Rhyne)
  • Summary:

    This issue depends on acceptance of the proposal BACM_5 to remove Annex B from the specification document. It seeks proposals to dispose of this content.

  • Reported: BACM 1.0a1 — Wed, 22 Jun 2022 17:00 GMT
  • Updated: Wed, 22 Jun 2022 17:00 GMT

Remove Section 9 and republish as a separate, informative adjunct document

  • Key: BACM-6
  • Status: open  
  • Source: Thematix Partners LLC ( James Rhyne)
  • Summary:

    Section 9 consisted of responses to RFP requirements to address alignment with other OMG specifications. This information should probably have been placed in Section 0 of the submission and be deleted prior to publication as a beta specification. Moreover, the information in this section is informative and is expected to evolve rapidly as the BACM specification is used by architects. Consequently, the recommended action is to delete Section 9 and republish it as an informative adjunct to the normative specification.

  • Reported: BACM 1.0a1 — Tue, 21 Jun 2022 20:08 GMT
  • Updated: Tue, 21 Jun 2022 20:08 GMT

Remove Annex B from the specification document

  • Key: BACM-5
  • Status: open  
  • Source: Thematix Partners LLC ( James Rhyne)
  • Summary:

    The first part of Annex B (B1) is irrelevant given the changes made to the implementation of the <<shortcut>> stereotype in both the model and the MOF-compliant XMI. These changes were approved by the Architecture Board and accepted by the DTC. But the required changes to the specification were not made prior to publication.
    The second part of Annex B (B2) while technically correct, does not match the model shown in the diagrams. It is planned that this part will be rewritten and submitted as an informative document associated with the specification.
    The recommendation is to remove Annex B in its entirety

  • Reported: BACM 1.0a1 — Tue, 21 Jun 2022 19:58 GMT
  • Updated: Tue, 21 Jun 2022 19:58 GMT

Replace diagram 7.3.1.1.3 and following text

  • Key: BACM-2
  • Status: open  
  • Source: Thematix Partners LLC ( James Rhyne)
  • Summary:

    During the AB approval process, the BACM_Model package diagram was changed to eliminate imports of the other packages. The submitters failed to include these changes in the final document that was sent to the OMG publications team for re-publication as dtc-22-06-01.

  • Reported: BACM 1.0a1 — Tue, 21 Jun 2022 16:46 GMT
  • Updated: Tue, 21 Jun 2022 16:49 GMT
  • Attachments:

Make changes to the spec to enable the production of MOF compliant XMI

  • Key: BACM-1
  • Status: open  
  • Source: Thematix Partners LLC ( James Rhyne)
  • Summary:

    As a condition of acceptance by the Architecture Board, the FTF is required to produce a MOF compliant XMI file. MOF does not allow profiles or association classes. To allow a faithful translation of the EA model, some new classes were introduced that translate stereotyped associations into a pattern of a class and two associations. To facilitate this, some new classes were added to the BusinessElement diagram and some redundant classes and generalizations were removed. Prose explanations should be added following the new BusinessElement diagram

  • Reported: BACM 1.0b1 — Mon, 20 Jun 2022 22:17 GMT
  • Updated: Mon, 20 Jun 2022 22:17 GMT
  • Attachments: