SysML: Naming: You may include Block, ValueType, and Signal names in the names of Behaviors (such as Activities) as long as this does not undermine the principles of functional analysis and allocation.

Icon class
far fa-sticky-note
far fa-sticky-note
Note kind
Policy level
Specification keywords
UML keywords
SysMLv1.x keywords
Including the names of model Blocks, ValueTypes, and Signals in Behavior names can make them much clearer, and is recommended as long as you don't pre-suppose allocations of Behaviors:

Note that a classifierBehavior is always an ownedBehavior, so strictly speaking a classifierBehavior can't directly participate in "classic" functional allocation anyway. Owned Behaviors can of course reference allocated Behaviors owned elsewhere via CallBehaviorActions.

Visit also the discussion here for some examples.

Relates to
Related notes
Related notes (backlinks)
Related snippets (extracts)
Visit also
Visit also (backlinks)