SysML Activity Diagram

hex$E$GungorWinterton$1987$twophase$htc$horizontal as a single expression using ‘sym$’ markup

Gallery

Tutorial

[TECHNICAL SLIDE TRAIL] The Webel libraries for Wolfram Mathematica: With SysMLv1 models.

Section

SECTION: Miscellaneous examples of applications of Webel libraries for Mathematica to air conditioners and heat exchangers. With SysMLv1 models.

Gungor-Winterton method for boiling heat transfer 1987 as SysML Activity Diagram ('$SI$' Real convention version)

Gallery

Tutorial

[TECHNICAL SLIDE TRAIL] The Webel libraries for Wolfram Mathematica: With SysMLv1 models.

Section

SECTION: Miscellaneous examples of applications of Webel libraries for Mathematica to air conditioners and heat exchangers. With SysMLv1 models.

hex$E$Shah$twophase$htc$combined as a single expression using ‘sym$’ markup

Gallery

Tutorial

[TECHNICAL SLIDE TRAIL] The Webel libraries for Wolfram Mathematica: With SysMLv1 models.

Section

SECTION: Miscellaneous examples of applications of Webel libraries for Mathematica to air conditioners and heat exchangers. With SysMLv1 models.

The Shah 1982 CHART correlation for saturated boiling heat transfer as SysML Activity Diagrams (2): Detailed view of the hex$SI$Shah$twophase$htc$combined SI Real convention function variant

Gallery

Tutorial

[TECHNICAL SLIDE TRAIL] The Webel libraries for Wolfram Mathematica: With SysMLv1 models.

Section

SECTION: Miscellaneous examples of applications of Webel libraries for Mathematica to air conditioners and heat exchangers. With SysMLv1 models.

Slide kind

SysML Activity Diagram

The Shah 1982 CHART correlation for saturated boiling heat transfer as SysML Activity Diagrams (1)

Gallery

Tutorial

[TECHNICAL SLIDE TRAIL] The Webel libraries for Wolfram Mathematica: With SysMLv1 models.

Section

SECTION: Miscellaneous examples of applications of Webel libraries for Mathematica to air conditioners and heat exchangers. With SysMLv1 models.

Slide kind

SysML Activity Diagram

Webel: SysML4Mathematica: Activity Diagrams used purely for analysis and as development aids are not required to show every ControlFlow, may omit InitialNode and ActivityFinalNode, and are not required to fully validate in SysML tools or execute.

About «pseudo» blocks (always prefixed with ‘@’)

This content has been marked as discussing an ADVANCED topic!

Gallery

Tutorial

[TECHNICAL SLIDE TRAIL] The Webel libraries for Wolfram Mathematica: With SysMLv1 models.

Section

SECTION: Modelling the Wolfram Language in SysMLv1 and related Webel coding conventions

Extract Options from an OptionsPattern[] in a SysML Activity (2) DETAILED

This content has been marked as discussing an ADVANCED topic!

Gallery

Tutorial

[TECHNICAL SLIDE TRAIL] The Webel libraries for Wolfram Mathematica: With SysMLv1 models.

Section

SECTION: Modelling the Wolfram Language in SysMLv1 and related Webel coding conventions

Extract Options from an OptionsPattern[] in a SysML Activity (1)

This content has been marked as discussing an ADVANCED topic!

Gallery

Tutorial

[TECHNICAL SLIDE TRAIL] The Webel libraries for Wolfram Mathematica: With SysMLv1 models.

Section

SECTION: Modelling the Wolfram Language in SysMLv1 and related Webel coding conventions

Webel: Mathematica: CONVENTION: The Stereotype keyword «functional» indicates a "pseudo functional" representation of functional in SysML. There are limits to representation of functional programming in SysML, but it can be informative and is worth doing.

The sigsUp function with OptionsPattern modelled as a SysML Activity (and with "pseudo functional" representation)

This content has been marked as discussing an ADVANCED topic!

Gallery

Tutorial

[TECHNICAL SLIDE TRAIL] The Webel libraries for Wolfram Mathematica: With SysMLv1 models.

Section

SECTION: Modelling the Wolfram Language in SysMLv1 and related Webel coding conventions

The Webel '$opt$' option "help holder" convention

Gallery

Tutorial

[TECHNICAL SLIDE TRAIL] The Webel libraries for Wolfram Mathematica: With SysMLv1 models.

Section

SECTION: The Webel '$opt$' and '$arg$' help holder conventions for options and arguments in the Wolfram Language

SysML Activity with @pseudo functions capturing Wolfram Language logic

This content has been marked as discussing an ADVANCED topic!

Gallery

Tutorial

[TECHNICAL SLIDE TRAIL] The Webel libraries for Wolfram Mathematica: With SysMLv1 models.

Section

SECTION: Modelling the Wolfram Language in SysMLv1 and related Webel coding conventions

SysML/UML ExpansionRegion for iteration (as adapted for use with Mathematica)

Gallery

Tutorial

[TECHNICAL SLIDE TRAIL] The Webel libraries for Wolfram Mathematica: With SysMLv1 models.

Section

SECTION: Modelling the Wolfram Language in SysMLv1 and related Webel coding conventions

SysML Activities as function networks (simple contrived Real maths example)

Gallery

Tutorial

[TECHNICAL SLIDE TRAIL] The Webel libraries for Wolfram Mathematica: With SysMLv1 models.

Section

SECTION: Modelling the Wolfram Language in SysMLv1 and related Webel coding conventions

Example: Representation of a Webel MAll class MTools method as a SysML Activity Diagram

Gallery

Tutorial

[TECHNICAL SLIDE TRAIL] The Webel libraries for Wolfram Mathematica: With SysMLv1 models.

Section

SECTION: Modelling the Wolfram Language in SysMLv1 and related Webel coding conventions

Webel: SysML: SE: A functional analysis «whitebox» Activity may have swimlanes that Allocate to logical subsystems (logical handlers) within the 'problem' zone or to design/implementation level blocks.

Webel: SysML: SE: The custom Stereotype keyword «whitebox» applied to an Activity indicates that it is part of the functional analysis breakdown serving a «whitebox» «scenario» Activity (directly or indirectly) for a UseCase.

Webel: SysML: SE: «blackbox»: The custom Stereotype keyword «scenario» indicates a Behavior (Interaction as Sequence Diagram or Activity) that Refines a top-level UseCase within the 'problem' zone.

Webel: SysML: SE: Terminology: '«logical» handler' is used for a specific kind of «logical» subsystem (aka 'conceptual subsystem') that is a SPECIFIC collaboration of parts that handle one Activity usage in a higher level «whitebox» Activity.

HOWTO "cheat" with two-level white-boxing and tracking stereotypes because you just don't want that darn "extra" logical subsystem (conceptual subsystem) Block the systems engineers reckon you are supposed to use (and why it's easier to actually use one)

Webel: SysMLv1: Functional analysis (isolation of white-box Activities identified via «blackbox» scenario Activities of UseCases). Recommend custom stereotype them. Candidate: «whitebox» (or a recommended SE methodology stereotype).

SysML: Cameo/MagicDraw: ItemFlow notation/indication on ObjectFlow edges in SysML Activity Diagrams is a tool-specific feature, although it was proposed and discussed (but DEFERRED) as part of the OMG SysMLv1 Revision Task Force (RTF).

SysMLv1: MagicDraw/Cameo: Having a SystemContext as the 'subject' of each main UseCase plays nicely with the feature for automated creation of usage-level allocation swimlanes in SysML Activity Diagrams for part properties. But it's not the only way.

SysMLv1: MagicDraw/Cameo: Automated creation of usage-level allocation swimlanes in SysML Activity Diagrams for part properties of a Block. EXAMPLE: A UseCase scenario within a SystemContext as UseCase ‘subject’.

SysMLv1: UseCase scenario representations: On use of Activity Diagrams with swimlanes and/or Sequence Diagrams (Interactions): Actor or block-based custom «actor» on 1st (typically left) Lifeline/Swimlane, System/Subsystem on 2nd Lifeline/Swimlane

Webel: MBSE: SysMLv1: Prefer a custom «actor» extension of a Block (such as the non-normative External) over UML-style Actor for use as parts in IBDs and on allocation swimlanes. You can also have a Trace from a block-based «actor» to a UML-style Actor.

Webel: SysML/UML: Dr Darren explains HOWTO use concise 'i'/'o' (input/output) Pin and Parameter naming conventions to promote a signal processing mindset in Activity Diagrams. And HOWTO get them compact.

TIP: SysMLv1: MagicDraw/Cameo: Activity Diagrams: Consider using the Pin display mode 'Name And Type Labels Inside' for 'Position of Labels'. Dr Darren swears by it!

Webel: Psy/MPsy: Psychrometrics for Mathematica: '$HC' in a function name indicates pure sensible heating or cooling (with no change in water vapour content). Such functions may also be used in the pure sensible portion of a 2-step treatment.

Webel: SysML4Mathematica: POLICY: Handle flow sign changes via a single negative (not duplicated and "adjusted" algebra). This strategy may come at a very slight performance cost (for benefit of more robustness).

SysMLv1.x: Limitation: The 'body' (maths formula) of an OpaqueBehavior can't be synchronised (shared) with the 'constraint' of a ConstraintBlock (directly in the SysML model). Can lead to a WET (not DRY) model and breaks Single Source of Truth!

Webel: SysML4Mathematica: SysML Activities and SysML Activity Diagrams CAN represent some functional programming paradigms (sort of). You can type Parameters by encapsulations of functions and pass them to/from InputPins/OutputPins of Actions.

Webel: SysML4Mathematica: TIP: Representing Mathematica functions as SysML ConstraintBlocks modelled in SysML Parametric Diagrams and as Activities in SysML Activity Diagrams is super for analysing the dependencies between functions and their arguments!

SysML: Cameo Systems Modeler: A ValueType that does not extend Real might not always simulate correctly when used to type a constraint parameter of a ConstraintBlock (in a SysML Parametric Diagram) or to type a parameter (in a SysML Activity Diagram)!

ISSUE/GOTCHA: MagicDraw/Cameo v2022x: UML/SysML: If you "rename" an ActivityParameterNode symbol on the frame of an Activity Diagram it actually renames the underlying Parameter (only) NOT the name of the ActivityParameterNode element!

SysML/UML: MagicDraw/Cameo: The name of an ActivityParameterNode does not always stay in synch with its Parameter (and it is not always desirable that it does).

SysML/UML: MagicDraw/Cameo: Activity Diagrams: All Pins of CallBehaviorActions and CallOperationActions MUST be displayed (synchronised). All ActivityParameterNodes MUST be shown on the frame of an Activity Diagram.

Webel: SysML4Mathematica: SysML Parametric Diagrams are not well suited to modelling calculations with Blocks for MTools classes, or for modelling complex logic flow of Mathematica functions. Prefer SysML Activity Diagrams for those modelling cases.

SysML/UML: MagicDraw/Cameo: GOTCHA: Connecting a typed OutputPin to an untyped (UNSPECIFIED) InputPin with an ObjectFlow changes the type of the InputPin

Webel: SysML4Mathematica: Convention: A '$E' in a function name indicates that all parameters (arguments and return) are Mathematica '_' expressions. However, when representing such functions as Activities they may end up getting strongly typed in tools!

TIP: Webel: SysML/UML: On the boundary of Action symbols in Activity Diagrams use any placement or "ordering" of Parameter symbols that works for the diagram. Ignore the Parameter ordering of Operation and Behavior signatures completely!

SysML4Mathematica: Example 11 [B]: Total (qDotTot), sensible (qDotSen), and latent cooling (qDotLat) required for cooling air: Using Webel MPsy objects and SysML Activity Diagrams

Gallery

Tutorial

TRAIL: Air Conditioning Psychrometrics (vs CED Engineering course): Example results (only) in Mathematica and SysML using the Webel Psy package and MPsy class

Section

Slide kind

SysML Activity Diagram

SysML4Mathematica: Example 11 [A] Total (qDotTot), sensible (qDotSen), and latent cooling (qDotLat) required for cooling air: Using CoolProp wrappers and SysML Parametric Diagrams

Gallery

Tutorial

TRAIL: Air Conditioning Psychrometrics (vs CED Engineering course): Example results (only) in Mathematica and SysML using the Webel Psy package and MPsy class

Section

Slide kind

SysML Parametric Diagram

Webel: SysML4Mathematica: When modelling the main logic flow of Mathematica code with Activity Diagrams it isn't necessary to model every Mathematica construct. Placeholder Actions, OpaqueActions , and OpaqueBehaviors (as CallBehaviorActions) may be used.

SysML4Mathematica: Example 10: Condition and dehumidify air by chilling and condensing some moisture: Process table

Gallery

Tutorial

TRAIL: Air Conditioning Psychrometrics (vs CED Engineering course): Example results (only) in Mathematica and SysML using the Webel Psy package and MPsy class

Section

Slide kind

SysML Activity Diagram

SysML Parametric Diagram

SysML4Mathematica: Example 09: Moisture added to air: Amount (mass)

Gallery

Tutorial

TRAIL: Air Conditioning Psychrometrics (vs CED Engineering course): Example results (only) in Mathematica and SysML using the Webel Psy package and MPsy class

Section

Slide kind

SysML Activity Diagram

SysML Parametric Diagram

SysML/UML: MagicDraw/Cameo: To display the body of an OpaqueBehavior on a usage (CallBehaviorAction) in an Activity Diagram use an element property callout of 'Body' into a Note with a handle to the CallBehaviorAction

SysML4Mathematica: Example 08a: Humidification: Drying lumber with air: required volumetric air flow rate

Gallery

Tutorial

TRAIL: Air Conditioning Psychrometrics (vs CED Engineering course): Example results (only) in Mathematica and SysML using the Webel Psy package and MPsy class

Section

Slide kind

SysML Activity Diagram

SysML Parametric Diagram

SysML4Mathematica: Example 07: Sensible cooling: 'qDotSen' (-ve): energy transfer rate FROM humid air

Gallery

Tutorial

TRAIL: Air Conditioning Psychrometrics (vs CED Engineering course): Example results (only) in Mathematica and SysML using the Webel Psy package and MPsy class

Section

Slide kind

SysML Activity Diagram

SysML Parametric Diagram

SysML4Mathematica: Example 06: Sensible heating: 'qSen' per mass (+ve): energy transfer TO humid air

Gallery

Tutorial

TRAIL: Air Conditioning Psychrometrics (vs CED Engineering course): Example results (only) in Mathematica and SysML using the Webel Psy package and MPsy class

Section

Slide kind

SysML Activity Diagram

SysML Parametric Diagram

SysML4Mathematica: Example 05: Sensible heating: 'qSen' (+ve): energy transfer TO humid air

Gallery

Tutorial

TRAIL: Air Conditioning Psychrometrics (vs CED Engineering course): Example results (only) in Mathematica and SysML using the Webel Psy package and MPsy class

Section

Slide kind

SysML Activity Diagram

SysML Parametric Diagram

SysML4Mathematica: Psychrometrics (humid air physics) Air Conditioning scenarios in graphical Systems Modeling Language (SysMLv1.x) and Mathematica

Gallery

Tutorial

TRAIL: Air Conditioning Psychrometrics (vs CED Engineering course): Example results (only) in Mathematica and SysML using the Webel Psy package and MPsy class

Section

Slide kind

SysML Package Diagram

[FIXED in v2022Refresh1]: BUG: MagicDraw/Cameo: 19SP3/v2022xGolden: Activity Diagrams: Pin display mode 'Position of Labels' does not stick, label positions in Diagrams have sometimes moved after re-opening a project [and "FIX"]

MagicDraw/Cameo: UML/SysML: TIP: Activity Diagrams: Learn how to use the Refactor > Extract feature to divide-and-conquer and identify cleaner flow and logic. Get control of those crossed wires!

Webel: MagicDraw/Cameo: UML/SysML: TIP: Activity Diagrams, StateMachine Diagrams, and port-based IBDs: Keep it loose initially with oblique (no break) paths, then square it up with rectangular paths at the very end

UML/SysML: TIP: Using Cameo Simulation Toolkit will strengthen your use of Activity Diagrams even when they are "just" analysis diagrams

MagicDraw/Cameo 19SP3/v2022xGolden: [FIXED in v2022xRefresh1]: Activity Diagrams: Pin display mode 'Position of Labels' does not work correctly for 'Name And Type Labels Inside', only shows the Name inside (not the Label) [and WORKAROUND]

Stereotypes applying to parameters can appear on object nodes in activity diagrams, as shown in Figure 11-7, when the object node notation is used as a shorthand for pins.

Source

OMG Systems Modeling Language (SysML) 1.6

Screencast: SysML/MBSE: An air conditioner refrigerant cycle in Cameo Simulation Toolkit

Keywords

Video style

This video only shows the Activities and StateMachines. For the underlying Block model please visit this accompanying slide trail:

TRAIL: SysML: Simple model of an air conditioner with a refrigerant cycle and StateMachine driven by Activities in MagicDraw/Cameo

35: Activity ActualisePhysicalAsset and «STUB» ManifestActualAssetFromPotentialAsset

This content has been marked as discussing an ADVANCED topic!

Gallery

Tutorial

TRAIL: The Webel SysMLv1 Pattern for Digital Twinning

Section

Slide kind

hybrid diagram

SysML Activity Diagram

34: Activity «STUB» PopulatePotentialWithProcessesAndTrackingData

This content has been marked as discussing an ADVANCED topic!

Gallery

Tutorial

TRAIL: The Webel SysMLv1 Pattern for Digital Twinning

Section

Slide kind

SysML Activity Diagram

33: Activity «STUB» PopulateDigitalWithDesignModels

This content has been marked as discussing an ADVANCED topic!

Gallery

Tutorial

TRAIL: The Webel SysMLv1 Pattern for Digital Twinning

Section

Slide kind

SysML Activity Diagram

32: Activity CreatePhysicalEntityFromDigitalEntity

This content has been marked as discussing an ADVANCED topic!

Gallery

Tutorial

TRAIL: The Webel SysMLv1 Pattern for Digital Twinning

Section

Slide kind

SysML Activity Diagram

31: Case: Create a new physical asset using a «digital» @Entity initially as a digital "template"

This content has been marked as discussing an ADVANCED topic!

Gallery

Tutorial

TRAIL: The Webel SysMLv1 Pattern for Digital Twinning

Section

Slide kind

SysML Activity Diagram

30: Activity UpdateDigitalFromPhysical

This content has been marked as discussing an ADVANCED topic!

Gallery

Tutorial

TRAIL: The Webel SysMLv1 Pattern for Digital Twinning

Section

Slide kind

SysML Activity Diagram

25: Effect Activities used by the acquisition case

This content has been marked as discussing an ADVANCED topic!

Gallery

Tutorial

TRAIL: The Webel SysMLv1 Pattern for Digital Twinning

Section

Slide kind

hybrid diagram

SysML Activity Diagram

29: Acquisition case: «STUB» Activities for initial model data and information mapping

This content has been marked as discussing an ADVANCED topic!

Gallery

Tutorial

TRAIL: The Webel SysMLv1 Pattern for Digital Twinning

Section

Slide kind

SysML Activity Diagram

28: Activity «stub» PopulateDigitalEntity

This content has been marked as discussing an ADVANCED topic!

Gallery

Tutorial

TRAIL: The Webel SysMLv1 Pattern for Digital Twinning

Section

Slide kind

SysML Activity Diagram

27: Activity CreateDigitalEntityFromPhysicalEntity

This content has been marked as discussing an ADVANCED topic!

Gallery

Tutorial

TRAIL: The Webel SysMLv1 Pattern for Digital Twinning

Section

Slide kind

SysML Activity Diagram

Screencast: The Webel Digital Twin Pattern for SysML: Part 1: Simulating acquisition or creation of physical assets using Activities and StateMachines in Cameo Simulation Toolkit.

Keywords

Video style

© Copyright 2020 Darren R C Kelly (Webel IT Australia).

Read more about Screencast: The Webel Digital Twin Pattern for SysML: Part 1: Simulating acquisition or creation of physical assets using Activities and StateMachines in Cameo Simulation Toolkit.

26: Activity IdentifyAcquireAttachPhysical

This content has been marked as discussing an ADVANCED topic!

Gallery

Tutorial

TRAIL: The Webel SysMLv1 Pattern for Digital Twinning

Section

Slide kind

SysML Activity Diagram

23: Mini StateMachine for DigitalTwin and DoAttach effect Activity

This content has been marked as discussing an ADVANCED topic!

Gallery

Tutorial

TRAIL: The Webel SysMLv1 Pattern for Digital Twinning

Section

Slide kind

hybrid diagram

SysML Activity Diagram

SysML StateMachine Diagram

24: Case: Acquisition: Twin a pre-existing physical asset

This content has been marked as discussing an ADVANCED topic!

Gallery

Tutorial

TRAIL: The Webel SysMLv1 Pattern for Digital Twinning

Section

Slide kind

hybrid diagram

SysML Activity Diagram

Activity example: send and catch Signal

Gallery

Tutorial

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

Section

01:04: UML Behavior: Activities quick start

Slide kind

hybrid diagram

SysML Activity Diagram

SysML Block Definition Diagram (BDD)

In a SysML Activity Diagram a control flow may be notated with a dashed line and stick arrowhead; this helps distinguish a ControlFlow from an ObjectFlow symbol.

11:01: [STUB] Activity modelling extensions in SysML

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

Slides in this section

If you want to navigate the entire section including the additional explanatory text click on the title link of the first slide to view the full slide page, then use the next links to move through the slide pages. If you just want to view the slide images only in sequence, click on any slide to view it larger in a viewer, then click again to move through each slide in this tutorial trail section.

SysMLv1.7 Activity extensions: ControlOperator and ControlValueKind: ADVANCED REFERENCE CARD

SysML Activity extension stereotypes - REFERENCE CARD

Tabular representations, such as the allocation table, are used in SysML but are not considered part of the diagram taxonomy.

Source

OMG Systems Modeling Language (SysML) 1.6

Activity diagrams have also been modified via the activity extensions.

Source

OMG Systems Modeling Language (SysML) 1.6

The SysML diagrams

Gallery

Tutorial

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

Section

01:01: [BRIEF] SysMLv1 Overview

Slide kind

SysML Package Diagram

MagicDraw/Cameo: In SysML Activity Diagrams you can only set the allocation mode in to 'usage' or 'definition' for an entire AllocateActivityPartition group at once, not for individual AllocateActivityPartition columns or rows.

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

The activity diagram for Monitor Traction is shown in Figure 11-11.

Source

OMG Systems Modeling Language (SysML) 1.6

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

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

MagicDraw/Cameo: to use SysML-style control flow notation with a dashed line and stick arrowhead set the Diagram Style display option SysML Control Flow Style to true (enabled)

Figure 11-4: Control flow notation

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 Activity Diagram

Control flow may be notated with a dashed line and stick arrowhead, as shown in Figure 11-4.

Source

OMG Systems Modeling Language (SysML) 1.6

CallBehaviorActions in activity diagrams may optionally show the action name with the name of the invoked behavior using the colon notation shown in Figure 11-3.

Source

OMG Systems Modeling Language (SysML) 1.6

Stereotypes applied to behaviors may appear on the notation for CallBehaviorAction when invoking those behaviors, as shown in Figure 11-2.

Source

OMG Systems Modeling Language (SysML) 1.6

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

Section: SysML-1.6: HSUV sample

Slide kind

SysML Activity Diagram

MagicDraw/Cameo: If the underlying Parameter of an InputPin or OutputPin on a CallBehaviorAction or CallOperationAction is set to streaming, the indicator {stream} optionally displays on the Pin

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

Slide kind

SysML Activity Diagram

Figure D.36 - Behavior Model for “Accelerate” Function (Activity Diagram) {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: HSUV sample

Slide kind

SysML Activity Diagram

Figure D.36 - Behavior Model for “Accelerate” Function (Activity Diagram) {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: HSUV sample

Slide kind

SysML Activity Diagram

Subscribe to SysML Activity Diagram