(12135) Figure 11.10 Actions better shown as clearly typed anonymous CallBehaviorActions (rather than capital names & no Type)

(12136) Figure11.10 use anonymous, typed Pins for indication of flowing information type and to support {stream} Parameter

It is difficult and/or inconsistent to show the {stream} indication of the Action ':Driving' without an output Pin corresponding to an underlying output Parameter of Behavior 'Driving' satisfying the 'isStream=true' condition.

Indeed Table 11.1 - Graphical nodes included in activity diagrams shows only Actions with Pins and the {stream} indicator for UML4SysML::Parameter.isStream

The following image shows Figure 11.10 adapted to use Pins throughout (except for ControlValue input to the controller Action 'Monitor Traction'):

(12137) Figure 11.10 suggest use output Pin from <<controlOperator>> 'Enable On Brake Pressure > 0' typed by ControlValue

The <<controlOperator>> action ':Enable on Brake Pressure > 0' does not show an output Pin corresponding to an output Parameter of type ControlValue that must exist for the Behavior Enable on Brake Pressure > 0. From SysML1.0:

'11.3.2.2 ControlOperator

,,

Constraints
[1] When the «controlOperator» stereotype is applied, the behavior or operation must have at least one parameter typed by ControlValue. If the stereotype is not applied, the behavior or operation may not have any parameter typed by ControlValue.'

It would make sense (and be clearer) if the «controlOperator» had an output Pin typed by ControlValue.

Below we see the diagram adapted to use an output Pin typed by ControlValue.

Figure 11.10 - Continuous system example 1 in MD_SysML_15 using Pins wherever possible

Here we see (in advance of my analysis of the individual issues) my suggestion for an "improved" Figure 11.10, which uses typed Pins wherever possible, a strategy that solves many of the specification issues and MD SysML 15 tool issues. Note also the use of clearly typed anonymous CallBehaviorActions.

Figure 11.10 - Continuous system example 1 in MD_SysML_15 with detailed annotations on spec and tool issues

Please examine this detailed analysis of the many issues concerning Figure 11.10. Issues are extracted from this analysis and reported individually as shown in the following pages, along with an "improved" version of Figure 11.10.

---

For an even more detailed discussion of issues with Figure 11.10 and recommendations for MD SysML 15 please visit the Hybrid SUV sample tutorial:

Figure 11.10 - Continuous system example 1 in MD_SysML_15

 

Table 11.2 Rate <<discrete>> <<continous>>

[Image upload target only]