-
Key: UAF13-123
-
Status: open
-
Source: Eclectica Systems Ltd ( Nic Plum)
-
Summary:
In establishing a mapping there are 3 possible outcomes (gap analysis):
1) Target element is not linked to any UAF element
2) Target element is linked to a UAF element
3) UAF element is not linked to any target elementThe Traceability document only considers 2). This is inadequate. For example a statement is made concerning linkage to MODEM but this is only true up to the point where MODEM was released - UAF elements added which are not present in a 'donor AF' such as Requirement will not be linked to MODEM. Without a full list of all of the UAF elements its difficult to do a completeness check and to spot potential errors. It's important for an implementer to understand what might be in the UAF that isn't in a donor AF - particularly where the donor AF is no longer being maintained and over time therefore there will be more new-to-UAF elements.
-
Reported: UAF 1.2 — Thu, 4 Apr 2024 14:50 GMT
-
Updated: Thu, 4 Apr 2024 15:22 GMT
UAF13 — Appendix A. Traceability. Mapping Results Should Show Unmapped Elements - on UAF Side and on Target Side
- Key: UAF13-123
- OMG Task Force: Unified Architecture Framework (UAF) 1.3 RTF