UML - Case study on ATM transaction

yesterday on ATM transaction so let us

discuss some case studies so that you

can get an idea that how these systems

from the very problem statement to the

implementation can be done and what are

the steps in between so in this

particular case study we have drawn

different diagrams UML diagrams

depending upon the problem statement and

also we have shown you that how to draw

such diagrams using rational rows

software please watch all the videos on

this case study so now at first let us

discuss the problem statement software

is to be designed for supporting a

computerized ATM banking network all the

processes involved in the bank are

computerized accounts maintained in the

bank the transactions affected and

including ATM transactions are to be

processed step-by-step by the computers

in the bank and ATM machine accepts ATM

card so now we are discussing in the

problem statement how one can deposit or

withdraw money using the ATM card

so an ATM machine accepts ATM card

validates a pin and verifies the

password and interacts with the user and

communicates with the central system to

carry out the transaction dispenses and

deposits cash and prints receives of the

transaction history so this is a part of

the problem statement so let us let us

have some respond statement so the

invalid pin of the cart is rejected the

system to be designed and implemented

must include appropriate record-keeping

and security provisions the proposed

system must satisfy the user recommends

the system should be user-friendly and

derive usability and also it should give

the quality assurance so this is the

problem statement we are having here so

here is one diagram to show you that

there is a central computer these are

the bank can be

they're connected with some computer

communication network and with the

central computer ATMs are connected with

these Bank computers where having the

different accounts are getting connected

there's a Cask cash counter these are

the different customers who will be

using them so just one pictorial

representation of this a problem

whatever we have discussed so I think we

have gone through the problem statement

so now we are going to have two sections

now one is a functional requirement and

the one is that non-functional

requirement so through this discussion

also you'll be having the idea what is

the difference between functional and

non-functional requirements so

functional requirements so details of

that transaction if the bank client must

be able to deposit or withdraw an amount

to or from his account using the ATM

counters each transaction has to be

recorded and the client must be able to

review all transactions performed in his

system or accounts all the transactions

include the following details so that is

a bank client account date time and type

of transactions made amount and account

balance after the transaction so all

this detailing is required so that is

our details of the transaction so let us

go for another functional requirement on

validate Bank client access to the bank

account through ATM card is validated by

a pin code which has been mentioned in

the problem step and also the length of

the pin code is the numeric digit of

length 4 so that means we will be having

4 digits in the pin code next one next

functional recommend there is a third

recommend account to be the amount to be

withdrawn the bank in consultation with

a client shall fix that amount that can

be or can be withdrawn on a specific day

that means depending upon the account

type the bank or three

and the client so they must be having

some consolidation and they'll decide

what is the amount that can be withdrawn

in maximum for a certain day next one is

a cross withdrawal limit the system

should be designed such that it

automatically checks the amount in the

account of the client if the amount to

be withdrawn exceeds the amount in the

account of the client then he should

check whether the client could avail the

overdraft facility or not as for the

bank rules to enable the transaction so

sometimes it may happen that among which

is going to be withdrawn is greater than

the amount which is there in the account

balance so in the case we should have to

check whether the overdraft facility is

available on that account or not and

accordingly the transactions will be

will have the success now this is this

that the non-functional recommend so

whatever the function recommends we

discussed so let me reverse once so that

is the details of the transaction what

are the what are the attributes that

should be kept as the details of the

transaction and then validate the bank

client so how to check whether the

client is valid or not

through the password through the

four-digit pin and so on and next

functional requirement was that that is

the amount to be withdrawn what is the

amount the client can withdrawn in

maximum part day and then cross

withdrawal limit so what is the

withdrawal limit whether the account is

having the word or facilities or not so

here you have brief discussed these are

the functional requirements so now let

us go for the non-functional

requirements so system should be

designed simple enough to enable the

user to operate without any formal

training or any kind of delay system

must be secured and protected from

unauthorized users so in the problem

statement we have we have discussed that

the system should be user-friendly the

system should be the quality assurance

should be ensured the system should be

secured so they are mentioning all these

in the in a in non-functional

requirements in some specific points so

system must handle the card stock up

network and power failure

software must be efficient to use and

provide quick recover from the fault

software must validate and cancel

operation of incorrect pin incomplete

transaction insufficient font time delay

and written failure and user interface

screen must be designed to operate

easily it should be user-friendly and it

should have visual appealing so these

are the non-functional requirements so

we are getting this idea that whenever a

problem in our real-life scenario when

will be working for a certain project

the problem statement will be given and

then we should have to derive the

functional requirements and the

non-functional requirements so you are

getting this idea that how the real

light projects can be handled so please

watch next videos there in the

continuation of this discussion thanks

for watching this