Usecase Digram
Tutorial - Building a Use Case Diagram
1. Introduction
A Use Case diagram is a graphical representation of the high-level system scope. It includes use cases, which are pieces of functionality the system will provide, and actors, who are the users of the system. Looking at a Use Case diagram, you should easily be able to tell what the system will do and who will interact with it.
You can create one or more Use Case diagrams for a single system. If you create more than one, each will show a subset of the actors and/or use cases in the system. You can also group the use cases and actors into packages to help organise the model. Α Use Case diagram can be helpful in communicating with the end users of the system. It is designed to be straightforward and non-technical so that everyone on the team can come to a common understanding of the system scope. It is usually created by the technical team, but in conjunction with an end user representative.
To create a new Use Case diagram: 1. Right-click a package in the Use Case view. 2. Select New → Use Case Diagram. A Use Case diagram shows a subset of the use cases and actors in the system. You can create as many Use Case diagrams as you need to fully document the system scope.
2. Actors
An actor is a person, system, piece of hardware, or other thing that interacts with your system. It is denoted with a stick figure. We differentiate active actors, who initiate interactions with a system, and passive actors, who are targets of requests or who are activated by the system.
1
Follow these steps to add actors to the diagram: 1. Determine the actors for your system. 2. Select the Actor toolbar button. 3. Click in the Use Case diagram to add the actor. 4. Name the actor.
3. Use cases
A use case is a piece of functionality the system will provide. It is usually named in the format , such as "Deposit Check" or "Withdraw Cash." Use cases are highlevel and implementation-independent. It is denoted with a
1. Introduction
A Use Case diagram is a graphical representation of the high-level system scope. It includes use cases, which are pieces of functionality the system will provide, and actors, who are the users of the system. Looking at a Use Case diagram, you should easily be able to tell what the system will do and who will interact with it.
You can create one or more Use Case diagrams for a single system. If you create more than one, each will show a subset of the actors and/or use cases in the system. You can also group the use cases and actors into packages to help organise the model. Α Use Case diagram can be helpful in communicating with the end users of the system. It is designed to be straightforward and non-technical so that everyone on the team can come to a common understanding of the system scope. It is usually created by the technical team, but in conjunction with an end user representative.
To create a new Use Case diagram: 1. Right-click a package in the Use Case view. 2. Select New → Use Case Diagram. A Use Case diagram shows a subset of the use cases and actors in the system. You can create as many Use Case diagrams as you need to fully document the system scope.
2. Actors
An actor is a person, system, piece of hardware, or other thing that interacts with your system. It is denoted with a stick figure. We differentiate active actors, who initiate interactions with a system, and passive actors, who are targets of requests or who are activated by the system.
1
Follow these steps to add actors to the diagram: 1. Determine the actors for your system. 2. Select the Actor toolbar button. 3. Click in the Use Case diagram to add the actor. 4. Name the actor.
3. Use cases
A use case is a piece of functionality the system will provide. It is usually named in the format , such as "Deposit Check" or "Withdraw Cash." Use cases are highlevel and implementation-independent. It is denoted with a