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. Component Diagrams

Socket (Required Interface)

PreviousBall (Interface Realization)NextCommunication Diagrams

Last updated 7 months ago

A Socket, also known as Required Interface, in a Component Diagram represents an interface that a component requires or expects from other components. It indicates a dependency on a service or capability that must be provided by another part of the system for the component to function properly.

With Sockets in Modeldraw's Component Diagram, you can:

  • Show the services or capabilities that a component needs from other components

  • Illustrate the dependencies of a component on external functionalities

  • Demonstrate how components interact and rely on each other

  • Clearly define the expected contracts between components

  • Represent the modular and interconnected nature of your system architecture

Understanding Socket (Required Interface)

Key points to understand about Sockets include:

  • Represents a service or capability needed by the component.

  • Shows that the component depends on an external service to function.

  • Connects to a Ball (Provided Interface) of another component that fulfills this requirement.

  • Defines a set of operations or functionalities that the component expects to be available.

  • A component can have multiple sockets, each representing a different required interface.

  • Each socket should be named to indicate the nature of the service it requires.

Creating a Socket (Required Interface)

To create a Socket in Modeldraw's Component Diagram:

  1. Ensure you have at least two components in your diagram, one with a Ball (Provided Interface) that you want to connect to.

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

  3. Click on the Ball (Provided Interface) of the component that provides the service.

  4. Move your cursor to the component that requires the service.

  5. Click on the edge of the requiring component where you want the Socket to appear.

  6. The Socket will be created and automatically connected to the Ball you selected.

A Socket