Use Case Diagram A use case describes how a user uses a system to accomplish a particular goal. A use case diagram consists of: • The system. • The related use cases. • The actors. Relates these to each other to visualize: what is being described? (System), who is using the system? (Actors) and what do the actors want to achieve? (Use cases), thus, use cases help ensure that the correct system is developed by capturing the requirements from the user’s point of view. <<Include>> in use case diagram The include relationship adds additional functionality not specified in the base use case. The <<Include>> relationship is used to include common behavior from an included use case into a base use case in order to support the reuse of common behavior. <<extend>> or <<exclude>> in Use Case Diagram The extend relationships are important because they show optional functionality or system behavior. The <<extend>> relationship is used to include optional behavior from an extending use case in an extended use case. In Summary: To represent complex relationships between different use cases, we can use the extend and include relationships. • Extend relationship: The use case is optional and comes after the base use case. It is represented by a dashed arrow in the direction of the base use case with the notation <<extend>>. • Include relationship: The use case is mandatory and part of the base use case. It is represented by a dashed arrow in the direction of the included use case with the notation <<include>>.
Use Case Diagram
A use case describes how a user uses a system to accomplish a particular goal.
A use case diagram consists of:
• The system.
• The related use cases.
• The actors.
Relates these to each other to visualize: what is being described? (System), who is using the system? (Actors) and what do the actors want to achieve? (Use cases), thus, use cases help ensure that the correct system is developed by capturing the requirements from the user’s point of view.
<<Include>> in use case diagram
The include relationship adds additional functionality not specified in the base use case. The <<Include>> relationship is used to include common behavior from an included use case into a base use case in order to support the reuse of common behavior.
<<extend>> or <<exclude>> in Use Case Diagram
The extend relationships are important because they show optional functionality or system behavior. The <<extend>> relationship is used to include optional behavior from an extending use case in an extended use case.
In Summary:
To represent complex relationships between different use cases, we can use the extend and include relationships.
• Extend relationship: The use case is optional and comes after the base use case. It is represented by a dashed arrow in the direction of the base use case with the notation <<extend>>.
• Include relationship: The use case is mandatory and part of the base use case. It is represented by a dashed arrow in the direction of the included use case with the notation <<include>>.
Step by step
Solved in 2 steps with 1 images
