-
Key: UAF13-112
-
Status: open
-
Source: Eclectica Systems Ltd ( Nic Plum)
-
Summary:
3.1 lists Normative References, 3.1.1 lists normative OMG references. Non-OMG normative references should still be part of 3.1 and hence should be 3.1.2 not 3.2
There is also a problem in the wholesale application of normative references to any part of the UAF. The DMM is supposed to be implementation-agnostic and therefore ADL references should not be normative for that. Similarly the only place where MODEM and DODAF etc are referenced are in the Traceability document (perhaps the UAFML?) so they are not normative for the DMM itself - particularly as there are elements in the DMM that are not in the MODEM, or DODAF or MODAF [this is also a problem within the Traceability document - it isn't complete].
It would make sense to qualify the scope of the normative references by splitting into sub-sections e.g. general (common to all), DMM, UAFML, Traceability - if you're going to place all of the references in the one place. Alternatively add a References section to each sub-document and only state the normative references that apply to the document being read.
-
Reported: UAF 1.2b1 — Thu, 4 Apr 2024 12:45 GMT
-
Updated: Thu, 4 Apr 2024 15:13 GMT
UAF13 — Structure of References Section is Incorrect wrt Normative Docs. It also Needs to Identify Which Normative Documents Apply to What Parts of the UAF
- Key: UAF13-112
- OMG Task Force: Unified Architecture Framework (UAF) 1.3 RTF