ATM SIMULATION

BY
ROHIT NANDAN SHAKYA
COMPUTER ENGINEERINIG (6TH SEM)
325252

INTRODUCTION
The topic ATM Simulation has been chosen keeping the functions of an ATM
machine and kiosk in mind. When we swipe our card through the machine, we
are able to extract all the relevant information of our account. A same attempt
has been made through this application to simulate those functions:

We have devised a menu-driven program that lets the user view his last
account activity combined with deposit & withdrawal of money from his
account.

Before the starting of this application, we have assumed that the account
information of 50 users would be stored by our application and the variables
like account balance, deposit & withdrawal would be initialized in the very
beginning to give a good look & feel of the application.

As the application starts, we assume that the user swipes his ATM debit card
which is effectively read by the machine though this is performed through the
human input because we are not integrating any such reader with our
application.

After that the user, enters his/her secret pin no. which is accepted by the
system in the form of a password. If the card no. which we are eventually
assuming as the account number entered manually by the user matches the
pin no., the user is redirected to the menu where he can see all the details
related to his account and can also do any account activity according to his
desires.

If at all the card number does not match with the pin no. the user is
appropriately informed of this.

OBJECTIVE
The proposed system (ATM Simulation) will be able to perform all operations of
the current manual system effectively with reduced cost. Also it will require less
manpower and low maintenance. The proposed system will be very user friendly
and it will require less effort to get acquainted with the system.
After understanding the complete problem, our objective was absolutely clear
regarding what we have to develop that can effectively solve the banks purpose.
To achieve that:

We have just started with the top 50 customers of the bank who had such
normal queries and frequent account transaction in a day..

Our objective was to encourage those customers to use the system and help
them serve all their general requests themselves

For this, we requested the bank to provide the account details & the
frequency of the account activity of such customers.

We finally used this data in our system as an input and tried to generate the
exactly same level of output as received by them by bank employees.

While devising the solution, we also took care of value addition in our work
which meant that the customers should find the system easy to use.

We had clear directions from the bank that the system should increase the
banks goodwill & improve the response times to customers and we also took
user-friendliness as well as scalability into account before developing this
application.

PROJECT CATEGORY:

Application Software
The ATM Simulation is application software, in which various activities are
performed through machine. Registrar user can login, mini statement, Deposit
amt and withdraw amt. the results are done automatically through this software.
The nature of this software is to solve the particular problem that is why its
category is application software.

TOOLS/PLATFORM,LANGUAGES:
Hardware:

Intel Pentium D Processor with 3.00 GHz CPU clock speed

01 GB of RAM

80 GB of Hard Disk space

Software:

Microsoft Windows XP Professional (Service pack 2)

Turbo C++ IDE 3.0

GANTT CHART
Gantt Chart is a project
scheduling technique.
Progress can be represented
easily in a Gantt chart, by
coloring each milestone
when completed. The
project will start in the
month of August and end
after 4 months at the end of
April.

MODULES & DESCRIPTIONS

Modules And Its Descriptions
Smarter Hiring System is composed of mainly twelve modules. Each module is
designed for specific purpose. Each one is supposed to perform a complete task.
These modules are as:

Account Verification Module

Account Detail Module

Amount Deposit Module

Amount Withdrawal Module

There is only one member (excluding Project Guide) involved in this project. The
team hierarchy is given below:

Description of the data objects:

1[a]: Account & Pin number entered by the user

2[d]: If the Account number does not match with Pin number or vice versa,
the application cleanly exits to the system with a proper user message like
Invalid Account / Pin no. entered.

If the inputted details are correct, they are passed to the Main Menu
process and further to different modules which serve the customers requests
individually using those details.

2[a]: Account information & details like Present Balance, Last Deposit & Last
Withdrawal.

2[b]: Deposit details & account balance after deposit.

2[c]: This is withdrawal details & account balance after the withdrawal in
case the withdrawal amount entered is correct.

If the withdrawal amount entered is incorrect or invalid like greater than the
balance, a message is displayed to the user like Invalid amount entered.

DATA FLOW DIAGRAM

ER DIAGRAM

PROCESS LOGIC
Account Verification
In Account Verification form, First user enter own Account number and password.
If your entered Account number and password matched from backened Then
project will process next step. If user put wrong account number then project
will be show error message. On Go, validation for each text box is carried out
and attention is focused on to respective text box that does not meet validation
requirement, thus chances of error are eliminated.
Account Detail
In this, module display the account detail with users account number.
Account detail module display the Last Deposit , Last withdrawl, Present Balance
etc. regarding account number and user name.

Amount Deposit
In Amount Deposit module, User can deposit the amount but user can deposit
maximum three notes. When user choice the Amount Deposit Then this module
will be show three statement: user present balance, Enter the amount to be
deposited and Enter new balance after deposit. If user click add without deposit
amount then this project will display the error message..

Amount Withdrawal
By use of module, User can withdraw amount but if entered amount is available
in bank.
If entered amount is not available then this project will be display error
message. So user can withdraw minimum amount than available in bank.
EXIT
This module will be work of EXIT. If users processing work have finish. Then user
will be exit from own Account.

TYPE OF REPORT GENERATION:

It is the activity of locating and correcting errors. It starts once a failure has
been detected.
In this the following debugging induction approach is used:

Locate the pertinent data

In this step, we take into account what the program did correctly and what
it did incorrectly.

Organize the data

The next step is the structuring of data to allow one to observe patterns. For
e.g. in our program the error can occur if we are assigning more than two project
to the particular person.

Devise a hypothesis

A hypothesis is devised so that according to it we can find out the most

probable one, which is causing the error more frequently.

Prove the hypothesis

Comparing it to the original clues proves the hypothesis or data, making sure
that this hypothesis completely explains the existence of the clues. If it does not
either the hypothesis is invalid, or the hypothesis is incomplete, or the multiple
errors are present

IMPLEMENTATION

Implementation is a process that carries out the operational plans developed

at the end of the information systems planning process. Therefore,
implementation is an important step in assuring the successful development
of information systems for end users.

Implementation involves a variety of acquisition, testing, documentation,

installation and conversion activities. Thus, implementation is a vital step in
assuring the success of new systems. Even a well-designed system can fail if it
is not properly implemented.

POST IMPLEMENTATION MAINTENANCE

Implementation of system means putting up system on users site. Therefore, the
system requires periodic maintenance. Maintenance can be for software or
hardware. User priorities, changes in organizational requirements or changes in
environmental factors call for system enhancements. This is very crucial for
systems life.

TEST CASE
It describes an input description and an expected output description. These are
derived during all phases of the development cycle. It helps in determining
expected results before running a test case.
Some of the test cases for this project are:

SCOPE OF FUTURE APPLICATION

We can hereby conclude that:

The system effectively automated the functions involved in the processes

being handled manually before.

The cost & benefit analysis shows that the system was quite successful in
saving costs for the bank & generate equivalently huge benefits

The system is secure & scalable. The system design has been done keeping
user-friendliness and efficiency in mind.

One year maintenance and software support for the proposed application
software will be provided free of cost (provided change of scope is not
raised).

The proposed software is completely modular and therefore it facilitates for

extendibility i.e. activities for new establishment can be easily added without
affecting the main program with less effort and cost.

Changes in GUIs based screen can be easily incorporated but it will be treated
as changed request and it will be charged.

It will be portable can be implemented on most of the available web based

platform.

Some part of the proposed Application System can be converted to web based
software by using web based scripting languages and tools.

Complete software will be easily upgraded (i.e. versioning of software is

possible) and will show downward compatibility.

BIBLIOGRAPHY

Object Oriented Programming with C++ by E. Balagurusamy

The C Programming language by Kernighan & Ritchie

Teach yourself C by Yashwant Kanetkar

WEB REFERENCES

www.cprogramming.com/tutorial.html

www.cplusplus.com/doc/tutorial/

www.coronadoenterprises.com/tutorials/cpp/index.html/