UAF 1.3 RTF Avatar
  1. OMG Issue

UAF13 — 8.1.10 View Specifications::Standards::Traceability - Sd-Tr - Incorrect Concerns. No Triples Provided to Match Concerns. Unclear Whether Trace or Conformance

  • Key: UAF13-176
  • Status: open  
  • Source: Eclectica Systems Ltd ( Nic Plum)
  • Summary:

    p99 8.1.10 View Specifications::Standards::Traceability

    The concern for the 'UAF::view specification' is:-
    'Concerns: standards that need to be taken in account to ensure the interoperability of the implementation of architectural elements.'

    1) Why is a view needed to describe the standards affecting the interoperability of an architecture description?
    2) 'implementation of architectural elements' is meaningless - do mean the standards that affect the system of interest? Standards don't just affect implementation

    'Definition: shows the applicability of standards to specific elements in the architecture'

    3) Difficult to make sense of given the endemic conflation of 'architecture' to mean both 'architecture' and 'architecture description'. Standards apply to the system of interest. 'elements' is too much like 'architecture description element' used to form an AD.

    Figure 8:82 Standards Traceability

    This shows Standard, Protocol elements and the generic UAFElement.

    4) There are no relationship elements provided to establish what looks like a 'conforms to' relationship between a UAFElement and a Standard or Protocol

    5) Either the diagram doesn't provide the elements to address the concerns or the concerns are incorrect. The diagram describes conformance not a trace ('standards that need to be taken in account'). Which is it? The concerns and the triples shown in the diagram need to be consistent with each other.

  • Reported: UAF 1.2 — Wed, 24 Apr 2024 08:56 GMT
  • Updated: Wed, 24 Apr 2024 14:07 GMT