SysML Activity extension stereotypes - REFERENCE CARD Gallery Tutorial TRAIL: Webel's ultimate guide to Systems Modeling Language (v1) with MagicDraw/Cameo Section 11:01: [STUB] Activity modelling extensions in SysML Slide kind UML Profile Diagram
Figure 11-12: Continuous system example 3 {EXPLICIT PINS} Gallery Tutorial TRAIL: The SysML-1.6 Hybrid SUV sample and specification diagrams in MagicDraw/Cameo (with annotations) [UNDERGOING UPDATE to SysML1.7] Section Section: SysML-1.6 specification diagrams: 11 Activities Slide kind SysML Activity Diagram
Figure 11-10: Continuous system example 1 {EXPLICIT PINS} Gallery Tutorial TRAIL: The SysML-1.6 Hybrid SUV sample and specification diagrams in MagicDraw/Cameo (with annotations) [UNDERGOING UPDATE to SysML1.7] Section Section: SysML-1.6 specification diagrams: 11 Activities Slide kind SysML Activity Diagram
The rake notations on the control operator and Monitor Traction indicate they are further defined by activities, as shown in Figure 11-11 and Figure 11-12. An alternative notation for this activity decomposition is shown in Figure 11-13. Source OMG Systems Modeling Language (SysML) 1.6
While the monitor is enabled, it outputs a modulation frequency for applying the brakes as determined by the ABS system. Source OMG Systems Modeling Language (SysML) 1.6
When the brake pressure goes to zero, disable control values are emitted from the control operator. The first one disables the monitor, and the rest have no effect. Source OMG Systems Modeling Language (SysML) 1.6
No pins are used on Monitor Traction, so once it is enabled, the continuously arriving enable control values from the control operator have no effect, per UML semantics. Source OMG Systems Modeling Language (SysML) 1.6
Brake pressure information also flows to a control operator that outputs a control value to enable or disable the Monitor Traction behavior. Source OMG Systems Modeling Language (SysML) 1.6
Figure 11-10: Continuous system example 1 {ELIDED PINS} Gallery Tutorial TRAIL: The SysML-1.6 Hybrid SUV sample and specification diagrams in MagicDraw/Cameo (with annotations) [UNDERGOING UPDATE to SysML1.7] Section Section: SysML-1.6 specification diagrams: 11 Activities Slide kind SysML Activity Diagram
Claim: The ControlValue input to Monitor Traction without a Pin is invalid in 'Figure 11-10: Continuous system example 1' and multiple issues with ControlOperator
Figure 11-9: Control values Gallery Tutorial TRAIL: The SysML-1.6 Hybrid SUV sample and specification diagrams in MagicDraw/Cameo (with annotations) [UNDERGOING UPDATE to SysML1.7] Section Section: SysML-1.6 specification diagrams: 11 Activities Slide kind SysML Block Definition Diagram (BDD)
Pins for control parameters are regular pins, not UML control pins. This is so the control value can be passed into or out of the action and the invoked behavior, rather than control the starting of the action, or indicating the ending of it. Source OMG Systems Modeling Language (SysML) 1.6
The control value inputs do not enable or disable the control operator execution based on their value, they only enable based on their presence as data. Source OMG Systems Modeling Language (SysML) 1.6
When the «controlOperator» stereotype is not applied, the behavior may not have a parameter typed by ControlValue. Source OMG Systems Modeling Language (SysML) 1.6
