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

Extend Relationship

PreviousInclude RelationshipNextState Machine Diagrams

Last updated 7 months ago

An Extend Relationship in a Use Case Diagram represents a situation where one Use Case (the extending Use Case) may be used to augment the behavior of another Use Case (the base Use Case) under certain conditions.

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

  • Show optional or conditional behavior in your Use Cases

  • Represent alternative flows or exceptional scenarios

  • Add flexibility to your Use Case model

  • Separate core functionality from optional or specialized behavior

  • Illustrate how a system can be extended without modifying the base Use Cases

  • Manage complexity by breaking down Use Cases into more manageable pieces

Understanding Extend Relationship

An Extend Relationship in Modeldraw's Use Case Diagram tool is typically represented by a dashed arrow with an open arrowhead, pointing from the extending Use Case to the base Use Case, labeled with the stereotype «extend». Key points to understand about Extend Relationships include:

  • The extending Use Case is only executed under specific conditions.

  • The base Use Case is complete on its own and may or may not include the extending Use Case.

  • The arrow points from the extending Use Case to the base Use Case.

  • The base Use Case may define specific points where the behavior can be extended.

  • It helps in separating core functionality from optional or specialized behavior.

  • Extend Relationships allow for system extensibility without modifying existing Use Cases.

Creating an Extend Relationship

To create an Extend Relationship in Modeldraw's Use Case Diagram:

  1. Select the Extend Relationship tool from the toolbox.

  2. Click on the extending Use Case (the one that provides the optional behavior).

  3. Move your mouse to the base Use Case (the one that may be extended).

  4. Click on the base Use Case. An Extend Relationship arrow will appear, pointing from the extending Use Case to the base Use Case.

  5. The relationship will be automatically labeled with the «extend» stereotype.

An Extend Relationship