Please note : This help page is not for the latest version of Enterprise Architect. The latest help can be found here.

Use Case Diagram

Use Case diagrams capture Use Cases and relationships between Actors and the subject (system).

Use To:

  • Describe the functional requirements of the system
  • Describe the manner in which outside things (Actors) interact at the system boundary
  • Describe the response of the system.

Example Diagram:     Example Use Case Diagram

Tools:  Select Use Case diagram elements and connectors from the Use Case pages of the Toolbox. Click on the following elements and connectors for more information.

Use Case Diagram Elements

Use Case Diagram Connectors

e_Actor

c_Use

e_UseCase

c_Associate

e_testcase

c_Generalize

e_Collaboration

c_Include

e_collaboration_use

c_Extend

e_BoundaryBox

c_Realize

e_Package

c_Invokes

 

c_Precedes

Notes:

  • Invokes and Precedes relationships are defined by the Open Modeling Language (OML). They are stereotyped Dependency relationships; Invokes indicates that Use Case A, at some point, causes Use Case B to happen, whilst Precedes indicates that Use Case C must complete before Use Case D can begin.

Learn More: