UAF13 — Consistency/Lack of Standardisation - 'stakeholder viewpoint', vs MODAF::viewpoint vs ISO 42010 Architecture Viewpoint

The UAF is supposed to be a technical standard. The effectiveness of standardisation requires the use of the correct standard terms consistently. ISO/IEC/EEEE 42010 provides the correct terms needed for architecture description - both their names and the meanings - but the UAF mixes and matches terms, changes their names and intoroduces its own non-standard new ones. The use of 'viewpoint' is inconsistent and incorrect and there is nothing provided to the reader so that they can understand the different meanings of the same term. This wouldn't be a problem if the UAF used the term 'architecture viewpoint' (not 'viewpoint') as defined by ISO/IEC/IEEE 42010 for the meaning defined by the ISO.

The abstract states:
'The nine steps of the workflow are laid out in alignment with the stakeholder viewpoints in UAF for producing the requisite architecture views in each of those viewpoints'

1) 'stakeholder viewpoints' should be 'architecture viewpoints' (viewpoints and views do not record something when "viewed from a particular direction"). The problem here, though is that these 'stakeholder viewpoints' are incorrectly termed 'view specifications' both in the UAF grid and the DMM package structure.

2) 'architecture views in each of those viewpoints' - an architecture viewpoint is a specification for an architecture view not a containing mechanism - this use of 'viewpoint' is actually MODAF::viewpoint - a different thing and undefined

3) wherever 'view' appears it should correctly be 'architecture view' in accordance with ISO/IEC/IEEE 42010 so that that the meaning is uambiguously tied to the ISO concept not the various casual uses of the term.