Signal

[TRAIL] SysMLv1: The Webel Radio Net port-based messaging example model in Cameo Systems Modeler and Cameo Simulation Toolkit

Context and structural model for the RadioNet, NetSession, and RadioStation

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.

Webel Radio Net: The 'RadioNetContext' system context as both an IBD and a BDD

Webel Radio Net: 'structure' SysML Package Diagram

Webel Radio Net: 'channel' SysML Package Diagram

Webel Radio Net: 'net' SysML Package Diagram with the 'RadioNet' system

Webel Radio Net: Focus BDD for block 'NetSession'

Webel Radio Net: 'NetSession' Activities overview

Webel Radio Net: Focus BDD for block 'SessionLog'

Webel Radio Net: 'radio' SysML Package Diagram with high level view of Port types for 'Radio' Signals

Gallery

Tutorial

[TRAIL] SysMLv1: The Webel Radio Net port-based messaging example model in Cameo Systems Modeler and Cameo Simulation Toolkit

Section

Webel Radio Net: Model overview, exchange items, and Ports

Slide kind

[TRAIL] SysMLv1: The Webel Radio Net port-based messaging example model in Cameo Systems Modeler and Cameo Simulation Toolkit

Webel Radio Net: Focus BDD of the 'InitSession' scheduling Signal and its special role in a net session

Gallery

Tutorial

Section

Webel Radio Net: Model overview, exchange items, and Ports

Slide kind

[TRAIL] SysMLv1: The Webel Radio Net port-based messaging example model in Cameo Systems Modeler and Cameo Simulation Toolkit

Webel Radio Net: 'message' SysML Package Diagram with Message block "packet" and '$msg' String

Gallery

Tutorial

Section

Webel Radio Net: Model overview, exchange items, and Ports

Slide kind

[TRAIL] SysMLv1: The Webel Radio Net port-based messaging example model in Cameo Systems Modeler and Cameo Simulation Toolkit

Webel Radio Net: 'scheduling' SysML Package Diagram with scheduling message Signal families (and Port types)

Gallery

Tutorial

Section

Webel Radio Net: Model overview, exchange items, and Ports

Slide kind

[TRAIL] SysMLv1: The Webel Radio Net port-based messaging example model in Cameo Systems Modeler and Cameo Simulation Toolkit

SysMLv1: MagicDraw/Cameo: GOTCHA: If you DRAG a Signal onto a Block symbol it will create a Reception. One way to create a Property typed by a Signal is to use a composite Association. Or just create an untyped Property then type it by the Signal.

Webel Radio Net: 'exchange' SysML Package Diagram with Signals (and Port types)

Gallery

Tutorial

Section

Webel Radio Net: Model overview, exchange items, and Ports

Slide kind

[TRAIL] SysMLv1: The Webel Radio Net port-based messaging example model in Cameo Systems Modeler and Cameo Simulation Toolkit

Simulating RadioMessage relaying within the RadioNet

Simulating the RadioNet session scheduling

[TRAIL] SysMLv1: The Webel Radio Net port-based messaging example model in Cameo Systems Modeler and Cameo Simulation Toolkit

The 3-Way RadioNet communication paths

[TRAIL] SysMLv1: The Webel Radio Net port-based messaging example model in Cameo Systems Modeler and Cameo Simulation Toolkit

Signals as exchange items

ISSUE: Cameo Simulation Toolkit: v2024x: Although does not respect inheritance of attributes of Signals on SendSignalAction or un-marshalling AcceptEventAction DOES require them on 'effect' Behaviors.

SysMLv1: Cameo Simulation Toolkit: GOTCHA: Do not use Associations with Signal attributes, they will become null when fed as argument values for Parameters of 'effect' Behaviors of Transitions

SysMLv1: Cameo Simulation Toolkit: HOWTO Handle a timeout for a Signal send/receive: Strategy: StructuredActivityNode with AcceptEventAction + TimeEvent [with mini video]

Gallery

Tutorial

TRAIL: SysMLv1/UML: Cameo Simulation Toolkit® (Magic Model Analyst®): Some basics for beginners and some more advanced cases [with mini videos]

Section

Slide kind

TRAIL: SysMLv1/UML: Cameo Simulation Toolkit® (Magic Model Analyst®): Some basics for beginners and some more advanced cases [with mini videos]

SysMLv1: Cameo Simulation Toolkit: HOWTO Handle a timeout for a Signal send/receive: Strategy: TimeEvent on Transition [with mini video]

Gallery

Tutorial

Section

Slide kind

TRAIL: SysMLv1/UML: Cameo Simulation Toolkit® (Magic Model Analyst®): Some basics for beginners and some more advanced cases [with mini videos]

SysMLv1: Cameo Simulation Toolkit: HOWTO send a Signal via a nested Port using Action Language Helper (ALH) [with mini video]

Gallery

Tutorial

Section

Slide kind

TRAIL: SysMLv1/UML: Cameo Simulation Toolkit® (Magic Model Analyst®): Some basics for beginners and some more advanced cases [with mini videos]

SysMLv1: Cameo Simulation Toolkit: Cases for StateMachine Transitions with 'effect' Behaviors and/or States with 'entry' Behaviors triggered by a Signal with an attribute [with mini video]

Gallery

Tutorial

Section

Slide kind

TRAIL: SysMLv1/UML: Cameo Simulation Toolkit® (Magic Model Analyst®): Some basics for beginners and some more advanced cases [with mini videos]

SysMLv1: Cameo Simulation Toolkit: Cases for Transitions triggered by Signals sent direct to a remote target vs via Ports [with mini video]

This content has been marked as discussing an ADVANCED topic!

Gallery

Tutorial

Section

Slide kind

TRAIL: SysMLv1/UML: Cameo Simulation Toolkit® (Magic Model Analyst®): Some basics for beginners and some more advanced cases [with mini videos]

SysMLv1: Cameo Simulation Toolkit: HOWTO handle sending and receiving families of related Signal types with reuse of send/receive and processing logic [with mini video]

This content has been marked as discussing an ADVANCED topic!

Gallery

Tutorial

Section

Slide kind

TRAIL: SysMLv1/UML: Cameo Simulation Toolkit® (Magic Model Analyst®): Some basics for beginners and some more advanced cases [with mini videos]

SysMLv1: Cameo Simulation Toolkit: HOWTO send a Signal via a Port to an intended recipient via a mediating secure RoutingHub [with mini video]

Gallery

Tutorial

Section

Slide kind

Action Language for Foundational UML 1.1

ISSUE: Cameo Simulation Toolkit: v2024x: Does not show argument Pins corresponding to inherited attributes of Signal on SendSignalAction or an un-marshalling AcceptEventAction. No known UML2.5.1 or fUML-1.4 constraint; no obvious tool display option.

fUML-1.4: 7.6.2.1: Reception: [1] fuml_reception_no_method: A reception must not have an associated method.self.method->isEmpty()

Source

Webel: SysML: Heard of "follow the money"? In MBSE we "follow the flows"! Identify requests, data packets, messages, signals early on and use ItemFlow as often as you can wherever you can! Adopt a signal processing mindset throughout (systems thinking).

SysML: Naming: You may include Block, ValueType, and Signal names in the names of Behaviors (such as Activities) as long as this does not undermine the principles of functional analysis and allocation.

SysML: Naming: Including Block, ValueType, and Signal names in the names of Behaviors (such as Activities) can sometimes undermine purist functional allocation (because it may presuppose the element of the physical solution that carries out the function).

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

SysML+SysPhS: Flows: If you intend to use a Classifier to type the itemProperty of an ItemFlow on a Connector for a physical interaction you MUST use a Block (not a ValueType or Signal) so your can extend ConservedQuantityKind.

SysML: Flows: If you use a Signal to type the itemProperty of an ItemFlow on a Connector, care must be take in how you create the Property or you might get an unwanted signal Reception on the owning context Block.

SysML: Whether you use a Block, ValueType, or Signal to represent something that flows (and can be applied to an ItemFlow) depends on what you want to achieve. If you want to indicate something structured with value properties with Units use a Block.

StateMachine for Refrigerant states

Gallery

Tutorial

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

Section

Slide kind

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

Overview of ValueTypes and Units

Gallery

Tutorial

Section

Slide kind

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

Package Diagram overview of a simple domestic air conditioner with an inverter

Gallery

Tutorial

Section

Slide kind

UML/SysML: HOWTO Consume a SignalEvent message in a StateMachine Transition 'effect' or State 'entry' or 'exit' Activity

MagicDraw/Cameo: You can drag a Class symbol onto a Class symbol (in a Class Diagram) or a Block symbol or ValueType symbol onto or Block symbol (in a Block Definition Diagram) to create a new part property or value property

SysML: Electronics: When modelling electronics systems you should to decide and make clear (with ItemFlow and/or Stereotypes) whether you are modelling signals (information, does not care about GND) or a physical design with voltage (needs GND)

Screencast: UML/SysML: HOWTO Consume a SignalEvent message in a StateMachine Transition 'effect' or State 'entry' or 'exit' Activity

Keywords

Video style

Consume a SignalEvent message in a StateMachine Transition 'effect' or State 'entry' or 'exit' Activity

Gallery

Tutorial

Section

Slide kind

hybrid diagram

UML Activity Diagram

Consume a SignalEvent message in a StateMachine Transition 'effect' or State 'entry' or 'exit' Activity

UML/SysML: HOWTO Consume a SignalEvent message in a StateMachine Transition 'effect' or State 'entry' or 'exit' Activity

Jump to first slide

Sections

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

Keywords

Video style

This video accompanies this mini tutorial trail: HOWTO: Send and receive a Signal via Ports in SysML and Cameo Simulation Toolkit.

Cameo: UML: When sending a Signal via a Port with a SendSignalAction, Cameo does not care whether the Port is conjugated (even if it should).

IBD with Keypad, two specific Receiver sub-types, and a Display

Gallery

Tutorial

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

Section

Slide kind

IBD with Keypad, two specific Receiver sub-types, and a Display

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

Jump to first slide

Sections

Cameo: SysML: When sending a Signal via a Port with a SendSignalAction, Cameo does not care what the directed feature directions of the Signal receptions on the Type of the Port are (even if it should).

REFERENCE CARD: Property cheat-sheet for Block

Gallery

Tutorial

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

Section

08:01: The building Blocks of SysML

Slide kind

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

Activity example: send and catch Signal

Gallery

Tutorial

Section

01:04: UML Behavior: Activities quick start

Slide kind

hybrid diagram

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

Transitions

This content has been marked as discussing an ADVANCED topic!

Gallery

Tutorial

Section

01:03: UML Behavior: StateMachines quick start

Slide kind

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

Section

01:02: UML 101 for model-based systems engineering with SysML

Slide kind

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

REFERENCE CARD: Types of Block Properties and Block compartments

Gallery

Tutorial

Section

08:01: The building Blocks of SysML

Slide kind

A compartment with the label “receptions” may appear as part of a block definition to show signal receptions. The “«signal»” keyword is optional in this compartment.

Source

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

MagicDraw/Cameo v19SP3: uses the Block compartment name 'signal receptions' instead of just 'receptions'. [CLAIMED FIXED in v2021x]

ExampleBlock in a Block Definition Diagram (BDD)

Gallery

Tutorial

Section

08:01: The building Blocks of SysML

Slide kind

FlowProperty::1_restricted_types A FlowProperty shall be typed by a ValueType, Block, or Signal.

Source

When Monitor Traction is enabled, it begins listening for signals coming in from the wheel and accelerometer, as indicated by the signal receipt symbols on the left, which begin listening automatically when the activity is enabled.

Source

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

Figure 11-11: Continuous system example 2 {EXPLICIT PINS}

Gallery

Tutorial

Section

Section: SysML-1.6 specification diagrams: 11 Activities

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-11: Continuous system example 2 {ELIDED PINS}

Gallery

Tutorial

Section

Section: SysML-1.6 specification diagrams: 11 Activities

Slide kind

Note that the parentheses are not considered part of the input-argument list, so a request-message-label without an input-argument-list may still optionally include an empty set of parentheses (“()”) after the message-name.

Source

If a request-message-label does not include an input-argument-list and the Message has a signature, then this denotes that the Message has wildcard arguments corresponding to all in and inout ownedParameters of an Operation or attributes of a Signal ...

Source

Message::signature : NamedElement [0..1] ... The signature of the Message is the specification of its content. It refers either an Operation or a Signal.

Source

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

Figure D.9 - Black Box Interaction for "StartVehicle", referencing White Box Interaction

Gallery

Tutorial

Section

Section: SysML-1.6: HSUV sample

Slide kind

SysML Sequence Diagram

UML Sequence Diagram

Figure D.8 - Finite State Machine Associated with “Drive the Vehicle”

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

Figure D.22 continues the refinement of this Controller Area Network (CAN) bus architecture using ports.

Source

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

Figure D.21 - Initially Defining Flow Specifications for the CAN Bus (CAN Bus Flow Properties)

Gallery

Tutorial

Section

Section: SysML-1.6: HSUV sample

Slide kind

Figure D.21 is an incomplete first step in the refinement of this bus architecture, as it begins to specify the flow properties for InternalCombustionEngine, the Transmission, and the ElectricalPowerController.

Source

For purposes of example, the ports, flows, and related point-to-point connectors in Figure D.19 are being refined into a common bus architecture. For this example, ports with flow properties have been used to model the bus architecture.

Source

This single signal carries the temperature, rpm, and knockSensor information of the engine.

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 Controller Activity (classifierBehavior of the Controller class)

Gallery

Tutorial

Section

Slide kind

UML Activity Diagram

If it has isUnmarshall=true, then it must have result OutputPins corresponding to each of the attributes of the Signal of the SignalEvent (in order), and the attribute values of the Signal instance associated with an accepted SignalEvent occurrence ...

Source

If an accept signal action has isUnmarshall=false, then it must have a single result OutputPin on which the Signal instance associated with an accepted SignalEvent occurrence is placed.

Source

An AcceptEventAction with a trigger for a SignalEvent is informally called an accept signal action.

Source

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

Overview: Controller class (and its Activity), Dialer Class (and its StateMachine), Number class

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

Representing the telephone numbers as Signals

Gallery

Tutorial

Section

Slide kind

HOWTO invoke an operation as a Transition guard in Cameo Simulation Toolkit

The Signal trigger simulator in Cameo Simulation Toolkit 19SP3 does not support run-time user-defined attribute values (but you can define defaults)

StateMachine diagram for comparing action language access to an operation for a guard

Gallery

Tutorial

Section

Slide kind

HOWTO invoke an operation as a Transition guard in Cameo Simulation Toolkit

Class diagram for comparing action language access to an operation for a guard

Gallery

Tutorial

Section

Slide kind