&quot;standard&quot; Port

Slide kind

TRAIL: SysMLv1+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

NewtonCoolingWithBlocks

Gallery

Tutorial

Section

Slide kind

TRAIL: SysMLv1+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

Block Diagram Components - S0 - DISO

Gallery

Tutorial

Section

Slide kind

TRAIL: SysMLv1+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

Block Diagram Components - SO - SISO

Gallery

Tutorial

Section

Slide kind

TRAIL: SysMLv1+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

ThirdSpeciesWolf

Gallery

Tutorial

Section

Slide kind

TRAIL: SysMLv1+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

FoxRabbitWithInit

Gallery

Tutorial

Section

Slide kind

TRAIL: SysMLv1+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

Interaction - Predation

Gallery

Tutorial

Section

Slide kind

TRAIL: SysMLv1+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

SinkOrSource - Reproduction - Starvation

Gallery

Tutorial

Section

Slide kind

TRAIL: SysMLv1+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

Lotka-Volterra Equations Revisited - RegionalPopulation

Gallery

Tutorial

Section

Slide kind

TRAIL: SysMLv1+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

Lotka-Volterra Equations Revisited - FlowingSpecies

Gallery

Tutorial

Section

Slide kind

TRAIL: SysMLv1+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

UngroundedGearComparison - comparison

Gallery

Tutorial

Section

Slide kind

TRAIL: SysMLv1+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

GroundedGear - comparison

Gallery

Tutorial

Section

Slide kind

TRAIL: SysMLv1+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

SMD_WithBacklash

Gallery

Tutorial

Section

Slide kind

TRAIL: SysMLv1+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

SMD

Gallery

Tutorial

Section

Slide kind

TRAIL: SysMLv1+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

Compliant - RotationalInertia - Spring - Damper - Ground

Gallery

Tutorial

Section

Slide kind

TRAIL: SysMLv1+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

Basic Rotational Components - TwoFlange

Gallery

Tutorial

Section

Slide kind

TRAIL: SysMLv1+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

TwoPin - SwitchedRLC

Gallery

Tutorial

Section

Slide kind

TRAIL: SysMLv1+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

Resistor - Capacitor - Inductor - StepVoltage - Ground

Gallery

Tutorial

Section

Slide kind

TRAIL: SysMLv1+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

Electrical Components - TwoPin

Gallery

Tutorial

Section

Slide kind

TRAIL: SysMLv1+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

AmbientConvectionCapacitance (combined)

Gallery

Tutorial

Section

Slide kind

TRAIL: SysMLv1+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

Cooling

Gallery

Tutorial

Section

Slide kind

TRAIL: SysMLv1+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

AmbientCondition

Gallery

Tutorial

Section

Slide kind

TRAIL: SysMLv1+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

MagicDraw/Cameo v19SP3: vs SysPhS-1.1: Modelica export: Direct binding from a PhSVariable value property within a FlowProperty of a Port to an inner value property does not flatten. WORKAROUND: Use an intermediate constraint property.

Convection

Gallery

Tutorial

Section

Slide kind

TRAIL: SysMLv1+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

CoolingToAmbient

Gallery

Tutorial

Section

Slide kind

TRAIL: SysMLv1+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

ThermalCapacitance - Adiabatic

Gallery

Tutorial

Section

Slide kind

TRAIL: SysMLv1+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

Thermal Connectors

Gallery

Tutorial

Section

Slide kind

TRAIL: SysMLv1+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

Graphical Connectors

Gallery

Tutorial

Section

Slide kind

TRAIL: SysMLv1+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

Block Connectors

Gallery

Tutorial

Section

Slide kind

TRAIL: SysMLv1+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

Fluid Connectors - ThermoFluid

Gallery

Tutorial

Section

Slide kind

TRAIL: SysMLv1+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

Fluid Connectors - Compressible

Gallery

Tutorial

Section

Slide kind

TRAIL: SysMLv1+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

Fluid Connectors - Incompressible

Gallery

Tutorial

Section

Slide kind

TRAIL: SysMLv1+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

SimpleDomains - Thermal

Gallery

Tutorial

Section

Slide kind

TRAIL: SysMLv1+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

SimpleDomains - Rotational

Gallery

Tutorial

Section

Slide kind

TRAIL: SysMLv1+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

SimpleDomains - Translational

Gallery

Tutorial

Section

Slide kind

TRAIL: SysMLv1+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

SimpleDomains - Electrical

Gallery

Tutorial

Section

Slide kind

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

UML/SysML: In Internal Block Diagrams: If you have a Port with a name that indicates a unique role AND and if there is an ItemFlow on a Connector that implies or suggests the Type of the Port, consider hiding the Type on the Port symbol.

SysML: The placement of usages of Blocks, their Ports, and Connectors in an Internal Block Diagrams DOES NOT necessarily represent physical geometry!

IBD: Context for SimpleDomesticInverterAirCon - detailed

Gallery

Tutorial

Section

Slide kind

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

IBD: Context for SimpleDomesticInverterAirCon

Gallery

Tutorial

Section

Slide kind

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

Overview of two SysPhS-style physical interaction Port types

Gallery

Tutorial

Section

Slide kind

SysML Package Diagram

Overview of flowing quantities and Port types with flows

Gallery

Tutorial

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

Section

Slide kind

SysML Package Diagram

SysPhS-1.1 vs Modelica: On export the SysPhS signal flow Port types are flattened to remove the FlowProperty (rSig, iSig, or bSig). In the exported Modelica code you'll only ever see the Port names.

SysML/SysPhS-1.1: Anonymous Property or Action names may not be an option if: You are exporting to Modelica or Simulink; You absolutely need names for generated query reports (such as generated Interface Control Documents).

BDD & IBD: HumidifierSystem

Gallery

Tutorial

TRAIL: SysMLv1: SysPhS-1.1 Annex A examples in MagicDraw/Cameo vs Modelica (Wolfram SystemsModeler)

Section

Annex A.5: Humidifier (with Units)

Slide kind

TRAIL: SysMLv1: SysPhS-1.1 Annex A examples in MagicDraw/Cameo vs Modelica (Wolfram SystemsModeler)

Figure 65: Internal structure of the total humidifier system - black box vs details

Gallery

Tutorial

Section

Annex A.5: Humidifier (with Units)

Slide kind

TRAIL: SysMLv1: SysPhS-1.1 Annex A examples in MagicDraw/Cameo vs Modelica (Wolfram SystemsModeler)

SysPhS-1.1: Annex A.5: Humidifier: Naming not very consistent across parts, input/output Port name, value properties, or constraint parameters

The use of an additional «port» keyword on a Port is usually redundant and causes clutter. The use of an additional «port» keyword on a basic Property is an obsolete trick. Please don't imitate it even if you see it in some specification sample diagrams!

MagicDraw/Cameo: You can drag out a Property (or Port) from a Class or Block symbol to create an Association with the Property (or Port) as one end

There is no «port» stereotype keyword for Port or Property in UML-2.5.1 or SysML-1.6. It is assumed to be introduced in some SysML and SysPhS specification diagrams as a custom or user-defined stereotype for special illustration purposes.

SysPhS-1.1: Apparent use of part Property with «port» keyword (instead of standard SysML Port) leads to property path symbols appearing inside the boundary of context blocks (instead of within a Port symbol on the boundary) in IBDs and Parametric Diagrams

Webel vs SysPhS-1.1: Recommend use standard SysML Ports instead of block part property with «port» keyword

IBD: Figure 59: Internal structure of hydraulics system (with :values compartment showing)

Gallery

Tutorial

Section

Annex A.4: Hydraulics

Slide kind

Part properties, typed by blocks ... represent components in this system. They are connected to each other through ports, which represent openings in the tanks and pipe ...

Source

TRAIL: SysMLv1: SysPhS-1.1 Annex A examples in MagicDraw/Cameo vs Modelica (Wolfram SystemsModeler)

IBD: Figure 59: Internal structure of hydraulics system

Gallery

Tutorial

Section

Annex A.4: Hydraulics

Slide kind

TRAIL: SysMLv1: SysPhS-1.1 Annex A examples in MagicDraw/Cameo vs Modelica (Wolfram SystemsModeler)

BDD: Figure 60: Hydraulics blocks, ports, & component properties

Gallery

Tutorial

Section

Annex A.4: Hydraulics

Slide kind

In this example, ports are typed by RealSignalOutElement and RealSignalInElement from the signal flow library ... which both have a flow property rSig typed by Real, from SysML, as shown in Figure 49.

Source

Signals flowing in and out of components are modeled by ports typed by interface blocks that have flow properties typed by numbers.

Source

Figure 48 connects the signal processor input to an amplifier, the output of the amplifier to a high-pass filter in parallel with a low-pass filter, the outputs of the filters to a mixer, and the output of the mixer to the signal processor output.

Source

Figure 47 connects a signal source to a signal processor, which it connects to a signal sink that displays the output.

Source

Signals pass through ports in the direction shown by the arrows. Item flows on connectors indicate that the signals are real numbers.

Source

Part properties, typed by blocks ... represent the components of the system. They are connected through ports .. which represent signal outputs and inputs ...

Source

TRAIL: SysMLv1: SysPhS-1.1 Annex A examples in MagicDraw/Cameo vs Modelica (Wolfram SystemsModeler)

IBD: Figure 48: Internal structure of the signal processor

Gallery

Tutorial

Section

Slide kind

TRAIL: SysMLv1: SysPhS-1.1 Annex A examples in MagicDraw/Cameo vs Modelica (Wolfram SystemsModeler)

BDD: Figure 50: Signal processing system blocks, ports, & component properties

Gallery

Tutorial

Section

Slide kind

TRAIL: SysMLv1: SysPhS-1.1 Annex A examples in MagicDraw/Cameo vs Modelica (Wolfram SystemsModeler)

IBD: Figure 47: Internal structure of test bed from signal source to sink

Gallery

Tutorial

Section

Slide kind

TRAIL: SysMLv1: SysPhS-1.1 Annex A examples in MagicDraw/Cameo vs Modelica (Wolfram SystemsModeler)

BDD: Figure 49: Total system (source to sink) blocks, ports, & component properties

Gallery

Tutorial

Section

Slide kind

Modelica: Naming convention: Why does the OnePort family of electrical components have 2 Pins? Where is the "one port"?

Component PhSConstants (SimulinkParameters and ModelicaParameters) for vectors and matrices have MultidimensionalElement applied, with dimension * and ,, respectively ...

Source

Component input ports for vectors are typed by specializations of RealVectorSignalInElement, while component output ports for vectors are typed by specializations of RealVectorSignalOutElement ...

Source

Component input ports for scalars are typed by RealSignalInElement, IntegerSignalInElement, or BooleanSignalInElement, while component output ports for scalars are typed by RealSignalOutElement, IntegerSignalOutElement, or BooleanSignalOutElement ...

Source

Simulation platform data specified in the Component Ports (Input and Output), PhSConstants, and platform Parameters columns are scalar, unless marked with a V (vector) or an M (matrix).

Source

TRAIL: SysMLv1: SysPhS-1.1 specification body figures in MagicDraw/Cameo vs Modelica [using Wolfram SystemsModeler]

Figure 30: Elements for signal flow

Gallery

Tutorial

Section

Slide kind

SysML Package Diagram

RealInSignalElement has an in flow property rsig, while RealOutSignalElement has the same property with an out direction.

Source

Figure 22 shows an example signal flow application. The block Spring has two ports u and y, of type RealInSignalElement and RealOutSignalElement from the signal flow library ..., respectively.

Source

Computer has ports u and y of type RealInSignalElement [ERROR:TYPO] and RealOutSignalElement [ERROR:TYPO] from the signal flow library (see Subclause 11.2.1), respectively.

Source

Model [ERROR] contains a connect equation linking component p2 of s1 to component p1 of s2.

Source

The following Modelica code corresponds to Figure 24. It has a model Example with two components s1 and s2 of types SpringA and SpringB, respectively. The models SpringA and SpringB have two components p1 and p2 of type Flange, defined similarly to Spring

Source

SysML connectors correspond to Modelica connect equations, which link components typed by Modelica connectors. This depends on the correspondence between SysML port types and Modelica connectors ...

Source

TRAIL: SysMLv1: SysPhS-1.1 specification body figures in MagicDraw/Cameo vs Modelica [using Wolfram SystemsModeler]

Figure 24: Connectors in SysML

Gallery

Tutorial

Section

Slide kind

TRAIL: SysMLv1: SysPhS-1.1 specification body figures in MagicDraw/Cameo vs Modelica [using Wolfram SystemsModeler]

Figure 23: Ports for physical interaction in SysML

Gallery

Tutorial

Section

Slide kind

TRAIL: SysMLv1: SysPhS-1.1 specification body figures in MagicDraw/Cameo vs Modelica [using Wolfram SystemsModeler]

Figure 22: Ports for signal flow in SysML

Gallery

Tutorial

Section

Slide kind

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

Webel: SysML: Electronics: DO NOT represent a jack/socket as a dumb proxy. Imagine it can introduce some signal noise or other effect (such as buzz) to test it is a physical model.

MagicDraw/Cameo: If you want to show a Property or Port listed both in its corresponding compartment on a Class or Block symbol and as the end of an Association in the same diagram, set the display option Show Association Ends As Attributes/Ports to 'all'

Boundary Ports and kinds of Connectors

Gallery

Tutorial

Section

09:02: Ports - The basics

Slide kind

If the general ports had both behaviors and internal binding connectors, then both specializations would be invalid.

Source

Unstereotyped ports have the basic functionality of stereotyped ones, including flow properties and nested ports, so they can be used as long as the modeler is not concerned with the distinction between proxy and full, and the constraints they impose.

Source

For example, if the port types on the general block in Figure 9-7 had behaviors defined, then the proxy specialization would be invalid. If the general ports had binding connectors to internal parts, then the full specialization would be invalid.

Source

Unstereotyped ports do not commit to whether they are proxy or full, and do not prevent or dictate future application of the stereotypes, except for ports that violate constraints of the stereotypes.

Source

Figure 9-7 happens to use unstereotyped ports on a general block distributed to users, and stereotyped ports on its specializations for implementation, but the modelers might have not used stereotypes at all, if they did not care whether the model met ...

Source

Modelers can apply stereotypes for proxy and full ports at any stage of model development, or not all if the stereotype constraints are not needed.

Source

The stereotypes of proxy and full ports might be elided in these cases to simplify diagrams.

Source

Using existing blocks with ports only requires knowing the port types, because they define the features available for linking or communication with those ports via connectors.

Source

Modelers have the option of applying stereotypes for proxy and full ports to indicate whether ports are specifying features of their owners and internal parts (proxy), or for themselves separately (full). This is a concern when defining ports, rather ...

Source

Modelers can choose between proxy or full ports at any time in the development lifecycle, or not at all, depending on their methodology.

Source

Proxy and full ports support the capabilities of ports in general, but these capabilities are also available on ports that are not declared as proxy or full.

Source

In either case, users of a block are only concerned with the features of its ports, regardless of whether the features are surfaced by proxy ports, or handled by full ports directly.

Source

TRAIL: SysMLv1: The SysML-1.6 Hybrid SUV sample and specification diagrams in MagicDraw/Cameo (with annotations) [ARCHIVAL]

Typing a "standard" Port by an InterfaceBlock or ~InterfaceBlock IS allowed AND can be useful; typing a FullPort by an InterfaceBlock or ~InterfaceBlock is formally allowed but not so useful, because it would have no parts or behaviors to do anything.

UML/SysML: In Internal Block Diagrams: Consider hiding the name of a named Port or Property in a Diagram if its Type is sufficient to indicate its role.

SysML: Typing a Port by an InterfaceBlock or ~InterfaceBlock does NOT imply that the Port is a ProxyPort (but ProxyPort must be typed by an InterfaceBlock or ~InterfaceBlock)

Figure D.22 - Consolidating Connectors into the CAN Bus (CAN Bus Description)

Gallery

Tutorial

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

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