Webel: SysML: SE: The custom Stereotype keyword «whitebox» applied to an Activity indicates that it is part of the functional analysis breakdown serving a «whitebox» «scenario» Activity (directly or indirectly) for a UseCase.

Icon class
icon_class
far fa-sticky-note
icon_class_computed
far fa-sticky-note
Note kind
CONVENTION
MODELLING
NAMING
TIP
Policy level
RECOMMENDED
UML keywords
Activity
CallBehaviorAction
CallBehaviorAction::behavior
SysMLv1.x keywords
SysML Activity Diagram
Keywords
Click on the image to view it full size

In the Webel recipe for pragmatic SE with SysML the custom Stereotype keyword «whitebox» applied to an Activity indicates that it is part of the functional analysis breakdown serving a «whitebox» «scenario» Activity (directly or indirectly) for a UseCase.

Note that «whitebox» refers here to the 'behavior' of a CallBehaviorAction even if it "shines" through as a so-called secondary stereotype on a CallBehaviorAction symbol in a «blackbox» level diagram!

The «whitebox» content is not somehow exposed here in the «blackbox» diagram; you have to navigate to the Activity Diagram for the «whitebox» Activity to see inside it as shown here with allocation swimlanes:

Webel Best Practice: Webel: SysML: SE: A functional analysis «whitebox» Activity may have swimlanes that Allocate to logical subsystems (logical handlers) within the 'problem' zone or to design/implementation level blocks.

Visit also:

[STUB] TRAIL: Webel's ultimate guide to simplified yet adequate pragmatic systems engineering with functional analysis in SysMLv1 for smaller scale MBSE projects in the MagicDraw/Cameo/CATIA Magic tools
Webel Best Practice: Webel: SysML: SE: «blackbox»: The custom Stereotype keyword «scenario» indicates a Behavior (Interaction as Sequence Diagram or Activity) that Refines a top-level UseCase within the 'problem' zone.
Relates to
[STUB] TRAIL: Webel's ultimate guide to simplified yet adequate pragmatic systems engineering with functional analysis in SysMLv1 for smaller scale MBSE projects in the MagicDraw/Cameo/CATIA Magic tools
Related notes
[EXPLANATION, GOTCHA, MODELLING]{INFORMATIVE} HOWTO "cheat" with two-level white-boxing and tracking stereotypes because you just don't want that darn "extra" logical subsystem (conceptual subsystem) Block the systems engineers reckon you are supposed to use (and why it's easier to actually use one)
[CAPABILITY, FEATURE, TOOL] Magicdraw/Cameo has powerful query view tables, maps, and dependency matrix diagrams!
[CONVENTION, FEATURE, MODELLING, OPTION, TIP, TOOL]{INFORMATIVE} SysMLv1: MagicDraw/Cameo: Having a SystemContext as the 'subject' of each main UseCase plays nicely with the feature for automated creation of usage-level allocation swimlanes in SysML Activity Diagrams for part properties. But it's not the only way.
[MODELLING, TIP, TOOL]{INFORMATIVE} The Webel recipe for pragramatic SE with SysML adopts the MagicDraw/Cameo tool friendly approach of using a SystemContext as 'subject' of top-level UseCases (although using a System as 'subject' can also be used).
[CONVENTION, MODELLING, NAMING, TIP]{RECOMMENDED} Webel: SysML: SE: A functional analysis «whitebox» Activity may have swimlanes that Allocate to logical subsystems (logical handlers) within the 'problem' zone or to design/implementation level blocks.
[CONVENTION, MODELLING, NAMING, TIP]{RECOMMENDED} Webel: SysML: SE: Naming convention: «whitebox»: A '$' prefix indicates a «logical» system, «logical» subsystem (aka conceptual subsystem) or «logical» handler Block (which is a more specific form of «logical» subsystems Block).
[CONVENTION, MODELLING, NAMING, TIP]{RECOMMENDED} Webel: SysML: SE: Stereotype keyword convention: BY DEFINITION HERE «blackbox» and «whitebox» refer specifically to the 'problem' zone and NEVER the 'solution' zone (as opposed to more general uses of the terms 'black-box' and 'white-box').
[CONVENTION, MODELLING, NAMING, TIP]{RECOMMENDED} Webel: SysML: SE: «blackbox»: The custom Stereotype keyword «scenario» indicates a Behavior (Interaction as Sequence Diagram or Activity) that Refines a top-level UseCase within the 'problem' zone.
Related notes (backlinks)
Related snippets (extracts)
Visit also
[STUB] TRAIL: Webel's ultimate guide to simplified yet adequate pragmatic systems engineering with functional analysis in SysMLv1 for smaller scale MBSE projects in the MagicDraw/Cameo/CATIA Magic tools
Visit also (backlinks)