UAF14 — View Specification - Am-Pr Architecture Development Method Name Doesn't Match Subject. Missing (No) Triples to Address Concerns

8.1.1 View Specification - Am-Pr Architecture Development Method is defined:

'Stakeholders: Enterprise Architects, Model Managers, Modelers, Enterprise Systems Engineers. Concerns: development sequence of models and views and how they are related to each other. Definition: defines workflow or process steps used in managing the architecture development. Recommended Implementation: SysML Activity Diagram, text.'

Figure 8.4 shows a single element - ArchitecturalDescription. No relationship elements. No architecture views,

1) The subject description of views, their sequence etc is not 'architecture' it's 'architecture description'. The view specification name is therefore not correct - the subject doesn't appear within the view specification name - it should be 'Architecture Description Method'
2) There are no elements / triples provided to describe the sequence of models, views and how they relate to each other hence Fig 8.4 does not provide the means to address the concerns. Presumably there should be at least the means to describe a trace. To describe a sequence of views you need something like 'View follows View'
3) Figure 8.4 only shows a single attribute for ArchitecturalDescription - see Figure 9:129. It ought also to include purpose, assumptionandConstraint etc (all of the ISO/IEC/IEEE 42010 required properties)
4) It suggests using a SysML Activity Diagram but provides no triples to describe Activities or their sequence.
5) If models and their sequence are expected you need to provide the means to describe them.
6) This view specification does so little that there seems to be little point in its existance - it would be easy to incorporate the concerns into another Am view specification.