-
Key: UAF13-135
-
Status: open
-
Source: Eclectica Systems Ltd ( Nic Plum)
-
Summary:
1.1 item 5 states 'The approach defined in this Guide is just one way to approach architectures when using UAF' which should be 'The approach defined in this Guide is just one way to approach architecture description when using UAF'
The use of 'architecture' to sometimes refer to 'architecture' and sometimes refer to its description ('architecture description') is a perniscious problem in the UAF. It might be acceptable in casual conversation but technically the terms from 42010 should be used correctly. This is particularly the case since the DMM states that 'The UAF conforms to terms defined in the ISO/IEC/IEEE 42010 standard for architecture description' - it doesn't. See also 'view specification' which is an undefined and unnecessary concept.
1.2 we have 'UAF extends the scope of UPDM and generalizes it to make it applicable to commercial as well as military architectures' which should also be 'architecture description' not 'architectures'
-
Reported: UAF 1.2 — Thu, 11 Apr 2024 14:39 GMT
-
Updated: Fri, 12 Apr 2024 19:26 GMT
UAF13 — 1.1 Introduction, 1.2 UAF Background Incorrectly Uses 'Architecture', 'Architectures' to Refer to Architecture Description
- Key: UAF13-135
- OMG Task Force: Unified Architecture Framework (UAF) 1.3 RTF