It is NOT true in SysML1.6+ that you "should" always use a SysML FullPort or a SysML ProxyPort instead of a "standard" Port, and it's not even always a good idea (and the spec states this very clearly in multiple places)!

Icon class
icon_class
far fa-sticky-note
icon_class_computed
far fa-sticky-note
Note kind
ASSERTION
WARNING
UML keywords
Port
SysMLv1.x keywords
FullPort
ProxyPort
"standard" Port
Dr Darren says:
This is one of the biggest misconceptions I encounter, in part because the MagicDraw SysML and Cameo tools unnecessarily "hide" standard Ports in many places (presumably under the impression that just because SysML introduces something extra only that should be used). Read these relevant "snippets" from the spec and you'll see it is simply not true that a ProxyPort or FullPort should always be used!

From the SysML-1.6 specification itself:

SysML-1.6: 'Ports that are not specified as proxy or full are simply called “ports.”'
SysML-1.6: '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.'
SysML-1.6: 'Modelers can choose between proxy or full ports at any time in the development lifecycle, or not at all, depending on their methodology.'
SysML-1.6: '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 ...'
SysML-1.6: '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.'
SysML-1.6: '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.'
SysML-1.6: '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 ...'
SysML-1.6: '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.'
SysML-1.6: '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.'
SysML-1.6: 'Ports that are not proxy or full can appear in block compartments labeled ports.'
SysML-1.6: 'All ports and nested ports (i.e., proxy, full, and ports with no stereotype applied), and their type definitions (e.g., interface blocks, blocks) can include compartments with textual and graphical representations to display their features ...'
Therefore:
Webel Best Practice strongly recommends that you DO NOT commit to using ProxyPort or FullPort early on in projects unless you are a true expert and know exactly why you are doing it. And not using ProxyPort and FullPort will also save you a lot of notational clutter.
It will help if you "un-tweak" some things in MagicDraw/Cameo:
HOWTO get at and display "standard" Ports that have been unnecessarily hidden and suppressed in MD SysML 19SP3 and Cameo 19SP3
Relates to
Figure 9-7: Usage example of proxy and full ports
Some valid FullPorts from the outside
SimpleOpticalTelescope light flow model: staging BDD and context IBD
KeplerianRefractor: simple image flow model: staging BDD
TRAIL: A SysMLv1.6+ model of the Arduino Mega2560Rev3 microcontroller board
Related notes
Related notes (backlinks)
Related snippets (extracts)
  [SysML-1.6] Ports that are not proxy or full can appear in block compartments labeled ports.
  [SysML-1.6] All ports and nested ports (i.e., proxy, full, and ports with no stereotype applied), and their type definitions (e.g., interface blocks, blocks) can include compartments with textual and graphical representations to display their features ...
  [SysML-1.6] SysML identifies two [EDIT:ADDITIONAL] usage patterns for ports, one where ports act as proxies for their owning blocks or its internal parts (proxy ports), and another where ports specify separate elements of the system (full ports).
  [SysML-1.6] Ports that are not specified as proxy or full are simply called “ports.”
  [SysML-1.6] 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.
  [SysML-1.6] 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.
  [SysML-1.6] Modelers can choose between proxy or full ports at any time in the development lifecycle, or not at all, depending on their methodology.
  [SysML-1.6] 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 ...
  [SysML-1.6] 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.
  [SysML-1.6] The stereotypes of proxy and full ports might be elided in these cases to simplify diagrams.
  [SysML-1.6] 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.
  [SysML-1.6] 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 ...
  [SysML-1.6] 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.
  [SysML-1.6] 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.
  [SysML-1.6] 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.
Visit also
Visit also (backlinks)