UAF14 — 8.1.4 View Specifications::Operational::Sequences::Operational Sequences View Specification Doesn't Provide Any Sequencing Triples to Address Its Concerns

View Specifications::Operational::Sequences::Operational Sequences View Specification:

'Concerns: express a time ordered examination of the operational exchanges as a result of a particular operational scenario.

Definition: provides a time-ordered examination of the operational exchanges between participating nodes (OperationalPerformer roles) as a result of a particular operational scenario'

1) Figure 8:29 includes no triples to define the order of exchanges of operational messages. Even the incorrectly included UML Lifeline does not define an order - it is inferred by visual presentation reading from, say, top to bottom or annotating with a sequence number. There are no formal semantics that define the order of a sequence. In any case the UML shouldn't be in this document - it is a specific implementation. The missing part in this view specification is something that semantically describes order or=f exchanges (which the UML etc is then able to implement) i.e. something like' OperationalExchange follows OperationalExchange'

2) The concern isn't 'time-ordered examination' - it is something like 'in what order ....'

3) The definition should be phrased in terms of real world things not the metamodel representing the real world. It might include the application of the viewpoint to real world situations. Simply describing the metamodel provides no utility.