Context diagram

Description

The context diagram is designed to break down components only where useful. We find this useful to get a 'top-down' functional impression of a system, with the option to generate diagrams that successively 'open the lid' on components, whilst keeping others 'boxed up'.

Definition

A context diagram shows the context of the specified element, with respect to a particular scope element.

The view contains:

  1. Main elements of interest
  2. Relevant associated elements.

Main elements of interest

The main elements of interest are those that are children of the scoping element. Or, if the scoping element has no children, the scoping element itself.

Relevant associated elements

A relevant associated element is one that is associated to one of the main elements of interest, where either:

  • Its immediate parent is an ancestor of the scope
  • It is a root element.

Example: entire system

The simplest 'context' is one with the scope of the entire system. All the 'top level' elements have been added (children of the world scope!).

arch 0xc000207c50 app 0xc000207230 sound-system 0xc000207c50->0xc000207230 control 0xc000207200 user 0xc000207230->0xc000207200 sound 0xc000207200->0xc000207c50 0xc000207200->0xc000207230 press

Example: sub-item

If we change the scope to a sub-item, in this case sound-system, we see that it is opened up and it's two children, amplifier and speaker are revealed.

The only connections that are shown are those that connect directly to these children.

arch cluster_0xc00038b2c0 sound-system 0xc00038bc80 app 0xc00038b710 amplifier 0xc00038bc80->0xc00038b710 control 0xc00038b380 speaker 0xc00038b710->0xc00038b380 0xc00038b290 user 0xc00038b380->0xc00038b290 sound 0xc00038b290->0xc00038b710 press