Project Report: Atm Management System

Atm Management System
ATM MANAGEMENT SYSTEM
PROJECT REPORT
DEEPAK KUMAR REG.NO-17303313060 Page 1

PROJECT REPORT
ON
ATM MANAGEMENT SYSTEM

(PAPER CODE: 604)
SUBMITTED BY
DEEPAK KUMAR
In partial fulfillment of the requirements for the award of Degree
Of
BACHELOR IN COMPUTER APPLICATION
(SESSION: 2017-2020)
UNDER THE GUIDANCE OF

VANDANA KUMARI
ARYABHATTA KNOWLEDGE UNIVERSITY, PATNA
INTERNATIONAL SCHOOL OF MANAGEMENT, PATNA

PROJECT APPROVAL
PROJECT REPORT
ON
“ ”
PREPARED BY
DEEPAK KUMAR
(REG. NO.-17303313060)
IS EXAMINED AND APPROVED
Internal Examiner External Examiner

CERTIFICATE
Certified that this is a bonafide record of the project work entitled

“ATM MANAGEMENT SYSTEM”
has been prepared by

DEEPAK KUMAR
(Reg. no.-17303313060)
BCA VIth semester, International School of Management, Patna

in the year 2020 in partial fulfillment of the requirements to the
award of Degree Bachelor in Computer Application of Aryabhatta
Knowledge University, Patna.
VANDANA KUMARI
Project Guide
TABLE OF CONTENTS
I) DECLARATION……………………………………………………………………………6
II) ACKNOWLEDEGEMENT………………………………………………………………..7
III) ABSTRACT……………………………………………………………………………….8
1. INTRODUCTION
1.1 INTRODUCTION TO ATM …………………………………………………………….9
1.2 OBJECTIVES AND SCOPES OF PROJECT…………………………………………...10
2. SYSTEM SPECIFICATION
2.1 HARDWARE CONFIGURATION……………………………………………………...11
2.2 SOFTWARE CONFIGURATION………………………………………........................12
3. SYSTEM ANALYSIS
3.1 EXISTING SYSTEM…………………………………………………….........................13
3.2 PROPOSED SYSTEM…………………………………………………………………...15
3.3 SOFTWARE TOOLS TO BE USED…………………………………….........................16
4. SYSTEM DESIGN
4.1 TABLE DESIGN………………………………………………………………………...18
4.2 DATA FLOW DIAGRAMS……………………………………………………………..20
4.3 ER DIAGRAM…………………………………………………………………………...25
5. SYSTEM IMPLEMENTATION
5.1 DESIGNING……………………………………………………………………………..28
5.4 CODING…………………………………………………………………........................36
6. SYSTEM TESTING
6.1 UNIT TESTING………………………………………………………….........................41
6.2 INTEGRATION TESTING……………………………………………………………...41
7. PERT CHART……………………………………………………………………………42
8. SECURITY FOR THE PROJECT……………………………………………………...43
9. LIMITATIONS OF THE PROJECT…………………………………………………...44
10. FUTURE SCOPE OF THE PROJECT……………………………………………….45
11. CONCLUSION………………………………………………………………………….46
12. BIBLOGRAPH………………………………………………………….........................47

DECLARATION
I hereby declare that all the documents prepared/attached in this project are
original, complete and of my own effort.
In the event of any information being found false at any stage about the
originality, my project is liable to the rejected.
Place: Patna (DEEPAK KUMAR )

BCA-VI SEM
Session-2017-2020
Reg. No.-17303313060

ACKNOWLEDGEMENT
The college International School of Management, Patna is itself a source of

Inspiration. I feel indebted to the Institute which provided me an opportunity to
undergo the BCA course.
It is my privilege to have the opportunity for expressing my deep sense of

gratitude and humble regards to all those people who guide and helped in
accomplishing this project work under the course “BCA604” submitted as
partial fulfillment for the award of the degree of “Bachelor in Computer
Application (BCA)”.
I am grateful to Mr. K. L. Ambashtha, Asstt .Prof & Head of Dept (IT), ISM,
Patna, who guided me throughout the work, deserves my special thanks.
Without their guidance and assistance I was totally unable to complete the
project work and I also thanks to Mr. Rajeshwar Dayal, Asstt. Prof., ISM, Patna
for his remarkable tips to complete the project work.
I am also grateful to Ms. Jaya Pathak Asstt. Prof., ISM, Patna, who guided me
throughout the work, and deserves my special thanks.
I express my gratitude to those who help me directly or indirectly leading to

accomplishment of the job.

ABSTRACT
The ATM System is the project which is used to access their bank accounts in
order to make cash withdrawals. Whenever the user need to make cash
withdraws, they can enter their PIN number (personal identification number)
and it will display the amount to be withdrawn in the form of 100’s 500’s and
1000’s. Once their withdrawn was successful, the amount will be debited in
their account.
The ATM System is developed in VB.Net and back-end database as Ms-

Access. VB.Net is the one of the powerful version of Framework and object
oriented programming. Hence we use this software in our project.
The ATM will service one customer at a time. A customer will be required to
enter ATM Card number, personal identification number (PIN) – both of which
will be sent to the database for validation as part of each transaction. The
customer will then be able to perform one or more transactions. Also customer
must be able to make a balance inquiry of any account linked to the card.
The ATM will communicate each transaction to the database and obtain
verification that it was allowed by the database. In the case of a cash
withdrawal, a second message will be sent after the transaction has been
physically completed (cash dispensed or envelope accepted). If the database
determines that the customer’s PIN is invalid, the customer will be required to
re-enter the PIN before a transaction can proceed.
If a transaction fails for any reason other than an invalid PIN, the ATM will
display an explanation of the problem, and will then ask the customer whether
he/she wants to do another transaction.
The ATM will provide the customer with a printed receipt for each successful
transaction, showing the date, time, machine location, type of transaction,
account(s), amount, and ending and available balance(s) of the affected account
(“to” account for transfers).

1. INTRODUCTION
1.1. Introduction to the ATM system:
Automated Teller Machine enables the clients of a bank to have access to their
account without going to the bank. This is achieved only by development the
application using online concepts.
When the product is implemented, the user who uses this product will be able to
see all the information and services provided by the ATM, when he enters the
necessary option and arguments. The product also provides services like
request for cheques, deposit cash and other advanced requirement of the
user. The data is stored in the database and is retrieved whenever
necessary. The implementation needs ATM machine hardware to operate or
similar simulated conditions can also be used to successfully use the developed
product.
To develop this ATM system the entire operation has been divided into the
following step:
1. verification process
2. language, service and account selection
3. Banking services
4. Transactions
5. Special services
The program is designed in such a way that the user has to card and pin
number. Once verified, he is provided a menu and he/she had to enter the
option provided in the menu.For example, when the user wants to view the list
of payment history than he/she had to enter the option for payment history
provided in the main menu. When the option is entered alone with the
respective argument, then the payment history is displayed on the screen.
The user also must be given option to browse through the pages like previous
page, next page, etc. The user may experience a delay in retrieving or viewing
the data, when there are many users logged on to the same bank branch system.

1.2 OBJECTIVES AND SCOPES OF THE PROJECT
Objectives:
 To deal with ATM Management System in an easy way and an efficient

manner,
 Create strong and secret data base that allow for any connection in a secret
way, to prevent any outside or inside attacks,
 To automate each and every activity of the manual system, which increases
its throughputs,
 To provide a quick response with very accurate information as and when
required,
 To make the present manual system more interactive, speedy and user
friendly,
 To avail any information, whatever and whenever required,
 To reduce the cost of maintenance.
Scopes:
 The software product “ATM management system” will be an application that

will be used for maintaining the records in an organized manner to replace
old paper work system.
 This project aims at automating the ATM management for smooth working
of the clinic by automating almost all the activities. Update & modifications
will be easily achievable and all the records and calculation work would be
accurate.

*
2. SYSTEM SPECIFICATION
2.1. Hardware Requirements:
1. Processor – Pentium 4
2. RAM – 1 GB
3. Hard Disk – 40GB
4. Mouse – Standard Mouse
5. Keyboard – Logitech Keyboard
6. Processor Speed – 2.4GHZ
2.2. Software Requirements:
1. Operating System – Microsoft Windows XP With Service

Pack 2
2. Front-End – Microsoft Visual Studio 2005
3. Back-End – Microsoft Access 2003
2.3. Display Mode:
1. Color Quality – Highest[32 bit]

2. Screen Resolution – 1024 by 768 Pixels

2.4 SOFTWARE CONFIGURATION
A major element in building a system is the section of compatible software

since the software in the market is experiencing in geometric progression.
Selected software should be acceptable by the firm and one user as well as it
should be feasible for the system.
This document gives a detailed description of the software requirement

specification. The study of requirement specification is focused specially on the
functioning of the system. It allows the developer or analyst to understand the
system, function to be carried out the performance level to be obtained and
corresponding interfaces to be established.

SYSTEM ANALYSIS
Understand the problem before the system to create analysis model there is a
tendency to rush to a solution, even before the problem is understood.
Develop prototypes that enables user to understand how human/machine

interaction will occur. Since the perception of the quality of software is often
based on the perception of the “friendliness” of the interface prototyping is
highly recommended.
Record the origin of and the reason for every requirement. This is the first step-
in establishing traceability back to the customer.
Use multiple views of requirements building data, functional and behavioral

models provide the software engineer with three different views. This reduces
the likelihood that something will be missed and increases the likelihood that
inconsistency will be recognized.
Rank requirements. Tight deadlines may preclude the implementation of every

software requirements to be delivered in the first increment must be identified.
Work to eliminate ambiguity because most requirements are described in a

natural language, the opportunity for ambiguity abounds.
3.1 EXISTING SYSTEM

The existing system is manual system.
1. The manual system is prone to error.
2. This system involves a lot of manual entries with the application to perform a
desired task.

3. Usage of papers and records in the process leads to less efficiently less
productivity.
4. Increase lots of mistakes while writing in paper.
5. Time delay between the user and customer is reduced.
6. For this reason the new system in invented.
DISADVANTAGES:
 More human power
 More strength and strain of manual labour needed
 Repetition of same procedure.
 Low security.
 Data redundancy.
 Difficulty to handle.
 Difficulty to update data.
 Record keeping is difficult.
 Backup data can be easily generated.
 Everytime customers had to come to bank for even small tranctions.
 Large expenditure on labour force.

3.2 PROPOSED SYSTEM
The system customer transactions, satisfies the requirements of the existing

system in full-fledged manner. Through this system, customer can make fast
transactions and view the last transactions easily.
3.2.1System planning:
1. Analysis principles are applied and a model of the software to be build

called a planning (prototype) is constructed for customer and developer
assessment.
2. The close-ended approach is often called throwaway prototyping using

this approach a prototype serves solely as a rough demonstration of
requirements it is then discarded and the software is engineered using a different
paradigm.
3. An open-ended approach, called evolutionary prototyping uses the

prototype as the first part of an analysis activity that will be continued into
design and construction the prototype of the software is the first evolution of the
finished system.
3.2.2 Feasibility Study:
Technology:
This system is technically feasible, because the system activated by computers

and recent technology. We use client / server technology which is powerful and
very user friendly.
Finance:

It is financially feasible. There is no need of spending over money. Since we
use visual studio dot net as a front-end it was most power-full, small and
portable across platforms and operating systems both at the source and at the
binary level. This project reduces the number of workers wage also.
Time:
This system really time-to-market beat the competition. Because,the system

developed with in a time span and worked based on time event. The time taken
to access the account is very less and avoids unnecessary waiting that was in the
traditional system. Although it uses less time but its performance is very well.
Resources:
This system will use the well known resources. Where there is no need of any
special kind of resource. It uses only the required databases, tables only.
3.3 SOFTWARE TOOLS TO BE USED
The whole Project is divided in two parts the front end and the back end.
3.3.1 FRONT END

Visual basic Form is the container for all the controls that make up the user
interface. Every window you see in a running visual basic application is a form,
thus the terms form and window describe the same entity. Visual Studio creates
a default form for you when you create a Windows Forms Application
3.3.2 BACK END

Microsoft Access is a Database Management System (DBMS) from Microsoft
that combines the relational Microsoft Jet Database Engine with a graphical

user interface and softwaredevelopment tools. It is a member of the Microsoft
Office suite of applications, included in the professional and higher editions.
 Microsoft Access is just one part of Microsoft’s overall data management
product strategy.
 It stores data in its own format based on the Access Jet Database Engine.
 Like relational databases, Microsoft Access also allows you to link
related information easily. For example, customer and order data.
However, Access 2013 also complements other database products
because it has several powerful connectivity features.
 It can also import or link directly to data stored in other applications and
databases.
 As its name implies, Access can work directly with data from other
sources, including many popular PC database programs, with many SQL
(Structured Query Language) databases on the desktop, on servers, on
minicomputers, or on mainframes, and with data stored on Internet or
intranet web servers.
 Access can also understand and use a wide variety of other data formats,
including many other database file structures.
 You can export data to and import data from word processing files,
spreadsheets, or database files directly.
 Access can work with most popular databases that support the Open
Database Connectivity (ODBC) standard, including SQL Server, Oracle,
and DB2.
 Software developers can use Microsoft Access to develop application
software.
Microsoft Access stores information which is called a database. To use MS
Access, you will need to follow these four steps −

 Database Creation − Create your Microsoft Access database and specify
what kind of data you will be storing.
 Data Input −After your database is created, the data of every business
day can be entered into the Access database.
 Query −This is a fancy term to basically describe the process of
retrieving information from the database.
 Report (optional) − Information from the database is organized in a nice
presentation that can be printed in an Access Report.
4. SYSTEM DESIGN
4.1 DATA DICTIONARY
Table Name: Customer
Column Name Data Type
Cust_id Varchar30
Cust_name Varchar30
Dob number
Contact_no number
Cust_add Varchar30
ac_no number
ac_type Varchar30
Bal number
Card_no number
Card_pin number
branch_id Varchar30

Table Name: Bank
Branch_id Varchar15
Branch_name Varchar15
Branch_add Varchar15
Admin_id Varchar15
Table Name: Atm
a_branch_id Varchar30
a_branch_name Varchar30
a_branch_add Varchar30
a_admin_id Varchar30
available_cash number
b_branch_id Varchar30
Table Name: Admin_atm
a_admin_id Varchar30
a_admin_name Varchar30
a_admin_pin number

4.2 DATA FLOW DIAGRAMS
a. 0-Level DFD (Atm)
USER NAME ENTER PIN
SERVICES
READER
PIN CHANGE
CARD NOT
ATM SCREEN
FOUND
BALANCE
DETAILS
FAST CASH

ER DIAGRAM ATM MANAGEMENT SYSTEM
AREA NAME
NAME
ID
ID
ATM MACHINE ATM CARD PIN NO
INSERT USES
Provide
ED IN
s
BANK ID USER
NAME
NAME
PIN NO
BRANCH ACCOUNT
AREA
NO

1st Level DFD for (customer)
Fund
Customer
Tranfer
r
Customer DATABASE
Details
Cash Withdrawal

2nd level DFD for Customer
Customer’s card details
Card cannot read

Read
detail from
Printer/Display
card
Card data
Encoded pin
Customer
Check
expiry
Pin
date
Card Validation data
Request
pin and Access map
match 3
times
Invalid
pin
Access Network Directory
authorization

2ND Level DFD For ADMIN
ADMIN LOGIN
DATABASE
See all Record

DELETE
record
ADD cash

ER Diagram for Atm Management System
Name
Password
Atm
User Uses
Maintain
Acc no
Admin
Balance
Expiry
date
Login Password
Id

ADMIN LOGIN
DATABASE
NOTIFICATION
DELETE
ADD VIEW
DATABASE

Full-Form of the words used:-
 Cust_id : Customer id
 Cust_name : Customer Name
 Dob : Date of Birth
 Contact_no : Contact number
 Cust_add : Customer Address
 ac_no : Account Number
 ac_type : Account Type
 Bal : Balance
 Card_no : Card Number

1. SYSTEM IMPLEMENTATION
5.1 DESIGNING
HOME PAGE

SECURITY YOUR ACCOUNT

ABOUT PAGE
1. Login to Online Banking.
2. Select 'Manage accounts' menu. Select 'View my debit card PIN' from
the 'Card Service' menu.
3. If you have multiple accounts with debit cards select the

appropriate one from the drop down.
 Then you have to actually go to the bank

and get a new card. This means that a person
would first have to have your card, and they
would then get only 3 attempts to gain access
to your account. ... That's why banking
institutions allow their ATM PINs to be just 4
digits in length

MENU

PLEASE SELECT ACCOUNT SCREEN
About page
 A savings account is most suitable for people who are salaried

employees or have a monthly income, whereas, Current Accounts work best
for traders and entrepreneurs who need to access
their accounts frequently. Savings accounts earn interest at a rate of
around 4%, while there is no such earning from a Current
Account


coding
Public Class Form1
Private Sub Timer1_Tick(ByVal sender As System.Object, ByVal e

As System.EventArgs) Handles Timer1.Tick
ProgressBar1.Increment(10)
If ProgressBar1.Value = ProgressBar1.Maximum Then
ProgressBar1.Value = 0
Timer1.Stop()
ProgressBar1.Hide()
Button1.Enabled = True
End If
End Sub
Private Sub Form1_Load(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles MyBase.Load
ProgressBar1.Maximum = 100
ProgressBar1.Minimum = 0
Timer1.Start()
End Sub
Private Sub Button1_Click(ByVal sender As System.Object, ByVal e

As System.EventArgs) Handles Button1.Click
Form2.Show()
End Sub
End Class

Imports System.Data.SqlClient
Imports System.Data
Public Class Form2
Dim inc As Integer
Dim con As New OleDb.OleDbConnection
Dim dbprovider, dbsource As String
Dim ds As New DataSet
Dim da As New OleDb.OleDbDataAdapter
Dim sql As String
Dim maxrows As Integer
dbprovider = "Provider=Microsoft.ACE.OLEDB.12.0;"
dbsource = "Data Source=D:\Users\Public\Videos\atm"
con.ConnectionString = dbprovider & dbsource

con.Open()
sql = "SELECT * FROM pinno"
da = New OleDb.OleDbDataAdapter(sql, con)
da.Fill(ds, "atm")
maxrows = ds.Tables("atm").Rows.Count
End Sub
Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles Button1.Click
Dim SearchId, i, currentrow As Integer
SearchId = TextBox1.Text
i = 0
While i <> maxrows + 1
If SearchId = ds.Tables("atm").Rows(i)("pin") Then
Me.Close()
Form3.Label1.Text = ds.Tables("atm").Rows(i)("acc_no")
Form3.Show()
Exit While
ElseIf i = maxrows Then
MsgBox("INVALID PIN number!!!")
Exit While
End If
i += 1
End While
currentrow = i
End Sub

TextBox1.Text = ""
TextBox1.Clear()
End Sub

Form1.Show()
Me.Close()
End Sub
Private Sub btn1_Click(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles btn1.Click, btn9.Click, btn8.Click, btn7.Click,
btn6.Click, btn5.Click, btn4.Click, btn3.Click, btn2.Click, btn0.Click
TextBox1.Text = TextBox1.Text & sender.text
End Sub
End Class
Imports System.Data
Public Class Form3
Dim inc As Integer
Dim sql As String
Dim maxrows, i, currentrow As Integer
dbsource = "Data Source=C:\Users\Public\Videos\atm.accdb"

con.Open()
sql = "SELECT * FROM master"
da.Fill(ds, "atm")
i = 0

If Label1.Text = ds.Tables("atm").Rows(i)("acc_no") Then
Label4.Text = ds.Tables("atm").Rows(i)("cust_name")
Form4.Label1.Text = ds.Tables("atm").Rows(i)("cust_name")
' Form10.Label8.Text =
ds.Tables("atm").Rows(i)("cust_name")
' Form10.Label6.Text = ds.Tables("atm").Rows(i)("acc_no")

' Form10.TextBox1.Text = ds.Tables("atm").Rows(i)("pin")
'Form11.Label3.Text =
ds.Tables("atm").Rows(i)("cust_name")
' Form11.Label6.Text = ds.Tables("atm").Rows(i)("acc_no")
Exit While
MsgBox("ADMIN USER")
Exit While
End If
i += 1
End While
currentrow = i
End Sub

Form4.Show()
End Sub

Form6.Show()
End Sub

Form7.Show()
End Sub
End Class
Imports System.Data
Public Class Form4
Dim inc As Integer
Dim sql As String
Dim maxrows, i, currentrow As Integer

con.Open()

da.Fill(ds, "atm")
i = 0
Label1.Text = ds.Tables("atm").Rows(i)("cust_name")
' Label6.Text = Dst.Tables("atm").Rows(i)("acc_no")
Exit While
MsgBox("ADMIN USER")
Exit While
End If
i += 1
End While
currentrow = i
End Sub

Form5.Show()
End Sub
Private Sub LinkLabel1_LinkClicked(ByVal sender As System.Object,

ByVal e As System.Windows.Forms.LinkLabelLinkClickedEventArgs) Handles
LinkLabel1.LinkClicked
Me.Close()
Form3.Show()
End Sub
End Class
Imports System.Data
Public Class Form5
Dim inc As Integer

Dim ds, ds1 As New DataSet
Dim da, da1 As New OleDb.OleDbDataAdapter
Dim sql, sql1, srw As String
Dim maxrows, mr, i, currentrow As Integer
Public balance, current As Integer
Dim dot As Date


con.Open()

sql1 = "SELECT * FROM dailytrans"
da1 = New OleDb.OleDbDataAdapter(sql1, con)
da.Fill(ds, "atm")
da1.Fill(ds1, "atm")
mr = ds1.Tables("atm").Rows.Count
End Sub

Dim i, currentrow As Integer
i = 0
current = ds.Tables("atm").Rows(i)("amnt")
balance = current - TextBox1.Text
daily()
Dim cb As New OleDb.OleDbCommandBuilder(da)

ds.Tables("atm").Rows(i).Item("amnt") = balance
da.Update(ds, "atm")
MsgBox("amount withdrawed")
Exit While
MsgBox("INVALID PIN number!!!")
Exit While
End If
i += 1
End While
currentrow = i
End Sub
Public Sub daily()

Dim cb1 As New OleDb.OleDbCommandBuilder(da1)
Dim dsNewRow As DataRow
dsNewRow = ds1.Tables("atm").NewRow()

If Form4.RadioButton1.Checked = True Then
srw = Form4.RadioButton1.Text
Else
srw = Form4.RadioButton2.Text
End If
dot = DateTime.Now
dsNewRow.Item("dateoftrans") = dot
dsNewRow.Item("acc_no") = Label6.Text
dsNewRow.Item("transtype") = srw
dsNewRow.Item("amtWD") = TextBox1.Text
dsNewRow.Item("prevamt") = current
dsNewRow.Item("curramt") = balance
ds1.Tables("atm").Rows.Add(dsNewRow)
da1.Update(ds1, "atm")
MsgBox("daily transaction updated")
End Sub

Me.Close()
Form3.Show()
End Sub
End Class

2. SYSTEM TESTING
6.1 UNIT TESTING
The software units in the system are modules and routines that are assembled
and integrated to perform a specific function. As a part of unit testing we
executed the program for individual modules independently. This enables, to
detect errors in coding and logic that are contained within each of the three
modules. This testing includes entering data that is filling forms and
ascertaining if the value matches to the type and entered into the database. The
various controls are tested to ensure that each performs its action as required.
6.2 INTEGRATION TESTING
Data can be lost across any interface, one module can have an adverse effect on
another, subfunctions when combined, may not produce the desired major
functions. Integration testing is asystematic testing to discover errors associated
within the interface. The objective is to take unittested modules and build a
program structure. All the modules are combined and tested as a whole. Here
the admin module, sec module and patient module options are integrated and
tested. This testing provides the assurance that the application is well integrated
functional unit with smooth transition of data.

7. PERT CHART
Requirement Gathering
30 24 23
march Days april
2020 2020
Designing
Start
22 13 3 may
april Days 2020
System Analysis 2020
4 april 20 2
2020 Days may
2020
Coding
4 26 30
may Days may
2020 2020
Testing Implimentation
31 13 14 14 june 12 20june
May Days june 2020 Days 2020
2020 2020
Stop

8. SECURITY FOR THE PROJECT
Security is one of the important features of any project. Without security the
project is not so reliable. In this system the software security and database
security will be implemented, so that unauthorized admin cannot enter into the
system and cannot access the database.
Those admin who know the user_Id and password can only access the database.
For this one table has been created in the database named signin in which there
are two attributes:
 Atm Card
 Atm pin

9. LIMITATIONS OF THE PROJECT
Every project has some limitations and in our project there are also some
limitations. In our present project there are no facilities for
 Fingerprint based atm

 Message alerts.
So, we will try to resolve these limitations in future.

10. FUTURE SCOPE OF THE PROJECT
There will be a huge demand for the atm management system in the future for
managing the atm. For the past few years, the number of customers of the banks
is increasing rapidly. Thereby the number of atm is also increasing to render the
customers. And hence there is a lot of strain on the banks who are running the
atm and software are not usually used in this context. In the future, fingerprint-
based atm will also be developed which has more security features than the
existing system. In the future, we can add more modules as per our requirement
for making our software more useful and user friendly.

11. CONCLUSION
The project developed using dot.net with html and ms access is based on the
requirement specification of the user and the analysis of the existing system,
with flexibility for future enhance. In the past few years the numbers of ATM
are increasing rapidly. . It became a necessity for such atm to use computers for
the purpose. But, in the absence of the versatile software the computer were not
being utilised and the banks were facing lot of problems too.
Keeping all these in the mind this software is developed to get rid from various
problems which occur during banking tranctions.
Identification of drawbacks of the earlier developed existing systems lead to the

designing and development of present system. This is compatible with the
existing system and is GUI oriented and more users friendly too.

12. BIBLOGRAPHY
[1] https://www.w3schools.com
[2] http://www.en.wikipedia.org/wiki
[3] https://www.aspsnippets.com
[4] https://web-school.in
[5] https://www.codeproject.com
[6] James R Groff and Paul N Weinberg, “Complete reference SQL”.

Second Edition

Project Report: Atm Management System

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Project Report: Atm Management System

Uploaded by

Copyright:

Available Formats

Atm Management System

ATM MANAGEMENT SYSTEM

DEEPAK KUMAR REG.NO-17303313060 Page 1

ATM MANAGEMENT SYSTEM

In partial fulfillment of the requirements for the award of Degree

UNDER THE GUIDANCE OF

ARYABHATTA KNOWLEDGE UNIVERSITY, PATNA

INTERNATIONAL SCHOOL OF MANAGEMENT, PATNA

DEEPAK KUMAR REG.NO-17303313060 Page 2

IS EXAMINED AND APPROVED

Internal Examiner External Examiner

DEEPAK KUMAR REG.NO-17303313060 Page 3

Certified that this is a bonafide record of the project work entitled

has been prepared by

BCA VIth semester, International School of Management, Patna

8. SECURITY FOR THE PROJECT……………………………………………………...43

9. LIMITATIONS OF THE PROJECT…………………………………………………...44

10. FUTURE SCOPE OF THE PROJECT……………………………………………….45

DEEPAK KUMAR REG.NO-17303313060 Page 5

Place: Patna (DEEPAK KUMAR )

DEEPAK KUMAR REG.NO-17303313060 Page 6

The college International School of Management, Patna is itself a source of

It is my privilege to have the opportunity for expressing my deep sense of

I express my gratitude to those who help me directly or indirectly leading to

DEEPAK KUMAR REG.NO-17303313060 Page 7

The ATM System is developed in VB.Net and back-end database as Ms-

DEEPAK KUMAR REG.NO-17303313060 Page 8

1.1. Introduction to the ATM system:

2. language, service and account selection

DEEPAK KUMAR REG.NO-17303313060 Page 9

1.2 OBJECTIVES AND SCOPES OF THE PROJECT

 To deal with ATM Management System in an easy way and an efficient

 The software product “ATM management system” will be an application that

DEEPAK KUMAR REG.NO-17303313060 Page 10

2.1. Hardware Requirements:

2.2. Software Requirements:

1. Operating System – Microsoft Windows XP With Service

2.3. Display Mode:

1. Color Quality – Highest[32 bit]

DEEPAK KUMAR REG.NO-17303313060 Page 11

2.4 SOFTWARE CONFIGURATION

A major element in building a system is the section of compatible software

This document gives a detailed description of the software requirement

DEEPAK KUMAR REG.NO-17303313060 Page 12

Develop prototypes that enables user to understand how human/machine

Use multiple views of requirements building data, functional and behavioral

Rank requirements. Tight deadlines may preclude the implementation of every

Work to eliminate ambiguity because most requirements are described in a

3.1 EXISTING SYSTEM

1. The manual system is prone to error.

DEEPAK KUMAR REG.NO-17303313060 Page 13

4. Increase lots of mistakes while writing in paper.

5. Time delay between the user and customer is reduced.

6. For this reason the new system in invented.

DEEPAK KUMAR REG.NO-17303313060 Page 14

The system customer transactions, satisfies the requirements of the existing

1. Analysis principles are applied and a model of the software to be build

2. The close-ended approach is often called throwaway prototyping using

3. An open-ended approach, called evolutionary prototyping uses the

3.2.2 Feasibility Study:

This system is technically feasible, because the system activated by computers

DEEPAK KUMAR REG.NO-17303313060 Page 15