A StateUsage must directly or indirectly specialize the StateUsage States::stateActions from the Systems
Model Library. (Chapter 8.3.18.6 StateUsage of the SysMLv2 Specification).
States::stateActions is typed by abstract state def StateAction.
abstract state def StateAction defines two states named start and done.
It means that every StateUsage has access to start and done StateUsages.
We should be able to model those start and done in the state transition compartment of a StateUsage.
New tools should be available on StateUsage graphical node (and its subtypes) and on state transition compartments.
New tools should be named New Start State and New Done State and be put in the Behavior section of the palette.
You can check what has been done for New Start Action and New Done Action, it should probably follow the same pattern.
Also add New Start State and New Done State tool on StateDefinition graphical nodes (and its subtypes).
A
StateUsagemust directly or indirectly specialize theStateUsageStates::stateActions from the SystemsModel Library. (Chapter 8.3.18.6 StateUsage of the SysMLv2 Specification).
States::stateActions is typed by abstract state def StateAction.
abstract state def StateAction defines two states named start and done.
It means that every
StateUsagehas access to start and doneStateUsages.We should be able to model those start and done in the state transition compartment of a
StateUsage.New tools should be available on
StateUsagegraphical node (and its subtypes) and on state transition compartments.New tools should be named New Start State and New Done State and be put in the Behavior section of the palette.
You can check what has been done for New Start Action and New Done Action, it should probably follow the same pattern.
Also add New Start State and New Done State tool on
StateDefinitiongraphical nodes (and its subtypes).