-
Key: BACM-43
-
Status: closed
-
Source: Thematix Partners LLC ( Mr. James Rhyne)
-
Summary:
This paragraph states:
"In general, metamodel classes in the diagrams in this document will become meta-classes (class prototypes or templates) in an implementation. However, classes stereotyped as “association” will become associationclasses. These entities are binary or n-ary associations that can be specialized (from other meta-associationclasses), have features, and participate in other associations. UML binary associations with a <<class>> stereotype should be implemented as binary meta-associationclasses."
This description is unclear. It mentions association classes that are not part of MOF. It does not adequately describe how to interpret the stereotypes <<class>>, <<association>>, <<shortcut>> and <<individual>> -
Reported: BACM 1.0a1 — Thu, 17 Nov 2022 18:59 GMT
-
Disposition: Resolved — BACM 1.0b2
-
Disposition Summary:
Attached file replaces 7.2.1 para3 et seq
The description of the translation to MOF is completely rewritten and all paragraphs of section 7.2.1 starting with paragraph 3 are replaced by the attached Word document content.
-
Updated: Mon, 2 Oct 2023 12:55 GMT
-
Attachments:
- Section_7_2_1_para3_et_seq-proposal.docx 15 kB (application/vnd.openxmlformats-officedocument.wordprocessingml.document)
BACM — The 3rd paragraph of 7.2 is unclear
- Key: BACM-43
- OMG Task Force: Business Architecture Core Metamodel (BACM) 1.0 FTF