UML - OOD steps on the ticket vending machine (TVM)

Object oriented design steps on the ticket vending machine

So in the previous video we have discussed what are the different steps in object

oriented ysis of this respective case study that is a TVM and prior to that

video we have discussed the problem statement. So in this video we are going to

show you are going to discuss on this object oriented design and what are the

different steps to be done in this TVM. In the object oriented ysis we do

the respective use case diagram we do the sequence diagram collaboration diagram and at the last we do the respective class diagram so now in this

case of object-oriented design the in this respective steps we shall be

drawing the component diagram the deployment diagram activity diagram structure diagram so let us go for the further details on it so at first

we're going to for the state chart diagram what is the state chart diagram state chart diagram will depict the change of states of one object in the system so here

you see this is a state chart diagram we are going to do so ready is the initial state

now request processing that is the generate request so request processing will be there

then accept cash then waiting for the confirmation then cash accepted balance processing and ticket

will be issued so here you were having this terminating state and here if there is some error then the balance error will come and again

it will be found in the ready state prior to this ready state I can also put

one starting state there so here this is a time out waiting for confirmation

for a certain duration of time for a certain time slice if the time has got

expired then the time out there will be there and then the state will be will

have the transition from the waiting for confirmation to the ready state

So this is a ticket purchase if you consider this respective object

So this is a straight transition diagram for it. We know that in case of real life projects there will be not a single structure diagram There will be multiple stretcher diagrams which will be required to denote the change of states of a certain object in the system

so now we are going for some sample codes for the to give the

guidance to the respective coder and developer so variables involved in the ticket transactor so type depth state

what are the states we are having one is the ready request processing wait for confirmation balance processing

and ticket issue. So these are the states we are having we've made one�p. That is an

enumeration here. So type dev event, what are the different event types? So there is a generate

request, accept cash, cash accepted timeout and the balance issued. Now we're having this

variables defined. So float fare, float cash deposited and float balance. So now we are going for

this. There is the different variables and the different enumerations which are required

for the tricket transactor. So C-do code for the event. So begin state is

equal to ready event handler colon switch event. So now we are having the

switch case statement depending upon the language in which we are going to

implement the respective syntax has to be followed here. So case generated

request colon so that is of one of the cases is that there call generate

request function and break. So case accept cash here call accept cache so there is a function to be called and then break so in this way

that is straight code has been written you can pause the video we can watch what are the

codes we have written here so pseudo code for the generate request so this is a

code for the generate request so if the state is not equal to ready then return error

otherwise state is equal to request processing and fear is equal to calculate the fear

from the requisition slip and return so this is the sample pseudo code for the better understanding here

So now in case of object-oriented design, we are now going for the implementation of the project

So that why the sample codes will help a lot for the developer to implement Next one is the code code for accept cash If state is not equal to request processing return error and then we having this

state is equal to wait for confirmation, issue deposit cash message to the cash

transactor and return. Now, this is our activity diagram. So in this particular activity diagram, here we're having this user ID

There is the initial state. we're having this user ID and enter the password if the password is not valid

invalid then again it will ask for the password entry and then if the password is

valid then it will come down to this choose type of report and then print the

report and then more report generation if it is required then it will go for the

choose the type of report that menu will come back again and otherwise report

generation will be completed and log out and that is a terminating state So this is known as the activity diagram

This activity diagram might be very much similar to your flowchard, but in the activity

diagram, respective chapter, you have discussed a lot that it is a flowchard, no issues

it is a flowchard. But this particular activity diagram is having some properties and features which are not

available in our flowchard. We can mention that which are the activities which can be executed in sequential fashion

in parallel, or maybe executing in a in a, swim lane so

this things we can mention in this activity diagram so this is the activity diagram here for this ticket vending machine so this is the component diagram in case of component diagram we are discussing what are the different components that will be used in our software development we know that component is nothing but maybe one file maybe one dlll maybe one package maybe one active x model maybe one applet so these are the respective component diagrams we're having so here will be

having the fair details or exc there is a ticket dot java so in this way they will get

integrated to go for the component diagram so depending upon the software architecture

what are the different components will be requiring to develop the software that will be depicted in the component diagram here we have suggested only a sample sample component diagram for the part for the real case studies obviously this component diagram will be will be in far more detail

so let us go for the deployment diagram so here you see the deployment diagram that visualizes

the distribution of components across the enterprise so in case of deployment diagram we're

dealing with multiple nodes these nodes can be categorized in two heads one is the processor and

another one is the respective device so device may be a dump terminal maybe a printer

maybe a card reader maybe a card puncher or any other input input devices and the processors

will have the processor inside which will be intelligent enough which can execute a code which can

execute one application so here we're having this database server there is a railway

reservation domain and here we're having this options that update options are there this

the respective processor and here we're having this TVM that is a front panel we're

having and they are connected by some communication network and in this way the

deployment diagram is visualizing how the distribution of components across the enterprise so in case of component diagram we are going to get the idea that

what are the components are required for the implementation of the software and in

case of deployment diagram we are telling that where these components are

going to get deployed so for that purpose this deployment diagram is there. In our real life case studies, obviously this deployment

diagram will be too much complicated. We have discussed lots of different aspects of this

deployment diagram in the deployment diagram chapter. Please watch all those chapters because

these particular case studies are the accumulation of those knowledgees which we have shared in the

earlier chapters. So we have considered in the first video of this case study we considered

the problem statement. In the next video we have discussed regarding the OA, that is

object-oriented ysis and in this video we have discussed the object-oriented design

I think now you are going to get one idea that whenever one project will be assigned to you

what are the steps to be followed, what is the process flow for development of that particular software

Thanks for watching this video