UAF14 — View Specification - Rs-Sr - Undefined Concerns, Missing Elements, Shouldn't Describe Function, Missing Triples - Measurement, Protocol

p74 8.1.7 View Specifications::Resources::Structure

1) identifier - Rs-Sr, missing'

Definition: defines the physical resources, e.g. capability configuration(s)/system(s) and interactions necessary to implement a specific set of OperationalPerformer(s).'

2) CapabilityConfiguration and System are not physical resources (as Figure 8:56 shows)

3) ResourceArchitecture specialised elements - System, SecurityEnclave allowed but missing from Fig 8:56. All elements of a taxonomy tree should be shown. If not then the parent should not be shown and particular individual child elements shown.

'Concerns: reference the resource structure, connectors and interfaces in a specific context.'
4) Meaningless - what does 'reference the ...' mean? 'In a specific context'? Back inAbitraryConnector territroy. How can you possibly determine that these elements represent the allowed view content when there is no clear set of concerns which triples formed from the elements should address?

5) Is nothing carried by a ResourceExchange? If so elements are needed on Fig 8:56 to describe this.

6) Protocol is not involved in any triple. There appears to be a triple involving ProtocolImplementation but not Protocol. If there is a triple involving Protocol expected then additional elements are required. If there is no triple involving Protocol delete it.

7) Similarly there is no triple involving Measurement - again define one including a relationship element or remove.

8) The 'ResourcePerformer IsCapableToPerform Function' triple has no connection to the structural and interface concerns. It makes no sense to try and describe functional, interfaces and structure on the one architecture view. Function should be the subject of e behaviour-oriented 'view specification' e.g. Resources Process - Rs-Pr. The IsCapableToPerform and Function elements should be remoed from Fig 8:56