Home | Sign in | English EN
  • Overview
  • Elements of use case diagram
WindowsLinuxUniversal Windows 10 AppJavaReports and QueriesUser code (UMC)
WindowsLinuxPHPWEBDEV - Browser code
AndroidAndroid Widget iPhone/iPadApple WatchUniversal Windows 10 AppWindows Mobile
Stored procedures
A use case diagram is used to view the behavior of a system in such way that:
  • the user can understand how to use each element.
  • the developer can implement these elements.
For example, the behavior of a cell phone can be described via a use case diagram.
Elements of use case diagram
A use case diagram includes the following elements:
  • Actor: represents the role of application users. For example, a person who works in a bank will be the loan manager. If this person has an account in this bank, he will also play the role of Customer.
  • Use case: describes a sequence of actions run by the application. For example, Place an order, Enter an invoice, Create a new Customer entry, ...
    A use case describes the actions performed by an application but it does not specify how the application performs these actions.
  • Relationship: describes the behavior of actors in relation to the use cases. Three types of relationships are available:
    • Association: Structural relationship between two linked elements.
    • Dependency: Relationship establishing that an element uses another one. For example, a bank customer may get cash from an ATM. In this case, the Get Cash action depends on the Customer.
      In order to get cash, the Customer must enter his PIN number. In this case, the Get Cash action depends on the Password Input.
    • Generalization: Relationship used to organize the elements according to a hierarchy.
      For example:
      - two types of Customer actor are available: Individual Customer or Enterprise Customer.
      - the identity check can be performed according to two different methods: type a password or check a fingerprint.
  • Package: divides and organizes the diagram representation (like the directories organize the files). Each package can contain actors and use cases.
See Handling a use case diagram for more details.
Minimum version required
  • Version 9
This page is also available for…
Click [Add] to post a comment