Back to Blog
Modelio sysml ports7/23/2023 Flow properties that represent blocks of data, such as messages, which are sent as a group across the connection.Use an Interface Block to type each logical connection (nested proxy port) with an Interface Block containing the following:.Nested elements for logical/abstract data flows across the network interface, such as sockets/connections.Nested full port elements for physical nested ports, such as pins that make up a physical ethernet port.Flow properties that represent physical items flowing out of the port, such as total electrical current (power).Use a block to type the network interface, including:.Use a full port for the raw network interface, the physical layer.I'm using MagicDraw as the SysML tool, but I don't think that should impact the core answer. a class/block) and when you are defining that this thing is a quantity that flows in your model (a flow of some kind - the message passes from one task or piece of hardware to another). I guess this boils down to confusion over when you are defining a thing (i.e. If the base message definition is a normal block, then when do you create a flow property that gets typed by that block, so that something can actually flow from one task to another through the port?Īn Interface Block should occur somewhere in there, in order to type the port, right? Does that mean I use it to define a message directly, or does that depend on my port scheme (i.e. The two Ports are now nested in the 'Equation' Port.In SysML, when modeling a message, I'm having trouble understanding what element type should be used to define it, its elements, and a port that it flows through.īoth can type a proxy port (formerly flow port, if I understand correctly), or type most other properties in other blocks as one builds up a full message interface or port system (either straight ports or nested ports). Select the checkboxes against 'Real' and 'Imaginary'.The 'Real' and 'Imaginary' Ports are shown in the list panel. Select the 'Show Owned/Inherited' checkbox.The Features window displays at the 'Interaction Points' tab. Right-click on the 'Equation' Port and select the 'Features | Interaction Points' option.In the 'Type' field, click on the drop-down arrow and select the 'Select Type' option, then locate and select the 'ComplexNumber' Block element this sets the 'Type' field to 'ComplexNumber'.Display the Properties window (press Ctrl+2) for the 'Equation' Port and select the 'Property' page.Create a SysML Block named 'ComplexNumber' with Ports named 'Real' and 'Imaginary'. Create a SysML Block named 'Equation' with a Port also named 'Equation'.In describing this procedure, we use a representation of the earlier example as a framework for the steps. This facility is available in Enterprise Architect for all versions of SysML and for UML. Once created and nested, the child Ports are always bound to the edge of the Parent Port on which they exist, during a resize or move of the parent element. Therefore we have to show them, on the Equation Port, in order to connect them. The Equation Block has a Port that takes a ComplexNumber, but we might want to connect the real and imaginary portions of that variable to different sources. This is represented by the ComplexNumber Block with two Ports, Real and Imaginary. The type of the Port is a Block (or one of its specializations) that also has Ports.'įor example, a complex number is made up of two members (of type Real) - the real value and the imaginary value. 'Ports nest other Ports in the same way that Blocks nest other Blocks. This statement is derived from the SysML 1.5 Specification:
0 Comments
Read More
Leave a Reply. |