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

Generalization

PreviousSystem BoundaryNextInclude Relationship

Last updated 7 months ago

A Generalization in Modeldraw's Use Case Diagram represents a relationship between Actors where one Actor (the child) is a specialized version of another Actor (the parent).

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

  • Show inheritance relationships between Actors

  • Represent hierarchies of user roles or types

  • Illustrate shared characteristics and behaviors among different Actors

  • Simplify diagram complexity by grouping common associations at the parent Actor level

  • Model specialized versions of general Actor types

Understanding Generalization

A Generalization in Modeldraw's Use Case Diagram tool is typically represented by a solid line with a hollow arrowhead pointing from the child Actor to the parent Actor. Key points to understand about Generalizations include:

  • In Modeldraw, Generalizations can only be used to connect Actors, not Use Cases.

  • The child Actor inherits all the associations and characteristics of the parent Actor.

  • The child Actor is a more specialized version of the parent Actor.

  • An Actor can be a child of multiple parent Actors, inheriting from all of them.

  • Generalizations can help simplify diagrams by allowing common associations to be shown only for the parent Actor.

  • Generalizations allow you to create multi-level hierarchies of Actors.

Creating a Generalization

To create a Generalization in Modeldraw's Use Case Diagram:

  1. Select the Generalization tool from the relationship toolbox.

  2. Click on the child Actor (the more specialized Actor).

  3. Move your mouse to the parent Actor (the more general Actor).

  4. Click on the parent Actor. A Generalization arrow will appear, pointing from the child to the parent.

A Generalization use in modelling user roles