ActivityParameterNode

HOWTO: Send and receive a Signal via Ports in SysML and Cameo Simulation Toolkit

The Append activity within Number

Gallery

Tutorial

Section

Slide kind

TRAIL: Webel's ultimate guide to Systems Modeling Language (v1) with MagicDraw/Cameo

ActivityParameterNode cases - REFERENCE CARD

This content has been marked as discussing an ADVANCED topic!

Gallery

Tutorial

Section

01:04: UML Behavior: Activities quick start

Slide kind

TRAIL: Webel's ultimate guide to Systems Modeling Language (v1) with MagicDraw/Cameo

Parameter vs ActivityParameterNode vs Pin

Gallery

Tutorial

Section

01:04: UML Behavior: Activities quick start

Slide kind

TRAIL: Webel's ultimate guide to Systems Modeling Language (v1) with MagicDraw/Cameo

uml101 - Activity Diagram - notation - REFERENCE CARD

This content has been marked as discussing an ADVANCED topic!

Gallery

Tutorial

Section

01:04: UML Behavior: Activities quick start

Slide kind

TRAIL: The SysML-1.6 Hybrid SUV sample and specification diagrams in MagicDraw/Cameo (with annotations) [UNDERGOING UPDATE to SysML1.7]

Figure 11-12: Continuous system example 3 {EXPLICIT PINS}

Gallery

Tutorial

Section

Section: SysML-1.6 specification diagrams: 11 Activities

Slide kind

OMG Systems Modeling Language (SysML) 1.6

The result of Calculate Traction is filtered by a decision node for a threshold value and Calculate Modulation Frequency determines the output of the activity.

Source

Figure 11-5: Block definition diagram with activities as blocks associated with types of object nodes, variables, and parameter

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

hybrid diagram

SysML Block Definition Diagram (BDD)

The Webel trail versions of the Activity Diagrams D.36 and D.38 use the name 'transMode' for the output Parameter and corresponding ActivityParameterNode (consistent with the spec figure D.38) NOT 'transMode_imported' (as in spec figure D.36)

Figure D.38 - Detailed Behavior Model for “Provide Power” {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

Slide kind

TRAIL: The SysML-1.6 Hybrid SUV sample and specification diagrams in MagicDraw/Cameo (with annotations) [UNDERGOING UPDATE to SysML1.7]

MagicDraw/Cameo 19SP3: if Continuous or Discrete are applied to the Parameter of an ActivityParameterNode the keywords «continuous» or «discrete» can be optionally displayed on the ActivityParameterNode symbol

Figure D.38 - Detailed Behavior Model for “Provide Power” {ELIDED PINS}

Gallery

Tutorial

Section

Slide kind

TRAIL: The SysML-1.6 Hybrid SUV sample and specification diagrams in MagicDraw/Cameo (with annotations) [UNDERGOING UPDATE to SysML1.7]

Figure D.36 - Behavior Model for “Accelerate” Function (Activity Diagram) {EXPLICIT PINS}

Gallery

Tutorial

Section

Slide kind

TRAIL: The SysML-1.6 Hybrid SUV sample and specification diagrams in MagicDraw/Cameo (with annotations) [UNDERGOING UPDATE to SysML1.7]

Figure D.36 - Behavior Model for “Accelerate” Function (Activity Diagram) {ELIDED PINS}

Gallery

Tutorial

Section

Slide kind

An inout Parameter shall be associated with at most one input ActivityParameterNode and at most one output ActivityParameterNode.

Source

An in Parameter shall not be associated with an output ActivityParameterNode and an out or return Parameter shall not be associated with an input ActivityParameterNode (though either may be associated with an ActivityParameterNode that does not have ..

Source

An Activity shall have one ActivityParameterNode corresponding to each in, out, or return Parameter and two ActivityParameterNodes for each inout Parameter.

Source

(Note that whether an ActivityParameterNode is for input or output is not determined until at least one ActivityEdge is connected to it.)

Source

An ActivityParameterNode shall have either all incoming or all outgoing ActivityEdges. An ActivityParameterNode with outgoing edges is an input ActivityParameterNode, while an ActivityParameterNode with incoming edges is an output ActivityParameterNode.

Source

Each ActivityParameterNode is associated with one Parameter of the Activity that owns the node. The type of an ActivityParameterNode shall be the same as the type of its associated Parameter.

Source

Within an Activity, inputs to and outputs from an Activity are handled using ActivityParameterNodes.

Source

When the Activity is invoked, values may be passed into the Activity execution on input Parameters (i.e., those with direction in or inout) and values may be passed out .. on output Parameters (i.e., those with direction inout, out or return).

Source

15.4.3.2 Activity Parameter Nodes - As a kind of Behavior, an Activity may have Parameters

Source

Except in the case of an output ActivityParameterNode, tokens held by an ObjectNode may leave the node on outgoing ActivityEdges.

Source

Except in the case of an input ActivityParameterNode ... the tokens held by an ObjectNode arrive from incoming ActivityEdges.

Source

HOWTO simulate UML-2.5.1 'Figure 14.7 Composite State with two States' in Cameo Simulation Toolkit - Operation-driven Transition case study

The append(n:int) operation and its Activity method Append

Gallery

Tutorial

Section

Slide kind

HOWTO simulate UML-2.5.1 'Figure 14.7 Composite State with two States' in Cameo Simulation Toolkit - Operation-driven Transition case study

The number.append Activity as entry Behavior for the PartialDial State

Gallery

Tutorial

Section

Slide kind

HOWTO simulate UML-2.5.1 'Figure 14.7 Composite State with two States' in Cameo Simulation Toolkit - Operation-driven Transition case study

Activity: DialN(n:int)

Gallery

Tutorial

Section

Slide kind

If an Activity has more than one InitialNode, then invoking the Activity starts multiple concurrent control flows, one for each InitialNode. (Additional concurrent flows may begin at input ActivityParameterNodes and enabled ExecutableNodes ...

Source