System Views (SV) [Physical, Specification or Solution Views]

Introduction to SV-10a, SV-10b and SV-10c v1.2

Many of the critical characteristics of an Architecture are only discovered when an Architecture’s dynamic behaviours are defined and described. These dynamic behaviours concern the timing and sequencing of events that capture resource performance characteristics (i.e. a resource performing the functions described in SV-4).

Behavioural modelling and documentation are key to a successful Architecture description, because it is how the Architecture behaves that is crucial in many situations. Although knowledge of the functions and interfaces is also crucial, knowing whether, for example, a response should be expected after sending message X to Resource Y can be crucial to successful overall operations.

Three types of models may be used to adequately describe the dynamic behaviour and performance characteristics of a SV. These three models are:

• Resource Rules Model (SV-10a)
• Resource State Transition Description (SV-10b)
• Resource Event-Trace Description (SV-10c)

SV-10b and SV-10c may be used separately or together, as necessary, to describe critical timing and sequencing behaviour in the SV. Both types of diagrams are used by a wide variety of different systems methodologies.

Both SV-10b and SV-10c describe resources’ responses to sequences of events. Events may also be referred to as inputs, transactions, or triggers. When an event occurs, the action to be taken may be subject to a rule or set of rules as described in SV-10a.

Page version 1.2, dated 1st July 2008