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 Dependency
  • Creating a Dependency
  1. UML Designer
  2. Common Elements

Dependency

PreviousComment LinkNextRealization

Last updated 7 months ago

A Dependency in Modeldraw is a relationship that indicates that one element (the client) depends on another element (the supplier) for its specification or implementation. It's a versatile relationship that can be used across various diagram types to show how changes in one element may affect another.

With Dependencies in Modeldraw, you can:

  • Show that one element relies on another element

  • Indicate relationships between different components of your system

  • Illustrate how changes in one part of the system might impact other parts

  • Represent usage, instantiation, or other forms of reliance between elements

Understanding Dependency

A Dependency in Modeldraw is typically represented by a dashed line with an open arrow pointing from the dependent element (client) to the element being depended upon (supplier). Key points to understand about Dependencies include:

  • The arrow points from the dependent (client) to the depended-upon (supplier) element.

  • In Modeldraw, Dependencies are supported for:

    • Class

    • Enumeration

    • Package

    • Node (in Deployment Diagram)

    • Use Case

    • Interface

    • Component

    • Ball (Interface Realization)

Creating a Dependency

To create a Dependency in Modeldraw:

  1. Ensure you have the elements you want to connect with a Dependency in your diagram.

  2. Select the Dependency tool from the toolbox.

  3. Click on the client element (the one that will depend on another).

  4. Move your cursor to the supplier element (the one being depended upon).

  5. Click on the supplier element to complete the Dependency.

Remember that the direction of the Dependency is important. The arrow should point from the dependent element to the element it depends on.

Dependencies between Components