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.
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:
The material ("material" includes all pages, documents and on-line graphics) on this web site is protected by copyright law. (C) 1998-2011 Sparx Systems Pty Ltd.