UML - State chart diagram on ATM Transaction

Strait chart diagram for the ATM transaction case study

We know that in case of state chart diagram, we usually depict the different states of one

object and how the straight transitions will take place from one state to another state

of that very object that will be depicted in the state chart diagram

So let us go for the detailing and here we have selected the account object for the state

diagram a banking account can remain in two different states one is the

open state another one is a closed state okay so this is our initial state

this is our final state we have also leveled that one here so there is a

start state and this is a stop state so this is the circle filled up and there is a

double circle and filled up like this so they are denoting the states we have

written that one and here we are denoting this one as a state

transition so if we have a state transition like this where the initial state

and the terminating state both are the same initial state and the next state

both are the same in that case we can consider it as a reflexive transition okay

now see what is happening so when the account is open in the opening open

state in that case if I want to withdraw money but if the balance is less than

zero that means the money cannot be withdrawn then I shall come down here so So overdraw do send a notice to the customer so the notice will be sent to the customer so from this particular

state the state transition will take place here so now if the car customer

deputies some money so he or she deposits some money on his or her account

when the balance is less than zero then again the account will be in the

opening state but if this when this particular note will be sent and if the balance still remains less than zero for more than 30 days

then in the case the account will be found in the closed state and here also

if customer requests for the closer of the account then from this particular

state open the next state of the account object will become the closed state and

that is the final state as we discussed earlier so in this way we have shown you

that how to draw the stature diagram for the account object A single project may have multiple such diagrams on different objects

So here we are having this diagram, stretcher diagram on the account class only

We can also do such stretcher diagram for other objects in our project as required

So we have discussed the ATM transaction case study. We have drawn the different diagrams

We have gone through the problem statement to this respective diagram, how to draw them into some

details with the practical demonstration. Thanks for watching this video