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.

This page identifies a possible issue, inconsistency, concern, error, or bug!
One of the ways Webel IT Australia helps promote tools, technologies, and languages is by donating a lot of time identifying, tracking, and reporting potential issues, in order to help vendors and developers improve the tools and technologies. In some cases, we also offer workarounds and advice for users. All issues tracked on our public site are offered most constructively and with sincerest gratitude to the tool vendors and technology developers.
DISCLAIMER: Vendors do not officially endorse issue analysis by Webel IT Australia.
Icon class
icon_class
far fa-sticky-note
icon_class_computed
far fa-sticky-note
Note kind
ANTI-PATTERN
ISSUE
WARNING
Policy level
INFORMATIVE
Specification keywords
SysPhS-1.1
UML keywords
«keyword»
Port
Association
Association::memberEnd
Association::ownedEnd
user defined Stereotype
custom Stereotype
SysMLv1.x keywords
"standard" Port
SysPhS specification figure
Keywords
Click on the image to view it full size
To understand this concern fully it helps if you first understand this tool feature:
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
The diagram shown also employs this power display feature:
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'

The concern is that an apparently user-defined or custom stereotype keyword «port» appears in some diagrams for the SysML and SysPhS specifications, even though no such stereotype keyword officially exists in UML-2.5.1 or SysML-1.6 (not even non-normative). This can be confusing for those not fully familiar with the underlying metamodel machinery, and I've seen a lot of people redundantly copying the practice.

For example, in SysML-1.6:

SysML-1.6: 'Figure 9-8 shows an association block Water Delivery between a bank of spigots and a faucet. The «port» keyword indicates which association ends are ports (associations use properties as ends, which can be ports). '

In the SysPhS-1.1 spec the keyword «port» appears in some diagrams but not in the body text.

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!

The only justification for it might be to distinguish between a Property as an Association end and a Port as an Association end in "associative" modelling in Class Diagrams or Block Definitions Diagrams (for special educational or illustrative purposes), but typically naming is sufficient for that anyway, and Ports can always be simply listed in compartments.

What can make it even more confusing is that SysML-1.6 DOES support special stereotype keywords for the extending stereotypes ProxyPort «proxy» and FullPort «full». Note however that these have not always been popular with some users:

The ProxyPort «proxy» and FullPort «full» stereotype keywords can quickly lead to clutter in diagrams. The SysML Revision Task Force is working on some new concise notational indicators on the Port rectangle symbol itself.
Relates to
BDD: Figure 39: Electrical blocks, ports & component properties
BDD: Figure 50: Signal processing system blocks, ports, & component properties
BDD: Figure 60: Hydraulics blocks, ports, & component properties
Related notes
[DISPLAY, FEATURE, TOOL]{INFORMATIVE} 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'
[CAPABILITY, FEATURE, TIP, TOOL]{INFORMATIVE} 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
[ISSUE, MODELLING, STYLE]{RECOMMENDED} 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
[DISPLAY] The ProxyPort «proxy» and FullPort «full» stereotype keywords can quickly lead to clutter in diagrams. The SysML Revision Task Force is working on some new concise notational indicators on the Port rectangle symbol itself.
[ANTI-PATTERN, MODELLING] 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!
[MODELLING, STYLE]{RECOMMENDED} Webel vs SysPhS-1.1: Recommend use standard SysML Ports instead of block part property with «port» keyword
Related notes (backlinks)
Related snippets (extracts)
  [SysML-1.6] Figure 9-8 shows an association block Water Delivery between a bank of spigots and a faucet. The «port» keyword indicates which association ends are ports (associations use properties as ends, which can be ports).
Visit also
SysPhS-1.1
OMG Systems Modeling Language (SysML) 1.6
Visit also (backlinks)