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
icon_class
far fa-sticky-note
icon_class_computed
far fa-sticky-note
Note kind
ANTI-PATTERN
CAVEAT
MODELLING
NAMING
WARNING
Policy level
INFORMATIVE
Specification keywords
SysML-1.6
SysML-1.7
UML keywords
Element::owner
BehavioredClassifier::ownedBehavior
BehavioredClassifier::classifierBehavior
Behavior
Activity
Signal
SysMLv1.x keywords
Allocate
Block
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:
SysML: Naming: Including Block, ValueType, and Signal names in the names of Behaviors (such as Activities) can sometimes undermine purist functional allocation (because it may presuppose the element of the physical solution that carries out the function).

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
Refrigerant cycle Activity allocation
Related notes
[NAMING, POLICY]{STRONG} Prefer 'UpperCamelCase' (a.k.a. PascalCase) names for Behaviors such as Activities intended for use in CallBehaviorActions, or at least use a 'Capital first letter'; avoid 'all lower case' (as it leads to confusion with lower case Action names)
[ANTI-PATTERN, CAVEAT, MODELLING]{OPTION} SysML: Having a Behavior owned by a Block it is allocated to may undermine purist functional allocation (because it presupposes the element of the physical solution that carries out the function)
[ANTI-PATTERN, CAVEAT, MODELLING]{OPTION} SysML: Having a Behavior owned by a Block it is allocated to may undermine purist functional allocation (because it presupposes the element of the physical solution that carries out the function)
[NAMING, POLICY]{STRICT} SysMLv1.x: ValueType naming: The Webel convention is 'UpperCamelCase' (a.k.a. PascalCase).
[NAMING, POLICY, STYLE]{STRONG} The Webel modelling style, naming conventions, and Best Practices for SysML are more consistent than most SysML spec diagrams. When following Webel courses please DO NOT use the spec sample diagrams (which serve a different purpose) as visual references!
[NAMING, POLICY]{STRONG} Use 'UpperCamelCase' (a.k.a. PascalCase) names for Classifiers such as UML Classes and SysML Blocks) to avoid confusion with 'lowerCase' Property names [see however special naming conventions for acronyms and SysML contract and flow Blocks]
Related notes (backlinks)
Related snippets (extracts)
Visit also
Visit also (backlinks)