Figure 15-7: Example of flow allocation from ObjectNode to FlowProperty

Gallery
Tutorial
TRAIL: The SysML-1.6 Hybrid SUV sample and specification diagrams in MagicDraw/Cameo (with annotations) [UNDERGOING UPDATE to SysML1.7]
Section
Section: SysML-1.6 specification diagrams: 15 Allocations
UML keywords
ObjectFlow
Connector
callout
Action
Activity
SysML keywords
Allocate
behavior allocation
FlowProperty
Block
Keywords
Slide kind
hybrid diagram
SysML Activity Diagram
SysML Internal Block Diagram (IBD)
Click on the image to view it full size
In this trail version lower case names are used for the Actions action1 and action2 and the ObjectNode objectNode4:
Prefer anonymous Actions, or if they must be named, prefer code-like 'lowerCamelCase' or completely 'lower case' (if you do absolutely insist on having spaces in action names, but please no other punctuation).
SysML: Naming: Always use either anonymous or first letter lower case for Property, ObjectNode and InstanceSpecification names; no exceptions (unless using names to "quote text")! Valid: 'lowerCamelCase' OR 'tla' vs TLA acronym OR 'uCC' vs UpperCamelCase
There are multiple issues with the spec version of the figure:
SysML-1.6: The 'Figure 15-7: Example of flow allocation from ObjectNode to FlowProperty' does not allocate to any FlowProperty
SysML-1.6: The 'Figure 15-7: Example of flow allocation from ObjectNode to FlowProperty' does not show the allocatedFrom for 'action2' on Block7
SysML-1.6: In 'Figure 15-7: Example of flow allocation from ObjectNode to FlowProperty' it does not make sense naming the BDD 'Block0' if that Block is not shown in the diagram
Whether the following is an error is a matter of opinion:
SysML-1.6: In 'Figure 15-7: Example of flow allocation from ObjectNode to FlowProperty' there are allocations from an Actions (usage level) to Blocks (definition level)
But it is not Webel Best Practice:
AVOID "mixed" functional (behavioral) allocation levels! DO NOT Allocate from Usage level (Action) to Definition level (Block) or from Definition level (Activity) to usage level (part Property) - even if formally permitted in SysML.
There are also some tool issues:
MagicDraw/Cameo does not seem to offer the display option Apply SysML Callout Style on CentralBufferNode
The only reason that a CentralBufferNode is involved anyway is this problem:
MagicDraw/Cameo: ERROR: Incorrectly uses 2 ObjectFlow edges and a CentralBufferNode in place of "elided Pin notation" instead of an abstract ObjectNode symbol and 2 arrow symbols (that are supposed to represent together 2 Pins and 1 ObjectFlow edge)
A version of the Activity using explicit Pins is included in this trail version.

This trail version also includes the allocations from Activity1 to Block6 and Activity2 to Block7 that are not explicitly shown in the spec version.

Up next
Figure 15-8: Example of Structural Allocation
Notes
[ISSUE] SysML-1.6: The 'Figure 15-7: Example of flow allocation from ObjectNode to FlowProperty' does not allocate to any FlowProperty
[ISSUE] SysML-1.6: The 'Figure 15-7: Example of flow allocation from ObjectNode to FlowProperty' does not show the allocatedFrom for 'action2' on Block7
[ISSUE] SysML-1.6: In 'Figure 15-7: Example of flow allocation from ObjectNode to FlowProperty' it does not make sense naming the BDD 'Block0' if that Block is not shown in the diagram
[ISSUE, TOOL] MagicDraw/Cameo: ERROR: Incorrectly uses 2 ObjectFlow edges and a CentralBufferNode in place of "elided Pin notation" instead of an abstract ObjectNode symbol and 2 arrow symbols (that are supposed to represent together 2 Pins and 1 ObjectFlow edge)
[DISPLAY, ISSUE, TOOL, WARNING] Webel recommends when using MagicDraw/Cameo: AVOID the "elided Pin" abstract ObjectNode notation on Activity Diagrams, use explicit Pins!
[NAMING, POLICY, WARNING]{STRICT} DO NOT use Property names that are identical to the names of the Classifier (Class, DataType, Block, ValueType) that type them!
[NAMING, POLICY]{STRICT} SysML: Naming: Always use either anonymous or first letter lower case for Property, ObjectNode and InstanceSpecification names; no exceptions (unless using names to "quote text")! Valid: 'lowerCamelCase' OR 'tla' vs TLA acronym OR 'uCC' vs UpperCamelCase
[NAMING, POLICY]{STRONG} Prefer anonymous Actions, or if they must be named, prefer code-like 'lowerCamelCase' or completely 'lower case' (if you do absolutely insist on having spaces in action names, but please no other punctuation).
[CAVEAT, ISSUE, STYLE] MagicDraw/Cameo does not seem to offer the display option Apply SysML Callout Style on CentralBufferNode
[CAPABILITY, FEATURE, TOOL] MagicDraw/Cameo: Supports embedding of one or more Diagrams in another via the Diagram Overview feature. Awesome!
[ISSUE] SysML-1.6: In 'Figure 15-7: Example of flow allocation from ObjectNode to FlowProperty' there are allocations from an Actions (usage level) to Blocks (definition level)
[POLICY, WARNING]{STRICT} AVOID "mixed" functional (behavioral) allocation levels! DO NOT Allocate from Usage level (Action) to Definition level (Block) or from Definition level (Activity) to usage level (part Property) - even if formally permitted in SysML.
Snippets (quotes/extracts)
Visit also
Visit also (backlinks)
Related slides (includes other tutorials)
Related slides (backlinks, includes other tutorials)