Problems building a Use Case through UI

[johnafitch]

When attempting to emulate the transportPassenger_1 use case from the SysML v2 standard (Section A.6, pg. 661, Figure 66), I had several difficulties:

1. Couldn't select a Use Case in the General View and be able to create nested Actions beneath it. No Behavior options were available in the context menu, although intuitively every use case is the logical parent of a set of actions.
2. Couldn't d&d the parent use case node to the Action Flow canvas but could an action (so I created the flow under a start action node as a workaround).
3. Couldn't distinguish whether to use the New Start Action and New Done Action options. In SysML v2 and SysON how do these differ from a simple Action?
4. Did know how to populate on the accept action (ignitionCmd) the "input parameter giving a receiver occurrence" per the SysML spec 7.16.8. How is an input parameter defined and associated with an accept action in SysON?
   Note - I took a few shortcuts, so the final diagram has fewer forks/joins that the specification example. Figures attached, including the SysON text/code download.
   
   
   

[AxelRICHARD]

Hello,

My answers below:

1.Couldn't select a Use Case in the General View and be able to create nested Actions beneath it. No Behavior options were available in the context menu, although intuitively every use case is the logical parent of a set of actions.

Indeed, the compartment for actions inside a UseCase has not been provided yet in SysON.

2. Couldn't d&d the parent use case node to the Action Flow canvas but could an action (so I created the flow under a start action node as a workaround).

The UseCase elements cannot be represented in the ActionFlowView diagram yet in SysON. But it should as a UseCase is a specific Action.

3. Couldn't distinguish whether to use the New Start Action and New Done Action options. In SysML v2 and SysON how do these differ from a simple Action?

SysON simply follows the SysMLv2 specification. It allows to create start/done actions. A start action is simply an Action that inherits from Actions::start from the standard library. Same for the done action with Actions::done.
Here is what the specification says about start/done : Further, every action inherits the features start and done from the base action definition Actions::Action, which represent the start and end snapshots of the action.

4. Did know how to populate on the accept action (ignitionCmd) the "input parameter giving a receiver occurrence" per the SysML spec 7.16.8. How is an input parameter defined and associated with an accept action in SysON?
   Note - I took a few shortcuts, so the final diagram has fewer forks/joins that the specification example. Figures attached, including the SysON text/code download.

SysON does not handle this part of the specification yet.

Regards,