This trail version of the figure instead assumes that AbstractReference and ConcreteExample are Blocks (re-named with no spaces in accordance to Webel Best Practice) and uses a Package Diagram.

Up next

Figure 15-9: Allocation Matrix showing Allocation for Hybrid SUV Accelerate Example

Notes

[ISSUE] SysML-1.6: The spec 'Figure 15-8: Example of Structural Allocation' has an IBD for Block1, which only makes sense if 'Abstract Reference' and 'Concrete Example' are meant to be part Properties (not Blocks)

[NAMING, POLICY]{STRICT} DO NOT use spaces in Property names or Class/Block names! If you want to communicate familiar names of elements within an organisation use a custom stereotype and tagged values (such as 'aka')!

Snippets (quotes/extracts)

[SysML-1.6] Systems engineers have frequent need to allocate structural model elements (e.g., blocks, parts, or connectors) to other structural elements.

[SysML-1.6] For example, if a particular user model includes an abstract logical structure, it may be important to show how these model elements are allocated to a more concrete physical structure.

[SysML-1.6] The need also arises, when adding detail to a structural model, to allocate a connector (at a more abstract level) to a part (at a more concrete level).

Related slides (includes other tutorials)

Related slides (backlinks, includes other tutorials)

Structural Allocation: USB - Progressive refinement using Allocations

Visit also

Visit also (backlinks)

Webel: SysMLv1: TIP: Consider using high level "communication" Associations between Blocks in BDDs with ItemFlows and corresponding context IBDs WITHOUT any Ports, with Connectors typed by the Associations (as well, in parallel with your port-based IBDs).

Flags