UML composite structure diagram

*Application_Tiered_typical

*Application_Tiered_typical

Before moving on to more detail, let's see how the model is converging so far, by examining a composite structure diagram from on analysis Class, which shows the flow of some of the information implied by the source text descriptions, modelled using port-based engineering.

We can also bring some of the information from existing source text «wrapper» Components into the diagram as instance-like Properties typed by the wrappers, which does show the text nicely, and with a little effort we can relate it to the analysis Properties with Dependencies, however this is in fact repeating work already done elsewhere in more automated fashion, and it also pollutes the Property space of the analysis element.

Figure 08: Model: Bunker shield assembly for the the Platypus reflectometer as UML2 composite structure diagram with flowport notation.

Figure 08: Model: Bunker shield assembly for the the Platypus reflectometer as UML2 composite structure diagram with flowport notation.

The «block» class is wrapped by a block «wrapper» Component that is hyperlinked to a block wrapper class diagram for the block. Other «block» classes are shown to provide a usage context and alternative navigation points1. Physical values (part-specific defaults) are not easily shown on the parts2. The limits of the port-based modelling and assembly interpretations are challenged by a postbunker guide that is part inside and part outside the bunker.

  • 1. Since 2008 MagicDraw UML supports easier navigation to clients of a Class in a Composite Structure Diagram, so there is less need for this strategy now. Note also that it is not always wise to indicate the usage context explicitly, it can prevent modularisation !
  • 2. Since 2008 MagicDraw UML supports SysML-style property-specific value indicators on UML Property symbols in composite structure diagrams

Figure 05: Example: UML2 composite structure diagram (systems engineering view) of a fictitious neutron beam conditioning bunker.

Figure 05: Example: UML2 composite structure diagram (systems engineering view) of a fictitious neutron beam conditioning bunker.

Shows the “anatomy” of neutron beam instrument assembly blocks with parts, custom UML2 notation for neutron and air flowports, and control ports.

UML: TIP: put the class diagram symbol on the composite structure diagram and the composite structure diagram symbol on the class diagram for easy navigation between related "views".

Applies to those UML tools with support for diagram icons hyperlinked to diagrams.

MOST: UML: Reflector

MOST: UML: Reflector

A parabolic trough with wire mesh.

A simplified representation of a triaxial accelerometer (vector acceleration sensor)

A simplified representation of a triaxial accelerometer (vector acceleration sensor)

I have actually combined here two related diagrams in a composite component hierarchy, which is a useful trick when one is designing everything in one large design diagram. Within the structure compartment of each component I have BOTH an "implementation diagram" of component classifiers AND the component parts network .

  • The subcomponent "implementation diagram" with component classifiers defines the ports (and also optionally the possible connections between components). The ports are NOT connected (exported to) the boundary ports.
  • The component part network (structure diagram) defines the actual network that each outer component contains, and input/output/parameter ports are exported to the outer component boundary.
Syndicate content
randomness