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

Include Relationship

PreviousGeneralizationNextExtend Relationship

Last updated 7 months ago

An Include Relationship in a Use Case Diagram represents a situation where one Use Case (the base Use Case) includes the functionality of another Use Case (the included Use Case) as part of its normal execution flow.

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

  • Show that a Use Case incorporates the behavior of another Use Case

  • Reduce redundancy by extracting common behavior into separate Use Cases

  • Simplify complex Use Cases by breaking them down into smaller, reusable components

  • Illustrate mandatory sub-flows within a Use Case

  • Improve the modularity and maintainability of your Use Case model

Understanding Include Relationship

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

  • The included Use Case is always executed as part of the base Use Case.

  • The included Use Case can be shared among multiple base Use Cases.

  • It helps in breaking down complex Use Cases into more manageable pieces.

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

  • The included Use Case is often named as a specific action or sub-process.

  • Include Relationships can help in hiding complexity and showing a higher-level view of the system.

Creating an Include Relationship

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

  1. Select the Include Relationship tool from the toolbox.

  2. Click on the base Use Case (the one that will include the functionality of another).

  3. Move your mouse to the included Use Case (the one whose functionality will be included).

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

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

An Include Relationship