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 Association
  • Creating an Association
  1. UML Designer
  2. Use Case Diagrams

Association

PreviousUse CaseNextSystem Boundary

Last updated 7 months ago

An Association in a Use Case Diagram represents a communication or interaction between an Actor and a Use Case. It indicates that an Actor participates in or initiates a particular Use Case.

With Associations in Modeldraw's Use Case Diagram, you can:

  • Connect Actors to Use Cases, showing which system functionalities are used by which external entities

  • Illustrate the interactions between users (or external systems) and the system's functions

  • Demonstrate the scope of a system by showing all the ways users interact with it

  • Provide a clear, visual representation of system requirements from a user's perspective

Understanding Association

An Association in Modeldraw's Use Case Diagram tool is typically represented by a solid line connecting an Actor to a Use Case. Associations are crucial components of Use Case Diagrams as they illustrate which Actors interact with which functionalities of the system. Key points to understand about Associations include:

  • Associations connect Actors to Use Cases, showing which system functionalities are used by which external entities.

  • Associations are usually bidirectional, meaning the communication can flow both ways between the Actor and the Use Case.

  • An Actor can be associated with multiple Use Cases, and a Use Case can be associated with multiple Actors.

  • Unlike some other UML relationships, Associations typically don't have labels or stereotypes.

  • Associations represent a simple "uses" relationship and don't imply any specific type of interaction beyond that.

Creating an Association

To create an Association in Modeldraw's Use Case Diagram:

  1. Select the Association tool from the toolbox.

  2. Click on the first shape you want to connect (either the Actor or the Use Case).

  3. Move your mouse over the second shape you want to connect.

  4. Click on the second shape. An Association line will appear connecting the two shapes.

An Association between an Actor and a Use Case