Up next in 10
UML - OOA steps on the ticket vending machine (TVM)
Show More Show Less View Video Transcript
0:01
object-oriented analysis steps on this
0:04
ticket vending machine yesterday so in
0:08
the next two videos this video and the
0:10
next video we're going to discuss the
0:12
steps and next one or these steps that
0:15
is object-oriented analysis what are the
0:18
steps we are going to follow here and
0:19
next video will be discussing the
0:22
object-oriented design steps on this
0:24
respective case study on ticket vending
0:27
machine so now we are having the step
0:30
number 100 a step number one that is
0:33
identify the actors so actors in TVM
0:37
that is a railway reservation system
0:39
we're having primary actors are the
0:42
passengers and secondary actors are the
0:45
operators and system administrators we
0:48
know that all those actors will initiate
0:50
some useless actors will initiate some
0:53
functional requirement of the software
0:56
so step number one will be identified
0:59
actors so we have defined two types of
1:01
actors one as a primary actor they are
1:04
nothing but the passengers and secondary
1:06
actors they are nothing but the
1:07
operators and system administrator now
1:12
we are going for the Oh a step number
1:15
two object-oriented analysis step two
1:17
that is developed the business process
1:20
model so here we shall draw one state
1:23
chair diagram with this initial state
1:26
and this final state and here in this
1:28
case we were just describing what are
1:31
the different states are possible so now
1:33
here you see we're having the TVM
1:35
management includes update and
1:38
maintenance of master files check
1:41
masters files and ticket and cash
1:44
management so it will be done by this
1:47
DVM that is a ticket vending machine
1:50
management includes so it is a purpose
1:52
of the it is a operations to be
1:54
performed by the management now here we
1:57
are having this carry out one of the
1:58
operators activities so what are the
2:01
lists of operated activities operated
2:03
activity can carry out any one of them
2:05
or multiple of them so summary report
2:08
generation get cache details withdraw
2:12
and deposit
2:12
- etc so from where we are getting all
2:15
this from the problem statement please
2:18
watch the previous video where you have
2:20
discussed the problem statement from
2:21
there we are developing this business
2:24
process model next one carry out one of
2:27
the passenger activities so now these
2:29
are the activities one of the activities
2:31
or multiple activities that passenger
2:33
can carry out there is a buy and
2:35
purchase tickets specify ticket details
2:38
and etcetera so this is our business
2:42
process model which has to be developed
2:44
in a step number two now we are going
2:48
for the next steps right now so let us
2:51
go for the Oh step number three and here
2:54
we shall go for the use case diagram and
2:57
the respective documentation so this is
2:59
our use case diagram and from the
3:01
Business Process Model web develop this
3:03
use case diagram so here is the system
3:06
boundary you can find that this is the
3:07
system boundary and this passenger this
3:10
operator and the system administrator
3:12
there external to the system boundary
3:14
but they are initiating the respective
3:16
use cases we know that actors may not be
3:19
always a human being may be some
3:21
applications either working within the
3:24
environment or within this system
3:26
boundary or from the outside of the
3:27
system boundary some application may be
3:29
one actor and human beings are always
3:31
men might be treated actors here so
3:34
identified their actors we that was my
3:37
step number one okay step number one so
3:40
there we had the primary actor that is a
3:43
passenger and two secondary actors they
3:46
are nothing but operators and system
3:48
administrators so these are the
3:50
operations these are the use cases there
3:53
is a functional requirements can be
3:54
initiated by this operator and this this
3:57
are the two use cases that can be
4:00
initiated by the system administrator so
4:03
that is about use case now what about
4:05
the documentation so please count that
4:07
how many use cases you are having here
4:09
just go on counting you are having eight
4:11
use cases so in the documentation we are
4:14
going to write their respective purposes
4:16
for more detailing so that a
4:18
documentation part will be following
4:20
next so we have written this
4:22
documentation in this order okay so two
4:26
use cases will be invoked by this
4:27
passenger then for use cases will be
4:30
invoked by this operator and these two
4:33
use cases will be initiated by these
4:36
system administrators okay
4:38
now specify ticket details so initiated
4:41
by the passenger and gives the following
4:44
details that is the destination place
4:46
place of journey and we're having the
4:48
passenger details number of errors
4:50
number of children and coach details and
4:53
and other details etc so this is the
4:56
specified ticket details which will be
4:58
initiated by the passenger captor next
5:02
one is a buy ticket so initiated by the
5:05
passenger to buy a ticket the passenger
5:07
pays cash and process accept cash button
5:10
and press s rather presses accept cash
5:13
grab button so that is one button is
5:14
there accept cash so he or she will
5:17
press that one and the system checks out
5:19
the cash and prints out the ticket and
5:22
dispense the balance if any and then
5:25
system also updates the records to
5:27
reflect the number of tickets to each
5:29
destination the total cash collected and
5:32
the total cash dispensed and the current
5:35
balance etc so that is the buy ticket so
5:39
next one will be the summary report and
5:42
it will be initiated by the operator so
5:44
see we are going for this summary report
5:46
right now so now this is my summary they
5:49
put initiated by the operator to know
5:51
the summary of the total business
5:53
transaction transacted for the day and
5:56
the cash collected and balanced cash
5:59
available in the system so that is our
6:02
summary report okay now other three
6:05
operations other three use cases will be
6:08
initiated by this operator so get cash
6:11
details initiated by the operator to get
6:13
a denomination wise number of nose and
6:17
coins available with the Machine at the
6:19
time the operator connects from a remote
6:22
place to the vending machine to get cash
6:24
details next one is the withdraw cash so
6:28
initiated by the operator to withdraw
6:30
cash from the machine the operator
6:32
connects to the machine locally and the
6:34
machine dispenses cash next one is the
6:38
last of uses
6:39
initiated by the operator is a deposit
6:42
cash initiated by the operator to
6:44
deposit cash in the machine the operator
6:46
connects to the machine locally and
6:48
specifies the amount to be deposited
6:51
with the denominations details so this
6:54
are the for use cases initiated by the
6:57
operator so if we go back to the
6:59
previous slide you can find that the
7:02
system administrators they are supposed
7:04
to issue or initialize these to use
7:07
cases check master files and update
7:10
master files so let me come to that
7:11
check master file initiated by the
7:14
system administrator system
7:16
administrator can login from a remote
7:18
place and check the details of the
7:20
machine ID user ID password and ticket
7:23
balance details we're having this update
7:26
master files initiated by the system
7:28
administrator to update system leaders
7:30
so this is my documentation and
7:33
previously we have discussed what is the
7:35
use case diagram so here we are having
7:38
this official and this is the concrete
7:41
actor so from there we're having this
7:44
this is the abstract actor rather so
7:46
from there we are having these concrete
7:48
actors so here we are having this
7:49
operator and system administrator so
7:52
this is a symbol it is indicating that
7:54
there is an abstract actor and these two
7:57
are the concrete actors so it is
8:00
actually depicting the inheritance or
8:02
the generalization now if this
8:06
documentation is being continued here
8:08
so by ticket include pay cash and also
8:11
include the dispense balance so these
8:15
are the other use cases which will be
8:17
initiated when this buy ticket initial
8:20
well this use case will be initiated
8:21
here so specified ticket extends specify
8:25
a return ticket and specify ticket to so
8:28
in this way so there is a extend so here
8:31
also we are getting this this one as the
8:33
as the abstract use case and these are
8:36
the concrete use cases we are getting
8:38
this extends their extent is indicating
8:40
that it is a case of generalization so
8:43
here we are having this include option
8:45
and here we're having this extend option
8:48
so we have covered up to step number
8:51
three what was the step number
8:53
identify the actor what was a step
8:56
number two that is that developed the
8:58
business process model what was the step
9:01
number three that was a design all the
9:05
use cases and the respective
9:07
documentation so now we are going for a
9:10
object oriented analysis step number
9:13
four and five so develop interaction
9:16
diagrams what are the Indian
9:17
introduction diagrams we're having two
9:19
diagrams are there one is a sequence
9:20
diagram another one is the collaboration
9:22
diagram and identify the objects and
9:25
develop static class diagram we know
9:27
that this class diagram object diagram
9:29
they are the they are providing the
9:32
static view of the system so now we are
9:35
going for that part so that is our step
9:37
number four and five so at first we are
9:40
going for this noun phrase approach that
9:43
is a very famous approach and here you
9:45
see identify object classes in TVM
9:48
railway reservation system is obtained
9:51
from the recommend as candidate classes
9:54
so here from the very problem statement
9:56
which we add in the earlier video of
9:58
this divyam yesterday from there we have
10:01
listed that respective nouns there so
10:04
fewer details front panel ticket
10:07
passenger railway stations so all these
10:10
nouns were there in their respective
10:11
problem statement so these nouns have
10:14
got filtered out and they are put listed
10:16
here the candidate classes above are
10:19
refined and the redundant Idul event
10:22
vague attribute and the operational and
10:26
implementation classes are removed from
10:28
the set is defined so now let us go for
10:32
the processing of this extracted nouns
10:34
from the problem statement so to have
10:36
the better idea on this let us go for
10:38
the next slide so now here we going for
10:41
this redundant class so redundant
10:44
classes are we here we are having this
10:46
requested ticket liquidation slip ticket
10:48
details and ticket cash details and cash
10:51
so chosen requisition slip ticket and
10:54
this cash flow form here we have we have
10:57
just we have taken them only we have
11:00
chosen them there is an equalization
11:01
slip ticket and the cash here we are
11:04
having the real media event class
11:06
so that is a passenger and been vague
11:08
classes that is a tenuous station
11:10
activate classes that is a fair balanced
11:12
amount destination number of medals
11:14
number of children machine ID user ID so
11:17
these are the attribute classes and
11:19
implementation will be the TVM and the
11:22
right classes after refinement our
11:24
ticket front panel cache report debit
11:29
note requisition slip the note coin and
11:33
this is affair details so these are the
11:36
right classes where we are selecting
11:38
after refinement so this is a very
11:41
important step there is a very important
11:44
steps and from here we can get the class
11:47
names from here we will be getting the
11:49
attributes which are going to be defined
11:51
under the classes so that the process is
11:54
known as noun phrase approach so here
11:59
let us go for the sequence diagram we
12:01
know that we are having two interaction
12:02
diagrams one is a sequence diagram and
12:04
the one is the cool operation diagram so
12:06
here you can generate here we are having
12:08
this respective sequence diagram we know
12:10
that in case of sequence diagram these
12:12
are the timeline these are the
12:14
activations and these are the objects we
12:17
are having so passenger front panel
12:19
ticket trans actors and requisition slip
12:21
and the fare calculator these are the
12:23
objects we are having and this is the
12:25
required sequence diagram which is in
12:27
front of you we're having a separate
12:29
chapter on the sequence diagram please
12:31
watch all the videos under their
12:32
sequence chapter a single diagram
12:34
chapter to have a better understanding
12:35
on this diagram so here we are having
12:39
the pool operation diagram from the
12:40
sequence diagram we can move to the
12:41
collaboration diagram this collaboration
12:43
diagram is in front of you and here this
12:45
messages have got numbered you can find
12:47
the messages have got numbered
12:49
automatically the in the collaboration
12:51
diagram the messages will get half the
12:52
number so this collaboration diagram and
12:54
sequence diagram these two diagrams are
12:57
falling under the diagram interaction
12:58
diagram
13:00
so this is a sample class diagram we are
13:02
having there is a sample class diagram
13:04
so here we are getting the concept of
13:07
inheritance so these are cash so cash
13:09
can be of two types one is a note
13:11
another one is a coin
13:12
so denomination denomination will be the
13:14
respective properties so attributes and
13:18
caches have having that denomination so
13:20
that is this particular denomination is
13:22
getting inherited here and here we are
13:25
having there decussation sleeps and
13:26
these are the respective attributes what
13:28
have been and from this equation sleep
13:30
we're having this ticket related and
13:32
this reports are getting related with
13:35
this printer and this is the
13:36
generalization again even finding so
13:38
dippel's can be of the summary table is
13:40
on the receipt and then the on the debit
13:43
note or reports can be can be created so
13:46
this is a respective class diagram
13:48
sample class diagram on this TPM so in
13:51
this particular video we have discussed
13:53
our Oh a step number 1 then 2 then 3 and
13:58
then 4 and 5 so now in the next video we
14:02
are going 400d that means
14:04
object-oriented design so analysis part
14:07
has got completed now let us go for the
14:09
designing part so please watch the next
14:11
video that will be in the continuation
14:13
of this one and thanks for watching this
#Business Operations
#Business Plans & Presentations
#Management
#Business Services
#Retail Trade
#Retail Equipment & Technology
#Programming
#Warehousing