Use Case Diagrams Tutorial for Business Analysts | Commonly Used Business Analyst Use Cases

[Music] hello everyone this is george from invensis learning with yet another session on business analysis welcome to our youtube channel understanding verifying and communicating user requirements can be a daunting task for business analysts so what's the solution modeling requirements with the help of use case diagrams so what exactly are use case diagrams that's the topic for today no let us quickly go through the agenda we will begin by discussing what a use case diagram is then we shall look into the history of use cases moving on we will touch on why use cases are important next we will discuss the different types of use cases later we will talk about how a use case helps a business analyst then we shall see the various components of use cases and wrap up the session by looking at real-time examples of use case diagrams i hope the agenda is clear to you guys let's get started then so what exactly is a use case diagram before i start defining use cases let us consider a situation where a customer needs to buy a product from the shop he has a facility to use coupons to avail the discounts the customer also has an option to choose an additional product along with it so cool right viewing from a business perspective this scenario can be broken down into multiple features or stories which can be represented with a use case diagram few use cases that came into picture in the given situation are buying a product using discount coupons availing discounts choosing additional product now why are these called use cases this is because a use case represents an interaction or a functionality of the system those points which i mentioned as use cases are also the functionalities a user is performing to reach his or her intentions let me now define the use case so that you can understand even better the use case is a set of sequences of interactions between systems and users in the system that helps to reach a particular destination they are the textual and visual representation of a user's behavior they specify the expected behavior but not the exact method of how a user may react use case modeling is a method that describes what a system will do it focuses on the users of the system and its needs as a use case consists of narrative text and is easily understandable by all stakeholders now how did the concept of use case diagrams come into existence let's take a trip into the history of use case diagrams shall we in the mid-1990s uml emerged as a combination of three methods that is booch oose and ont booch is a method for object-oriented software development it is made of an object modeling language object-oriented software engineering is a software design technique that is used in software design using object-oriented programming the object modeling technique is a modeling technique used for software modeling and designing this allowed the developers to rely on a system that had stability and predictability in 1996 the object management group asked for ibm microsoft and oracle to create a modeling language then software engineers like grady booch ivar jacobson and james rumbaugh of rational software invented uml during 1994 and 1995. it was under development until 1996. later their combined efforts made uml 1.0 this quickly gained a standard and gradually got updated moving on why are use cases important what should you use them for before knowing the advantages and benefits of using a use case let us consider an example of a bank where a customer wants to deposit money generally before depositing the money you must have an account if not you must open an account in that particular bank to do this the customer takes the help of a bank employee and opens a new account once the account is open he then deposits the money by seeing the above use case example you can easily notice certain advantages and benefits of use cases the primary advantage of use case modeling is that it helps in designing a system from the user's perspective it is the best technique for communicating system behavior in the user's terms through external action every use case defines one way the system is used use cases can be used in various software development streams including project planning implementation documentation test cases etc another advantage of use case modeling is that it also indicates all of the things that might go wrong this saves a lot of time for the analysts now let us look into some of the benefits of use cases as you have already seen an example you can easily say that a use case is easy to capture the functional requirement it is easy to write read and understand use cases help in fulfilling the user demands demands of the stakeholders are considered while writing a use case now you guys have an idea of what use case diagrams are and why they are important there are different types of use cases let us discuss them use cases can be described both in a textual and visual format likewise it can be divided into business and system use cases now let's understand both of them in detail business use case a business use case is also known as an abstract level use case this is because it is written in an abstract level written in a high-level business process which means that it is explained in a technology agnostic manner it involves a sequence of actions that the business process will involve that is sequences of different functions can be found it gives an observable result that can be easily understood system use case a system use case is also known as an implementation use case this use case is written at a lower level of detail compared to that of a business use case hence it is a low-level business process it includes specific processes that will be carried in a process as it mainly concentrated to achieve the task effectively it explains the end-to-end process to tell ui in simpler words eat food becomes a business use case whereas eat food before it gets cold becomes a system use case normally many professionals will start writing the use case with high-level language and continue with the low-level language now we shall see how use case diagrams help business analysts the use case diagram is an essential technique used by a business analyst to deal with the businesses scope and functional aspects they usually write use cases to build the gap between themselves and the it department to provide technical solutions use cases are employed during several software development stages like creating planning validating testing the user manuals a use case document helps the development team to identify and understand where errors are found these allow the developers to understand the actual system design flow that to be followed while creating a solution an analyst requires the use case diagram to correct the final stage of the project technically getting the original functional requirements right using the uml use case diagram with a business is essential for business analysts analyst supply use case modeling for the following reasons create the requirements verify the systems models the goals of the system focuses both on the user system and real-time system now let us go through the various use case components a use case is a process of how a person uses that system it is associated with software systems let me take an example of a school that is publishing the student's results on the website keeping this example i shall explain to you the different components of a use case the first one would be an actor in general an actor may include a single user or a group of people the machines and the external organizations to the system they are the ones who must interact with the system in this particular example the actors are teachers an admin who uploads the results to website student the next use case component is the system in simpler words system involves the process that helps in reaching the result the system is always enclosed within a boundary and the different stages are present within the limitation itself inside a system different use cases are mentioned which are enclosed in an oval shape as you already are familiar with the use cases it's easy to identify them so the use cases would be admin uploading the results into the website teachers verifying the uploaded details students log in students entering the user id and password students checking for the results the next use case component is the goal this represents the required outcome in our example getting the result would be the goal we have already seen some of the use case components those are the essential ones along with that some additional components must be included in a use case now we shall discuss them additional elements that a use case can have are the first component would be stakeholders stakeholders may be a person or group of people interested in knowing the systems process in our case the school is a stakeholder preconditions are the next use case component we must consider before writing any use case these are the external aspects that must be confirmed before a use case is processed in our example proper system connection becomes the precondition post conditions describes the state of the system at the conclusion this is another component present in a use case in this particular case mailing the student after entering the right user id and password becomes the post conditions business rules are another use case component they are the functional rules that govern the environment where the process flow takes place in the mentioned example students must log in only between 9am and 2pm becomes the business rule now to make you understand clearly about the term use cases let us consider an example and then explain it to you by showing you a use case demo now to make you understand clearly about the term use cases let us well let us consider a movie ticket reservation system firstly while understanding a use case it is required to identify the different use case components and their part functionality once this is known understanding becomes easy as i have already told you the system should be enclosed within a boundary as shown secondly who all can be the actors so generally actors are visually represented using a person for this movie ticket reservation system we can include a customer who is willing to watch a movie maybe one or many the owner who has the authority to either allow or deny the customers based on the ticket he checks the gateway admin who collects money to generate the ticket or to refund money and cancel the ticket an administrator who is responsible for uploading the movie into the database and the last actor is the canteen owner who would provide the essentials which asked by the customers well now i think you are clear with actors now we shall focus on the central concept that is use case so as already mentioned you say cases are represented using oval shapes the use case scenario is a single relationship between a use case and an actor the first use case would be the admin loading the movie details into the database in this stage the administrator will check for the new movies which are currently present after that he has to reach the movie operator and get the required details after he is sure that the received copies are perfect he will upload the details the next use case includes booking a ticket firstly the customer comes into the picture then he must select a particular language he is interested in after that he will choose a specific movie which he needs after this he can book the ticket after choosing the movie the customer must confirm the number of seats this depends on the customer sometimes the booking may be filled and there would be no enough seats that a customer would be looking for during that time he won't be able to select that number of seats this becomes the third use case later on the customer would have permission to select the seat slots this may include golden slots silver slots and platinum slots he can also choose seats row wise like the front panel back panel or middle panel this becomes another use case once a seat is selected the customer would have an option to order the snacks along with the ticket this depends on the customer whether to either consider snacks or not if he or she is interested in having snacks he has to choose those items he is willing to if not he can skip this stage this becomes the next use case next the customer is required to pay the amount for this a customer can either have one or two bills depending on whether the customer chose snacks or not in the end both the payments are merged and would be shown to the customer after this for making the payment he or she would have an option to choose the payment methods the mode of payment may include net banking card payment paytm etc this is another use case once the payment is made a ticket is generated along with a food coupon the ticket generated would have all the details like movie name number of seats selected seat slot and also if a food coupon is present if a food coupon is present there also details are mentioned the details would be like the name of the food a number of food items ordered and the type of food after the details are mentioned this would be sent to the customer this is another use case sometimes the customer may have to cancel the ticket and the booking system also considers that once the request of cancellation of ticket is received then the gateway admin considers it then the admin asks the reason for the cancellation and accepts the requests accordingly this becomes the next use case the final use case would be to enter the cinema hall for this the customer has to show the ticket while entering the cinema hall during that time the owner checks for the details and if acceptable he allows the customers now you have seen all the use cases let us look into the relationship linked in every use case uploading to the database administrator and owner booking a ticket customer and administrator number of seats customer and administrator selection of seat customer and administrator snacks customer and canteen owner payment customer and gateway ticket generation gateway and customer ticket cancellation customer and gateway entry customer and owner well i think the demo gave you an idea about the use case so you would have understood that once a use case model is developed it drives many other software development aspects including project planning implementation test case definitions and user documentation to know more about this we at invensis learning will provide certification training courses for business analysis foundation and practitioner qualifications enroll now with invensis learning to learn from the industry's best and become a certified business analysis professional for more updates on trending technology subscribe to invensys learning youtube channel also if you have any queries share them with us in the comments section

Channel: Invensis Learning

Views: 54,773

Keywords: use case diagram, use case diagram business analyst, business use case diagram, business analysis use cases, use case diagrams in business analysis, business analyst user stories, business analyst training, business analysis training, types of use case diagrams, business analysis user stories, business analyst certification, business analysis certification, invensis learning

Id: 0TJ4GoSFbhs

Length: 15min 4sec (904 seconds)

Published: Tue Jan 12 2021