Learn about Webel IT's new SysMLv2/MBSE Workshop Seminar course!

Provided/required Interface "lollipop" and "socket" (a.k.a. ball-and-socket) notation can quickly lead to clutter in UML Composite Structure Diagrams and SysML Internal Block Diagrams. SysML provided/required DirectedFeature notation is cleaner.

Icon class
icon_class
far fa-sticky-note
icon_class_computed
far fa-sticky-note
Note kind
DISPLAY
STYLE
WARNING
UML keywords
Port
lollipop
ball-and-socket
SysMLv1.x keywords
DirectedFeature
FeatureDirectionKind::provided
FeatureDirectionKind::required
FeatureDirectionKind::providedrequired
Relates to
[HISTORICAL] UML-STYLE: Hybrid SUV example: Ports with required/provided Interfaces (Internal Definition Diagram)
Related notes
[CAPABILITY, FEATURE, STYLE, TIP] TIP: MagicDraw/Cameo: Consider showing the Port name and type label inside the Port symbol! CAVEAT: This loses the direction indicators on Ports typed by Blocks with flow properties (but is fine if ItemFlows show the direction, or for "contract ports").
[DISPLAY, STYLE, WARNING] [HISTORICAL] ISSUE: UML: MagicDraw UML: Showing Port labels (name and type) inside Port rectangle symbols does not always work well with provided/required Interface "lollipop" and "socket" (a.k.a. ball-and-socket) notation
Related notes (backlinks)
Related snippets (extracts)
Visit also
Visit also (backlinks)