When dealing with required Interfaces you must use Usage (not Dependency) and it has dedicated "socket" notation.

Icon class
icon_class
far fa-sticky-note
icon_class_computed
far fa-sticky-note
Note kind
ASSERTION
TIP
Policy level
STRICT
UML keywords
Usage
required Interface
Relates to
Examples of Dependency and Usage
Dependency vs Usage vs Association vs Connector
Association vs Connector - detailed
Related notes
[DISPLAY, STYLE, WARNING] 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.
[DISPLAY, STYLE] SysML directed features displayed on Port symbols are often far clearer than UML-style provided/required Interface "ball (lollipop) and socket" notation
[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)