UAF13 — Am-Mv Architecture Principles View Specification Doesn't Provide the Elements to Address the Concerns Identified. No Triples Defined.

View Specifications::Architecture Management::Motivation

Am-Mv Architecture Principles 'View Specification' p19, Figure 8:1

States: 'Concerns: alignment of architecture with architecture heuristics, guidelines, and principles.
Definition: identifies relevant architectural principles and other guidelines to be used in architecture development and evaluation.'

1) What does 'alignment of..' 'with' mean? Do you mean identification of the reference sources? Do you mean identification of input requirements? Do you mean conformance with requirements (process, technical etc)? The current is unspecific and will therefore yield inconsistent results. Should be 'alignment of architecture description' ('architecture description' not 'architecture')

2) Fig 8:1 only provides a 'Driver' element and possibly typed by DriverKind (this isn't clear because of the notation. Is this a normative value - if so this needs to be made clear. At the moment it looks like an error of ommission. ''Architecture Principle' should be 'Architecture Description Principle'.

3) Is the notation supposed to indicate that Driver has an attribute 'DriverKind' which has a set of enumerated values? Even in the UML you'd show an attribute on Driver and link this to the enumeration so this notation doesn't look to be complete. It could be interpreted as a form of specialisation of Driver

4) There are no means to describe the 'alignment of architecture (description) with architecture heuristics, guidelines, and principles' - no relationships provided, no target elements to link Driver to etc. As shown a compliant architecture view wouldn't even constitute architecture desctiption since it'd be pemissible to provide a single Driver element not linked to anything - an orphan or soliton - which isn't describing anything.

5) The multiplicity on DriverKind is incorrect - shows 0..1 which allows Driver to take an empty undefined value. This not only fails to address the architecture viewpoint concerns but is indeterminate. Should be '1'.

6) The enumeration shown for DriverKind and on Fig 9:138 has no default value specified.