| Key | Issue | Reported | Fixed | Disposition | Status | |
|---|---|---|---|---|---|---|
| BACM11-3 | Entry- and Exit-Criteria missing | BACM 1.0b1 | open | |||
| BACM-38 | Entry- and Exit-Criteria missing | BACM 1.0b1 | BACM 1.0b2 | Deferred | closed | |
| BACM-89 | Entry- and Exit-Criteria missing | BACM 1.0b1 | BACM 1.0b2 | Duplicate or Merged | closed | |
| BACM-1 | Make changes to the spec to enable the production of MOF compliant XMI | BACM 1.0b1 | BACM 1.0b2 | Resolved | closed | |
| BACM-11 | Deliver MOF compliant XMI for specification | BACM 1.0b1 | BACM 1.0b2 | Resolved | closed |
Metamodel of Business Architecture Guild defines two relationships between Value Stream Stages and Value Item labeled as Entry Criteria and Exit Criteria. These relationships are missing in the BACM.
Metamodel of Business Architecture Guild defines two relationships between Value Stream Stages and Value Item labeled as Entry Criteria and Exit Criteria. These relationships are missing in the BACM.
Defer to Revision Task Force
These relationships did not appear in any version of the submission and constitute a material change to the beta specification. Recommend that this issue be deferred. Entry and exit criteria can also be determined by analysis of the outcomes of capabilities supporting the value stream stages and selecting specified outcomes to serve as entry and exit criteria. An architect following the BIZBoK Guide(tm) would be able to perform this analysis based on information in a BACM model.
Metamodel of Business Architecture Guild defines two relationships between Value Stream Stages and Value Item labeled as Entry Criteria and Exit Criteria. These relationship are missing in the BACM.
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
Replace 7.3.1.1
This proposal incorporates model changes to support the generation of MOF-compliant XMI by transforming the XMI generated from the source model according to the normative specifications in section 7.2. It also incorporates editing changes that were made in the BACM_Model package to remedy a failure to update the text associated with changes to the diagrams published in BACM 1.0b1 (dtc-22-06-01).
Because the diagrams and text of section 7.3 are generated from the UML model, the number of editing changes would be very large. Consequently this proposal replaces 7.3.1.1 in its entirety. These changes do not effect the remainder of the specification.
The XMI file exported from the EA model is not MOF compliant. It includes class-associations and a profile with stereotypes that effectively define cass associations. Additionally, the semantics of "shortcut" stereotypes on associations must be expressed in OCL.
A MOF-compliant XMI file is produced by a transformation program
A Python 3 program was written to input the exported EA XMI file, perform the transformations defined in section 7.2 of the beta specification, and output a MOF-compliant XMI file. This file has been subjected to automated and hand checks for correctness. It has also been analyzed by the OMG XMI compliance tester, producing some minor errors.
