Functional allocation of a CallBehaviorAction (usage level) in an Activity Diagram to elements in a BDD

Gallery
Tutorial
TRAIL: Webel's ultimate guide to Systems Modeling Language (v1) with MagicDraw/Cameo
Section
15:01: The Allocate relationship and functional analysis
Topic level
ESSENTIAL
UML keywords
Activity
Behavior
CallBehaviorAction
SysML keywords
«activity»
Block
part property
MD:PartProperty
behavior allocation
Keywords
Slide kind
hybrid diagram
SysML Activity Diagram
SysML Block Definition Diagram (BDD)

The slide shows some possible CallBehaviorAction allocations, the "classic" functional (behavioral) allocation using Action in SysML.

Not all of these kinds of possible (allowed) allocations shown here are recommended!
Click on the image to view it full size

The allocation from CallBehaviorAction allocateMeToPart (of type BasicActivity) to part Property part of type SubBlock - both at usage level - is a recommended allocation strategy.

The allocation from the usage level CallBehaviorAction allocateMeToBlock (of type BasicActivity) to Block at definition level is definitely not recommended:

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.
The allocations here have in fact been done using this sneaky tool feature:
MagicDraw/Cameo: You can allocate an Action to any NamedElement in the model via its specification box under the Allocations section by dragging and dropping an element (such as a part Property) from the model browser onto the Allocate To field.
But an easier - and in many ways more intuitive - approach for allocating any Action is to use AllocateActivityPartition "swimlanes" as shown next .
Up next
Allocation of a CallBehaviorActionAction to a PartProperty via an AllocateActivityPartition "swimlane"
Notes
[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.
[ISSUE, TOOL] MagicDraw/Cameo 19SP3: The property path in callout does always correspond to the SysML spec examples.
[CAPABILITY, FEATURE, TOOL] MagicDraw/Cameo: Supports embedding of one or more Diagrams in another via the Diagram Overview feature. Awesome!
[FEATURE, TIP, TOOL] MagicDraw/Cameo: You can allocate an Action to any NamedElement in the model via its specification box under the Allocations section by dragging and dropping an element (such as a part Property) from the model browser onto the Allocate To field.
Snippets (quotes/extracts)
  [SysML-1.6] Activities in block definition diagrams appear as regular blocks, except the «activity» keyword may be used to indicate the Block stereotype is applied to an activity, as shown in Figure 11-1. See example in 11.4, Usage Examples.
  [SysML-1.6] Allocate is a dependency based on UML::Abstraction. It is a mechanism for associating elements of different types, or in different hierarchies, at an abstract level. Allocate is used for assessing user model consistency and directing future design ...
  [SysML-1.6] It is expected that an «allocate» relationship between model elements is a precursor to a more concrete relationship between the elements, their properties, operations, attributes, or sub-classes.
  [SysML-1.6] Allocate is a stereotype of a UML4SysML::Abstraction that is permissible between any two NamedElements. It is depicted as a dependency with the "allocate" keyword attached to it.
  [SysML-1.6] Allocate is directional in that one NamedElement is the "from" end (no arrow), and one NamedElement is the "to" end (the end with the arrow).
  [SysML-1.6] The Allocate stereotype specializes DirectedRelationshipPropertyPath to enable allocations to identify their sources and targets by a multi-level path of accessible properties from context blocks for the sources and targets.
  [SysML-1.6] Allocation is the term used by systems engineers to denote the organized cross-association (mapping) of elements within the various structures or hierarchies of a user model.
  [SysML-1.6] System modelers often associate various elements in a user model in abstract, preliminary, and sometimes tentative ways. Allocations can be used early in the design as a precursor to more detailed rigorous specifications and implementations.
Related slides (includes other tutorials)
Figure 15-1: Abstract syntax extensions for SysML Allocation
Figure 15-3: Generic Allocation, including /from and /to association ends
Figure 15-4: Behavior Allocation
Figure D.40 - Tabular Representation of Allocation from “Accelerate” Behavior Model to Power Subsystem (Table)
Related slides (backlinks, includes other tutorials)
Visit also
Visit also (backlinks)