Parts in these systems may interact by many different means, such as software operations, discrete state transitions, flows of inputs and outputs, or continuous interactions. Source OMG Systems Modeling Language (SysML) 1.6
These include modeling either the logical or physical decomposition of a system, and the specification of software, hardware, or human elements. Source OMG Systems Modeling Language (SysML) 1.6
Activities in block definition diagrams can also appear with the same notation as CallBehaviorAction, except the rake notation can be omitted, if desired. Also see use of activities in block definition diagrams that include ObjectNodes. Source OMG Systems Modeling Language (SysML) 1.6
Properties with AdjunctProperty applied, where the principal of the AdjunctProperties are call actions, including call behavior actions, can be used as the part end of the associations. See 8.3.2.2 for constraints when AdjunctProperty is used ... Source OMG Systems Modeling Language (SysML) 1.6
This provides a means for representing activity decomposition in a way that is similar to classical functional decomposition hierarchies. Source OMG Systems Modeling Language (SysML) 1.6