-
Key: UAF14-33
-
Status: open
-
Source: Eclectica Systems Ltd ( Nic Plum)
-
Summary:
'No new terms and definitions have been required to create this specification. All terms are available in the normative references or bibliographic citations for detailed explanation'
This is clearly untrue - there are terms, such as 'View Specification', which if distinct from Architecture Viewpoint needs to be defined to differentiate it.
As an authorative standard that claims to have semantic underpinnings this is wholly unacceptable - what is the master source to be used/referenced in an implementation? There is no traceability. From an engineering perspective any design implementation must be provided with the means to create full traceability to the UAF spec and, where appropriate, the particular source definition.
-
Reported: UAF 1.1 — Fri, 8 Apr 2022 10:07 GMT
-
Updated: Fri, 20 Dec 2024 14:57 GMT
UAF14 — Claim That No New Terms is Incorrect. Any Terms Need to Be Clearly Defined with Traceability to Source / Master Definition
- Key: UAF14-33
- OMG Task Force: Unified Architecture Framework (UAF) 1.4 RTF