Ports | Pins | Interfaces | and more

This video describes SysML terms such as Proxy Ports, Full Ports, Interfaces, Pins, Activity Nodes, Accept Even Actions, Flow Final, and Activity Final
#SysML #MBSE #STC #DigitalEngineering ##engineering #CameoSystemsModeler #MagicDraw #CATIAmagic #simulation

[@kardeskalap2165]

Awesome, thank you for sharing!

[@silk2816]

Awesome explanation! Very thorough

[@willwalker2520]

proxy port and full port dialog very helpful!

[@sebastienpoussard4418]

nice presentation. now the remaining question is how to link the pins/parameters to the proxy ports.

[@parthpatel1465]

Thank you so much for the insightful explanation.
I have a question regarding the representation of a proxy port at different levels of structural diagrams. Let's say my system has a block and needs 1 proxy port (i.e. mechanics) at the system level 1. At system level 2, the same block deals with 3 subsystems and hence requires 3 proxy ports (i.e. thermal, fluid, acoustic).
So, "How can I represent this information on different system levels?" or in other words "How can I represent that 1 port at system level 1 will be divided into 3 different ports and each of them will deal with different subsystems?"

[@enderayhanrencuzogullar3649]

Hi, did you find answer for that?

[@muondude]

Very helpful video. Thank you. Question regarding Ports and Interface Blocks, do you have a naming convention you recommend?

[@tmzhk2001]

one question . i would add port to block at IBD, you added port to block at BDD . is there any difference ?

[@brianMoberley]

No, no difference actually. Either way is the exact same. The port is actually a “structural feature” of the block in the same way that a Value Property or Reference Property is. You can create Value Properties in Parametric diagrams as well but they will still be owned by the block, and not the part, in the same way the Port will be owned by the block regardless of whether you create it in an IBD or a BDD. Great question!

[@michaelkent2254]

Software interfaces are APIs

[@brianMoberley]

That is true, Michael. Software engineers use the term interface in a way that is different from how systems engineers use the term.