Some valid FullPorts from the outside

Gallery
Tutorial
TRAIL: Webel's ultimate guide to Systems Modeling Language (v1) with MagicDraw/Cameo
Section
09:06: ProxyPorts and FullPorts
UML keywords
Port
SysML keywords
«full»
FullPort
Slide kind
SysML Block Definition Diagram (BDD)
The gist is that a FullPort can be any kind of port EXCEPT a ProxyPort, because being a FullPort is not about what it does, it's about how it does it, namely itself (or in collaboration with other elements):
Click on the image to view it full size
This slide deliberately does not expose any of the Features of these ports yet, we'll see how to do that later.

A FullPort can be port with a contract of provided and required DirectedFeatures, or a port with one or more FlowProperty items, or it may be specify a contract using provided and required Interfaces.

It is not recommended here that you mix these modes!
In general, the SysML DirectedFeature approach is more powerful and the notation is cleaner than UML provided/required Interfaces. Prefer SysML DirectedFeatures unless you have a really good reason to use Interfaces!
You don't have to always show the «full» keywords, they mostly just add clutter, noting that clients of a Port do not EVER need to know whether a Port is a FullPort, a ProxyPort, or a "standard" Port, they just have to see the contract Features:
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. The stereotypes of proxy and full ports might be elided in these cases to simplify diagrams.'
Also:
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.
Up next
11:01: [STUB] Activity modelling extensions in SysML
Notes
[ASSERTION, WARNING] 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)!
[POLICY]{STRONG} Avoid mixing flow properties on the Type of a Port with directed features (operations and values); One distinguishes between "ports with flows" and "contract ports".
[TIP]{STRONG} In general, the SysML DirectedFeature approach is more powerful and the notation is cleaner than UML provided/required Interfaces. Prefer SysML DirectedFeatures unless you have a really good reason to use Interfaces!
[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.
Snippets (quotes/extracts)
  [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] Full ports specify a separate element of the system from the owning block or its internal parts. They might have their own internal parts and behaviors to support interaction with the owning block, its internal parts, or external blocks.
  [SysML-1.6] Full ports cannot be behavioral in the UML sense of standing in for the owning object, because they handle features themselves, rather than exposing features of their owners, or internal parts of their owners.
  [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] FullPort::1_not_proxy Full ports shall not also be proxy ports. This applies even if some of the stereotypes are on subsetted or redefined ports.
  [SysML-1.6] FullPort::2_not_bound_to_fullport Binding connectors shall not link full ports (either directly or indirectly through other binding connectors) to other composite properties of the block owning the full port (or that blocks generalizations or specializati
  [SysML-1.6] FullPort::3_not_behavioral Full ports shall not be behavioral (isBehavior=false).
Visit also
Visit also (backlinks)
Related slides (includes other tutorials)
Related slides (backlinks, includes other tutorials)