Use Case Diagram

Use case diagrams are set of actions (use cases) that some system or systems should or can perform in collaboration with one or more external users of the system. Each use case should provide some observable and valuable result to the actors or other stakeholders of the system.

Use case diagrams are used to specify:
• requirements, required usages of a system under design or analysis to capture what the system is supposed to do.
• the functionality offered by a subject – what the system can do.
• requirements the specified subject poses on its environment by defining how environment should interact with the subject so that it will be able to perform its services.

Instructions in Creating the Artifact

This instructions are inetended to give you a better scope of what a good Use Case Diagram could be like rather than a sole resource for the artifact of your project. You may need to tailor it and make several other changes to ensure it is a good fit for your use and project. It is essential that the use case diagram show association between use cases and/or user stories from your previous artifacts.

Use Cases: These are system functionalities that are connected through relationships with other use cases and/or user stories or associations with different actors of the system(including external services like payment systems).
Actors: An actor is behaviored classifier which specifies a role played by an external entity that interacts with the subject, a human user of the designed system, some other system or hardware using services of the subject.

Examples of Use Case Diagrams

• Use Case Diagram from Team TOSS, Winter 2017
• Use Case Diagram from Winter 2017
• Use Case Diagram from Team MAPS, Winter 2018
• Use Case Diagram from Team QuaranTeam, Fall 2020

---