Modeldraw
  • Welcome to Modeldraw
  • Getting Started
    • Quickstart Guide
  • FAQ
  • UML Designer
    • Common Elements
      • Comment
      • Comment Link
      • Dependency
      • Realization
      • Frame
    • Class Diagrams
      • Class
      • Association
      • Generalization
      • Composition
      • Aggregation
      • Enumeration
      • Interface
      • Association Class Link
      • Ball (Interface Realization)
      • Socket (Required Interface)
    • Sequence Diagrams
      • Lifeline
      • Activation Bar
      • Synchronous Message
      • Asynchronous Message
      • Return Message
      • Found Message
      • Interaction Frame
    • Use Case Diagrams
      • Actor
      • Use Case
      • Association
      • System Boundary
      • Generalization
      • Include Relationship
      • Extend Relationship
    • State Machine Diagrams
      • State
      • Initial State
      • Final State
      • Transition
      • Superstate
      • Concurrent Boundary
      • History Pseudostate
      • History Transition
    • Package Diagrams
      • Package
    • Deployment Diagrams
      • Node
      • Communication Path
      • Deployed Artifact
      • Internet
    • Activity Diagrams
      • Initial Node
      • Activity Final
      • Action
      • Flow
      • Decision / Merge
      • Fork / Join
      • Partitions
      • Flow Final
      • Send Signal
      • Accept Signal
      • Time Signal
    • Component Diagrams
      • Component
      • Ball (Interface Realization)
      • Socket (Required Interface)
    • Communication Diagrams
      • Object
      • Link
  • Wireframes
    • Views
    • Layouts
    • Components
Powered by GitBook
On this page
  • Understanding Socket (Required Interface)
  • Creating a Socket (Required Interface)
  1. UML Designer
  2. Class Diagrams

Socket (Required Interface)

PreviousBall (Interface Realization)NextSequence Diagrams

Last updated 7 months ago

A Socket, also known as a Required Interface in UML, is a relationship that shows that a class or component needs the services specified by an interface. In Modeldraw, you can use the Socket notation to represent this dependency in a compact and visually distinct manner, particularly useful in class and component diagrams.

Understanding Socket (Required Interface)

The Socket notation for Required Interface represents the dependency of a component on an interface provided by another component. Key characteristics include:

  • It shows that a component requires an interface

  • It's represented by a half-circle or "socket" connected to the requiring component

  • The interface name is shown near the socket

  • It's often used in component diagrams to show required interfaces

Creating a Socket (Required Interface)

To create a Socket (Required Interface) in Modeldraw:

  1. Create the Class that requires the interface.

  2. Select the Socket (Required Interface) tool from the toolbar.

  3. Click on the requiring Class.

  4. Move above and click the Ball of the Interface that the Class requires.

  5. The Socket will be created, connecting the requiring Class to the Ball of the Class implementing the Interface.

A Socket