The system view shows a graphical representation of the structure of the defined system and sub-system(s).
It shows the system’s ports, its sub-components and their ports, and all bindings between ports.
Initially the most complex (containing the most components) and outermost system is shown under System View in the Design perspective.
Clicking on a system boundary, component or port highlights the place in the model editor where the respective element is instantiated.
Ctrl-Click on a component shows the definition of the component.
Clicking on the (+) on the top left of a system will expand a system and show it’s internal structure. The internals can be hidden again by clicking on the (-) on the top left of an expanded system.
Double-clicking a sub-system component will cause the viewer to jump to the corresponding view. This can be repeated for deeper nested systems.
Click the arrow pointing to the left in the top right on the system view window ("Show previous diagram") to go back to the previous diagram.
Click on the folder icon in the top right on the system view window to show all systems which contain an instance of the current top level system component.
Click on the drop down list in the top right on the system view window to get a list of all (system) components in the file and select one to show.
A system component and each of its sub components is represented as a box. The required interface ports are depicted at the top, the provided interface ports at the bottom:
The internal structure of sub-components can be shown by clicking on the + button and hidden again by clicking on the - button.
Each component shows in text its name (i.e. its component name, not its instance name). Bindings are drawn as lines connecting the appropriate ports.
Take the AlarmSystem as an example:
provides Console console;
console <=> alarm.console;
alarm.sensor <=> sensor.sensor;
alarm.siren <=> siren.siren;
For this system the following view is generated
The sub components are coloured according to their "size", which denotes their compositional complexity, and is defined as follows:
A behavioural (non-system) component has size 1.
A system component with n sub components sized s1, …, sn has size 1+s1+…+sn.
The colours range from green to red where the size is taken as indicator:
The following (somewhat artificial) example shows a TOP system with three sub systems sized 6, 8, and 72 respectively.
For improved visibility and readability, the layout of the diagram can be changed by dragging components and dependency lines: