reflectometry

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 07: Model: Top-level UML2 composite structure diagram (systems engineering view) for the Platypus Reflectometer

Figure 07: Model: Top-level UML2 composite structure diagram (systems engineering view) for the Platypus Reflectometer

Connections from the bunker vacuum port and chopper control port to the boundary are not shown, and some other vacuum and control ports are omitted. The «proposal» and «design» Comments are elicited from the actual documents for the instrument.

Such "binding" of text to Unified Modeling Language™ (UML™) models has been formalised by Dr Darren as the UML™ Parsing Analysis recipe.
Syndicate content