-
Key: UAF14-159
-
Status: open
-
Source: Eclectica Systems Ltd ( Nic Plum)
-
Summary:
Figure 8:10 - Architecture Traceability.
The (Am-Tr) Architecture Traceability view specification has a number of problems:-
1) Figure 8-10 only allows one relationship (in green) - ...Architecture implements ...Phase - what is this supposed to mean - there is no direction ? How does this address the understanding of 'the impact of change'?
2) Under stakeholders - 'people who want to understand impact of change across the architecture supporting assets,' is a concern not a role
3) Under concerns - 'reuse of architectures' - given the widespread conflation of 'architecture' and 'architecture description' does 'architecture' here mean 'architecture'?
4) ArchitecturalDescription is show yet there is no allowed relationship with it. As it does not contribute any tripes that are allowed it should not be shown in the Figure
5) Under definition we have 'shows references to ... external sources, e.g. documents'. There are no relationships or artefact elements shown to enable these references to be described
6) Typo on role on Architecture - 'realizingArchitedcture' -
Reported: UAF 1.2 — Tue, 16 Apr 2024 08:24 GMT
-
Updated: Fri, 20 Dec 2024 14:57 GMT
UAF14 — View Specification Am-Tr Architecture Traceability - Only 1 Relationship Element Provided, Unable to Describe Traces to External Sources
- Key: UAF14-159
- OMG Task Force: Unified Architecture Framework (UAF) 1.4 RTF