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 Ball (Interface Realization)
  • Creating a Ball (Interface Realization)
  1. UML Designer
  2. Component Diagrams

Ball (Interface Realization)

PreviousComponentNextSocket (Required Interface)

Last updated 7 months ago

A Ball, also known as Interface Realization or Provided Interface, in a Component Diagram represents an interface that a component implements or provides to other components. It indicates a service or capability that the component offers for use by other parts of the system.

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

  • Show the services or capabilities that a component provides

  • Illustrate the public facing interfaces of a component

  • Demonstrate how components interact and offer functionality to each other

  • Clearly define the contract between components

  • Represent the modular and service-oriented nature of your system architecture

Understanding Ball (Interface Realization)

A Ball in Modeldraw's Component Diagram tool is typically represented by a small circle attached to the edge of a component. Key points to understand about Balls include:

  • Represents a service or capability offered by the component.

  • Other components can connect to this interface to use the provided service.

  • Defines a set of operations or functionalities that the component guarantees to provide.

  • Allows for hiding the internal implementation details of the component.

  • A component can have multiple balls, each representing a different provided interface.

  • Each ball should be named to indicate the nature of the service it provides.

Creating a Ball (Interface Realization)

To create a Ball in Modeldraw's Component Diagram:

  1. Select the Ball (Interface Realization) tool from the toolbox.

  2. Click on the component where you want to add the provided interface.

  3. In the dialog that will show up select an interface.

  4. The Ball will appear as a small circle on the component's border.

An Interface Realization using a Ball