Hello everyone welcomes to Master2Teach step-by-step guide in this video
we are going to learn how to check the use case diagram whether it's correct or
not I will try my best to explain step-by-step if you haven't subscribed
to our channel please click on the subscribe button and subscribe to our
YouTube channel okay let's start use case diagram simply use case diagram
shows a system or application people or organization or other that interact with
the system it is a very high-level diagram and typically it won't so a lot
of details but it's a great way to communicate a complex idea in a fairly
basis way we have already learn what is use case diagram different elements of
use case diagram how to draw use case diagram what is high-level use case
description and how to write it what is expanded use case description
and how to write it including an alternative on it also we have gone
through the use case diagram example if you haven't gone through the previous
use case to do tutorial please find the link above or in the description below
from the previous tutorial we have learn how to start drawing use case
diagram now let's learn how to verify it in this tutorial in use case diagram
only mention on the functional requirement of the system the functional requirement
like check balance transfer fund make payment etc check if there are any
non-functional requirement in the use case or not non functional requirement
like speed of execution memory consumption user friendliness etc use
case is denoted by the oval shape while drawing in the paper make sure to write
the use case name before drawing an oval shape because the size of the oval shape
may not sufficient power use case name and also make a list of use cases and
its respective actors before drawing the use case diagram the use case name is
usually an active verb and a noun phrase for example check balance
transfer fund make payments display an error message
verify login details etcetera check the use case names properly whether
it's an active verb and our noun phrase or not also make sure the name of the use
case is meaningful all the used cases should be inside the
system which is represented by a rectangle box so that only at the end of
design system box should be closed 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 case in a logical order where possible like
login then book service after that make payment because users will call
these use cases 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 steps like this which will looks more clear and attractive
try to maintain the position of use cases in proper shapes inside the system
box so that no need to overlap the lines while drawing the relationship between
the actor and the use cases check if there is any overlap and can be fixed by
repositioning the use cases or actors in use case diagram try to include at
least one include relationship like login and verified login use case the
included use case is a use case which is automatically called from the system
whenever the base use case is executed here log in is the base used 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 a line between the actor and the included use
case check whether there is a line between the actor and the included use
case or not if there is a similar use case that is also accessible by the
actor for example transfer fund use case has include relationship with the
check balance use case here whenever the actor called the transfer pond use case
the check balance use case is automatically called by the system
internally but there is also a requirement that the user can check
balance as well in this scenario make a different use
case like check user balance where actor and the use case check user balance
relationship exists don't mentioned the minor functionality use case as include
relationship use case which may leads the diagram miss the simpler your
diagram the better when producing a use case model always keep in mind what you
are trying to portrait and for what proposed the include relationship is
shown by the dotted line with arrow an arrow must point to the included use
case from the base use case and add a label include like this
whether include relationship arrow pointed to included use case or not
and is arrow label with include are not similarly include at least one extend
relationship in the use case diagram like login and display error message
extended use case may or may not call when the base use case is executed here
login is a base use case whereas the display error message is an extended use
case same as in include relationship the extended use case is called
automatically by the system if the condition matches so that there doesn't
exist any relationship with the actor so make sure there doesn't exist any line
between the actor and the extended use case check whether there is a line
between the actor and the extended use case or not the extend relationship is
shown by the dotted line with arrow similar to the include relationship but
the arrow must point to the base use case from the extended use case which is
just opposite of include relationship and add a label extend like this check
whether extend relationship arrow pointed to base use case or not
and is arrow level with extend or not also more than one use case can extend
the same extended use case only if the function needs to execute for both use
case are the same otherwise make a different extended use case for each for
example the login base use case extends the display error message use case and
also the payment use case also extend display error message here different use
case extends different use cases so separate the extended use case like
display login erode and display payment error check whether more than one base
use cases extends are includes the same extended or included use case carefully
make sure to include at least one generalization in the use case diagram
generalizing is also known as inheritance generalization is showing
the relationship between the parents and the child use case relationship
in simple word generalization is showing the type of actor are used case in the
system for the generalization relationship draw a solid line with an
arrow from the child use case or actor through parent use case or actor make
sure there doesn't exist any label in there for example the system has new
customer as well as old customer which can be shown in generalization like this
let's see another example of generalization of use cases payment use
case the system has a different methods of payment like PayPal MasterCard Visa
Card which can be shown in generalization
this check whether the use case diagram contains any generalization or not based
to so the generalization in actor as well as in use case check whether the
arrow is solid line with an arrow pointing towards parent actors or parent
use case or not also confirm that it doesn't exist label in arrow there is
one another type of notation which is extension point extension point are just
a detailed version of extended relationship and also can be shown in
note what sort of condition would lead to these extension points if possible so
at least one extension point in the use case diagram the actor is representing
by the human stick image anyone who used to perform a certain functions in a
system is actor actor maybe someone or something that can be a person an
organization another system machine or any external device so who or what is
going to use our system is a actor like costumer staff admin bank student
teacher etc make sure to represent all actor with a human stick image even for
the machine external devices and also contain at least more than one actor in
the use case diagram there are two types of actors primary actors and the
secondary actors a primary actor initiate the use of the system while the
secondary actor is more reactionary in other simple words primary actor request
something to the system and the secondary actor responds to the primary
actors primary actors should be position in the left of the system whereas
secondary actors are placed on the right side of the system
check whether primary actors are shown in the left side or not
similarly secondary actors are on the right side or not for detail please go
through my previous video tutorial where you can find step by step process with
details on use case diagram now let's move forward if there is any automatic
job going use case in the application like if customer didn't use their ATM
card for more than three months system will send an alert message to the
customer in these kinds of automatic stop use case actor as system is
represented with human stick image and so relationship with the use cases check if
there is any automatic job going use cases in the system or not moving forward
system the project that you are developing is a system the system is
representing a rectangle shape where the system name is written inside the top of
the system the rectangle shape helps to define the overall scope of the system
that you are going to develop so that everything that the system does jobs
place inside the system whereas anything outside the rectangle doesn't happens in
the system 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 the top or not while drawing use case diagram in a
paper make sure you have lift good margin in left side and right side of
the box cause you have to draw actors over there and close the system or box
at the end after drawing use case diagram
cause we are unknown about how much space do de use case will cover note
that even complex system should be restrict to a simplistic visualization
of functionality behavior and relationships so try to make a simple
clear meaningful design here are the list of checklists which you need to
check once more check if there are any non-functional requirement in the use
cases check the use case name properly whether it's an active verb and a noun
phrase or not check whether all the use cases are inside the system box or not
check the use case are in the logical order or not check if there is any
overlap and can be fixed by repositioning the use cases or actors
check whether the use case diagram contain at least one input relationship
or not check whether there is a line between
the actor and the included use case or not check whether include relationship
arrow pointed to the included use case or not and is arrow label with include
or not check whether the use case diagram contains at least one extend
relationship or not check whether there is a line between the actor and the
extended use case or not check whether extend relationship arrow pointed to
base use case or not and is arrow level with extend or not check whether more
than one base use case extends or includes the same extended or included
use case carefully check whether the use case diagram contains any
generalization or not check whether the arrow is solid lined with an arrow
pointing towards parents actor or parents use case or not also confirm
that there doesn't exist all label in arrow
if possible show at least one extension point in the use case diagram make sure
to represent all actor with human stick image even for the machine external
devices and also contains at least more than one actor in the used case diagram
check whether primary actor are shown in the left side or not
similarly secondary actors are on the right side or not check if there is any
automatic job going use case in the system or not make sure there is only
one rectangle box representing as a system where they're all the use cases
are included inside the box and actors are outside of the box or not check
whether you have written the system name inside the box at the top or not
I hope you learn from this video tutorial if you have any questions or
comments please make sure to leave a comment in the comment section below
also please be sure to like this video and subscribe to my channel if you
haven't already thank you very much for watching check us out for more it
tutorial and guide on website master2teach.com and we will see you again
soon bye