Introduction to Use Case Models
A Use Case Models describes how a system interacts with outside actors.
It is a graphical representation of the interaction between the elements and system.
Each use case represents a piece of functionality that a system provides to its user.
Also, Use case identifies the functionality of a system.
Use case diagram allows for the specification of higher level user goals that the system must carry out.
Moreover, These goals are not necessarily to tasks or actions but can be the more general required functionality of the system.
You can apply use case to capture the intended behavior of the system you are developing, without having to specify how that behavior is implemented.
Also, A use case diagram at its simplest is a representation of a user’s interaction with the system and depicting the specifications of a use case.
A Use Case Models contains four components.
- The boundary, which defines the system of interest in relation to the world around it.
- The actors, usually individuals involved with the system defined according to their roles.
- The use cases, which the specific roles played by the actors within and around the system.
- The relationships between and among the actors and the use cases.
Purpose of Use Case Models
- The main purpose of the use case diagram is to capture the dynamic aspect of a system.
- Moreover, Use case diagram shows, what software supposed to do from the user point of view.
- It describes the behavior of the system from user’s point.
- Also, It provides a functional description of the system and its major processes.
- Use case diagram defines the scope of the system you are building.
When to Use Use Cases Diagrams
- Use cases used in almost every project.
- Moreover, They are helpful in exposing requirements and planning the project.
- During the initial stage of a project, most use cases should define.