Usecase Diagram
Overview
Use case diagrams can be used to describe the behavior of the system in response to user requests. This page describes the operations for using the use case diagram in the following order.
- Place a use case diagram
- Define use cases
- Define actors
- Define associations
Place a use case diagram
To place a use case diagram, do the following:
Operation procedure
- Select a package in the model navigator and click Add Model> Usecase Diagram in the context menu.
- The use case diagram is placed on the child elements of the selected package.
Define use cases
To define a use case, do the following:
Operation procedure
- Drag and drop [Use case] from the toolbox to the displayed use case diagram.
- A new use case is added as a sibling element of the displayed use case diagram.
Elements that can be added from the toolbox
You can add the following elements displayed in the toolbox in the Use Case Diagram.
Icon | Name |
---|---|
Package | |
Use case | |
Actor | |
Note | |
Labels | |
Shape |
Add stereotypes to use cases
tip
If you want to display an existing use case on the use case diagram, you can display it by dragging and dropping the use case on the model navigator to the use case diagram.
Define an actor
To define an actor, do the following:
Operation procedure
- Drag and drop Actor from the toolbox onto the displayed use case diagram.
- A new actor is added as a sibling element of the displayed use case diagram.
Define associations
To define the association, do the following:
Operation procedure
- Move the pointer over the use case you want to associate.
- Drag the [โฒ] icons that appear on all sides of the use case and drop them on the other use case.
- A list of associations that can be added will be displayed. Select the association you want to add, and the selected association will be added.
Related that can be added
The following associations are available in Use Case Diagrams:
Icon | Name |
---|---|
Actor related | |
Dependencies | |
Inheritance |
Add stereotypes to associations
tip
If you want to express inclusion or extension, define the dependency association and use the stereotype of that dependency to express it.
Restrictions
- You cannot define extension points for use cases.
- Substitute the system boundaries with packages.