Platypus Reflectometer

Figure 15: Simplified SysML version of the Platypus neutron reflectometer model.

Figure 15: Simplified SysML version of the Platypus neutron reflectometer model.

With SysML flowport notation for neutron beam and air flows, control ports in UML2 notation, rich values with physical units, and part-specific default values assigned according to the usage context. MagicDraw™ UML's SysML1.1beta plugin was used.

ERROR: it is known that (at least) some of the details of the vacuum systems are wrong.

Figure 14: SWT TableTree ModelClient showing an instance of the Platypus reflectometer model.

Figure 14: SWT TableTree ModelClient showing an instance of the Platypus reflectometer model.

Note Systems Modeling Language™ (SysML™)-like node groups: attributes, values, parts, ports. (Controlled values are not synched here with the live control system.)

Figure 09: Model: bunker shield assembly for the Platypus reflectometer as "wrapped block" class diagram.

Figure 09: Model: bunker shield assembly for the Platypus reflectometer as "wrapped block" class diagram.

Many of the parts are used only once; their blocks are specifically designed for this one-off application, and so they do not require «part wrapper» Components, and their block «wrapper» Components are contained by their unique block wrappers. Other parts are typed by reusable generic blocks, and so they are given specific «part wrapper» Components.

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
randomness