Use Case Diagram - Step by Step Checklist with Example

Video Description

USE CASE DIAGRAM: How to Check the use case diagram whether it's correct or not? Simply use case diagram shows a system or application, people or organization, or others that interact with the system. It’s a very high-level diagram and typically won’t show a lot of detail, but it’s a great way to communicate complex ideas in a fairly basic way. If you haven’t gone through the previous use case video tutorial https://www.youtube.com/watch?v=sQgoFjxSdxo In use case diagram, only mention the Functional requirement of the system. Functional Requirements like check balance, transfer fund, make payment.Check if there are any non-functional requirement use cases. Use Case is denoted by the oval shape. While drawing in paper, make sure to write the use case name before drawing oval shape. Because size of the oval shape may not sufficient for the use case name. And also make a list of the use cases and its respective actors before drawing use case diagram. Use Case name is usually an active verb and a noun phrase. For example: –check balance, transfer fund, make payment, display error message, verify log in details, etc. Check all the use case name properly whether it’s a active verb and a noun phrase or not. Also make sure the name of the use cases are meaningful. All the Use Cases should be inside the system which is represented by rectangle box. So that system box should be close at the end only if you are drawing use case diagram in paper. Check whether all the use cases are inside the system box or not. It’s good practice to put the Use Cases in a logical order where possible like login than book service after that make payment because user will call these use case on serial wise and easy to understand the flow of the system. Check the use cases are in logical order or not. Try to maintain the use cases in half circle shape like this which will look more clear and attractive design. Try to maintain the position the use cases in proper space inside the system box so that no need to overlap the lines while drawing relationship between the actor and the use cases. Check if there is any overlap and can be fix by reposition the use cases or actor. In use case diagram try to include at least one include relationship. Like Login and the verify login use case. Included use case is use case which is called automatically from the system whenever the base use case is executed. Here Login is base use case where as verify login is Included use case. Make sure that included use cases are called automatically by the system so that there doesn’t exist any relationship with the actors. Do not draw line between the actor and included use case. Check whether there is line between the actors and the Included Use Case. The Simpler your diagram, the Better. When producing a Use Case Model always keep in mind what you are trying to portray and for what purpose. The “Include relationship” is shown by the dotted line with arrow and arrow must point to the included use case from the base use case. Check Whether include relationship arrow pointed to Included Use Case or not and is arrow label with include or not. Make sure to include at least one generalization in the use case diagram. Generalization is also known as inheritance. Generalization is showing the relationship between the parent and the child use case relationship. In simple words, generalization is showing the type of actor or use case in the system. For the generalization relationship, draw a solid line with an arrow from the child use case or actor to parent use case or actor. Make sure there doesn’t exist any label in arrow. For example, the system has New Customer as well as Old Customer which can be shown in generalization as this. There is one another type of Notation which is Extension Points. The Actor is representing by the human stick image. Anyone how use to perform a certain function in the system is actors. There are two type of actors. 1. Primary Actors 2. Secondary Actors If there is any automatic job doing use case in the application like if a customer didn’t use their ATM card for more than 3 months, system will send an alert message to the customer. In this kind of automatic job use case, actor as system is represented with human stick image and show relationship with the use cases. Check if there is any automatic job doing use cases in the system or not. Make sure there is only one rectangle box representing as a system where all the use cases are included inside the box and actors are outside of the box.Check whether you have written the system name inside the box at top or not. SUBSCRIBE to our YouTube channel for more videos: https://www.youtube.com/c/Master2Teac... Like us on Facebook: https://www.facebook.com/master2teach For more content go to https://master2teach.com/ E-mail: [email protected]