Figure 15-6: Example of flow allocation from ObjectFlow to ItemFlow

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
SysML keywords
Allocate
behavior allocation
ItemFlow
Keywords
Slide kind
hybrid diagram
SysML Activity Diagram
SysML Internal Block Diagram (IBD)
Click on the image to view it full size
The spec version of this diagram causes confusion because it has a part Block5:Block5 (compare with Figure 15-6). Prefer Webel Best Practice!
DO NOT use Property names that are identical to the names of the Classifier (Class, DataType, Block, ValueType) that type them!
In this trail version lower case names are used for the part Properties part6, part7, block5, the Actions action1 and action2, the ObjectFlow objectFlow3, and for the Connector connector8:
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
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).
There are tool issues:
MagicDraw/Cameo: 19SP3: Callout of allocatedFrom on Connector vs ObjectFlow shows «decisionInputFlow» not «objectFlow» keyword
MagicDraw/Cameo 19SP3: Can't callout from ItemFlow on Connector, the Note handle pulls from the Connector not the ItemFlow
Up next
Figure 15-7: Example of flow allocation from ObjectNode to FlowProperty
Notes
[ISSUE, TOOL] MagicDraw/Cameo: 19SP3: Callout of allocatedFrom on Connector vs ObjectFlow shows «decisionInputFlow» not «objectFlow» keyword
[ISSUE, TOOL] MagicDraw/Cameo 19SP3: Can't callout from ItemFlow on Connector, the Note handle pulls from the Connector not the ItemFlow
[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!
[CAPABILITY, FEATURE, TOOL] MagicDraw/Cameo: Supports embedding of one or more Diagrams in another via the Diagram Overview feature. Awesome!
[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).
Snippets (quotes/extracts)
  [SysML-1.6] Allocation of ControlFlow is not shown as an example, but it is not prohibited in SysML.
Visit also
Visit also (backlinks)
Related slides (includes other tutorials)
Related slides (backlinks, includes other tutorials)