ATM Project Report

Posted on February 12, 2011 by leesys

ATM SYSTEM

A PROJECT REPORT

Submitted for the partial fulfillment for the award of degree of BCA Computer

Application of the Thiruvalluvar University.

By

K. PRIYANKA – 2878803

V. PRIYANGA – 2878802

A. SHARMILA – 2878822

Under the guidance of

Mrs. Pichaiammal, M.C.A.,

Department of Computer Application

MMES Women’s Arts & Science College

Melvisharam, Vellore – 632 509.

JAN – FEB 2011

BONAFIDE CERTIFICATE

This is to certify that this project report entitled “ATM System “ being

submitted to the record, MMES Women‟s Arts & Science College,

Melvisharam,Vellore, by K. Priyanka, V. Priyanga and A. Sharmila for the

partial fulfillment for the award of degree of BCA (Computer Application), is a

bonafide record of work carried out by her, under our guidance and

supervision. It has not been submitted for the award of any other degree.

HEAD OF DEPARTMENT

Department of computer Application,

MMES Women‟s Arts & Science College,

Melvisharam, Vellore – 632 509.

Submitted for the Viva – Voice Examination on

INTERNAL EXAMINER EXTERNAL

EXAMINER

ABSTRACT

ATM MANAGEMENT SYSTEM

The ATM MANAGEMENT SYSTEM is the project which is used to access their
bank accounts in order to make cash withdrawals, cash Deposits and transfer
funds. Whenever the user needs to make cash withdrawal, user need to login
using their user name and password and it will display the amount to be
withdrawn in the form of 100‟s 500‟s and1000‟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 MY SQL.VB.Net is the one of
the powerful versions 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 login details such as user name and
password– 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 his/her
account. 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 (Amount credited success). If the database determines
that the customer’s username or password is invalid, the customer will be
required to re-enter the correct details before a transaction can proceed. If a
transaction fails for any reason, the ATM will display an explanation of the
problem, such as invalid username or invalid password.

ACKNOWLEDGEMENT

First of all, I thank the almighty god who showered his immense blessings on

me, which helped me to complete this project successfully.

My heart full thanks to Prof. U. Peer, M.Sc., M.phil., D.H.Ed., P.G.D.C.A.,

Principal, MMES Women‟s Arts & Science College for giving me the accessory

environment to acquire knowledge and skill.

My sincere and warmest thanks to Mrs. Mujeebunnisa Begum, M.C.A., Head of

the Department of Computer Application, MMES Women‟s Arts & Science

College, for her valuable and inspiring guidance and encouragement given

throughout the period of this project.

I feel indebted to guide Mrs. Pichaiammal, M.C.A., who guide our project with

reviews, evaluations, guidance and suggestions offered throughout this

project. She offered her time to perfect my work. I appreciate her immense

patience.

I am very glad to express my sincere thanks and sense of indebtedness to Mrs.

Geetha, B.B.A., MD, Lee Sys Software Development & Solutions, Vellore, for

permitting me to do my project work in this reputed institution.

I would also like to thank Mr. Muthu M.C.A., Project header, Lee Sys Software

Development & Solutions, Vellore, who has given his valuable guidance clearing

this project.

I also express my whole hearted thanks to my parents for their encouragement

to bring this project to a successful completion.

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. 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 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. Need for the ATM system:

Millions of times per day around the globe people are instantly withdrawing

money at automatic teller machines (ATMs). Given the fast-pace of the world

today, it is not surprising that the demand for access to quick cash is so

immense. The power of ATMs would not be possible without secure

connections. The final act of ATM dispending cash is the result of an amazingly

fast burst of the customer never sees, but a trust is being done in a confidential

manner.

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 – vb.net

3. Back-End – MySQL

2.3. Display Mode:

1. Colour Quality – Highest[32 bit]

2. Screen Resolution – 1024 by 768 Pixels

3. PROJECT DESCRIPTION

3.1 Need For The Software:

Now a days every one very busy in their work. So they feel that the job must be

easier so the system is used to reduce their work which is done in the ATM

system. Instead of keeping lots of paper into a record or file and it may be

missed somewhere so, this system help to keep the record of the customer it

also keeps the details of he customer. It is also easy to access.

3.2 Problem description :

The system mainly used by the bank clients. When a client comes to ATM

centre to update and delete their account. It reduces the time consumption and

lot of paperwork. For any single operation it involves numerous references and

updating also takes subsequent changes in other places.

4. SYSTEM STUDY AND ANALYSIS

4.1. Existing System:

v The existing system is manual system.

v The manual system is prone to error.

v This system involves a lot of manual entries with the application to perform

a desired task.

v Usage of papers and records in the process leads to less efficiently less

productivity.

v Increase lots of mistakes while writing in paper.

v Time delay between the user and customer is reduced.

v For this reason the new system in invented.

4.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.

4.3. 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.

4.4. System planning:

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

called a planning (prototype) is constructed for customer and developer

assessment.

v 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.

v 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.

4.5. 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. Mainly this

system constructed by existing devices only. 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.

5. SYSTEM DESIGN

5.1 Data flow Diagram:

Level 0:

Level 1:

Level 2:

5.2 UML Design:

Use case Diagram:

A use case diagram is a diagram which consists of set of use cases and actors
enclosed by system boundary, and association between use cases and

actors. Use cases diagram especially important in organizing, modelling the

behaviour of the system.

Use case is a set of scenarious tied together by a common user goal. A scenario

is a sequence of steps describing the interaction between a user and system.

Use case Diagram :

5.3. Sequence Diagram:

A sequence diagram is an easy way of describing the behaviour of the system. A

sequence diagram shows an interaction arranged in time sequence. It has two

dimensions, the horizontal dimension represents the life of the object.

5.4. Collaboration Diagram:

Collaboration diagram represent a collaboration which is a set of objects related

in a particular context and interaction which has asset of messages exchanges

between objects.

5.5. Activity Diagram:

This diagram describes the sequence of activities with superior for conditional

and parallel behaviour.

5.6. Class Diagram:

It describes that set of classed, interfaces and collaboration and their

relationship. It describes the types of objects in their system and various kinds

of static relationship that exceeds among them.

6. SCREEN SHOTS

Main Form:

Menu Form:

Login Form:

Transaction Form:

Balance Inquiry Form:

Withdrawal Form:

Processing Form:

Statement Form:

Administrator login Form:

Administrator Menu Form:

Administrator Report:

About Form:

7. CODING

Connection Module:

Module Module1

Public conn As New ADODB.Connection

Public cmd As New ADODB.Command

Public rsUser As New ADODB.Recordset „Recordset for clients

Public reportstr As String

Public Account Number As String

Public username As String

Public Client Name As String

Public Expire Date As Date

Public Account Balance As Double

Public cash As Double

Public Rs Trans As New ADODB.Recordset

Public rslog As New ADODB.Recordset

Public Sub conncall()

conn = New ADODB.Connection

conn.Open(“Provider=Microsoft.Jet.OLEDB.4.0;Data Source=atm.mdb”)

If conn.State = 1 Then

If rsTrans.State = 1 Then rsTrans.Close()

rsTrans.Open(“select

AccountID,TransactionDate,TransactionTime,AmountWithdrawal from trans”,

conn, ADODB.CursorTypeEnum.adOpenKeyset,

ADODB.LockTypeEnum.adLockOptimistic)

„Used to keep records of the transactions

If rsUser.State = 1 Then rsUser.Close()

rsUser.Open(“Select cardnumber from client”, conn,

ADODB.CursorTypeEnum.adOpenKeyset,

ADODB.LockTypeEnum.adLockOptimistic)

„Used for data validations and processing

If rslog.State = 1 Then rslog.Close()

rslog.Open(“Select AccIDText,PinText,UDate,UTime from log”, conn,

ADODB.CursorTypeEnum.adOpenKeyset,
ADODB.LockTypeEnum.adLockOptimistic)

„Used to keep track of the logins

Else

„when database connection error occurs

MsgBox(“Database Connection Error”, vbCritical, “SD BANK PVT LTD”)

End

End If

End Sub

End Module

MDIMain form:

Public Class MDIMain

Private Sub MDIMain_Load(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles MyBase.Load

Me.ATMMechineToolStripMenuItem.Enabled = False

FrmMainMenu.Show()

End Sub

Private Sub MainMenuToolStripMenuItem_Click(ByVal sender As

System.Object, ByVal e As System.EventArgs) Handles

MainMenuToolStripMenuItem.Click

Me.ATMMechineToolStripMenuItem.Enabled = False

FrmMainMenu.Show()

End Sub

Private Sub ExitToolStripMenuItem_Click(ByVal sender As System.Object,

ByVal e As System.EventArgs) Handles ExitToolStripMenuItem.Click

FrmMainMenu.Hide()

End Sub

Private Sub ATMMechineToolStripMenuItem_Click(ByVal sender As

System.Object, ByVal e As System.EventArgs) Handles

ATMMechineToolStripMenuItem.Click

FrmMainMenu.Show()

End Sub
Private Sub ReportsToolStripMenuItem_Click(ByVal sender As System.Object,

ByVal e As System.EventArgs) Handles ReportsToolStripMenuItem.Click

FrmMainMenu.Hide()

Frmlogin.Show()

End Sub

Private Sub AboutToolStripMenuItem_Click(ByVal sender As System.Object,

ByVal e As System.EventArgs) Handles AboutToolStripMenuItem.Click

„Me.Hide()

frmAbout.Show()

End Sub

End Class

Menu form:

Public Class FrmMainMenu

Private Sub cmdATM_Click(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles cmdATM.Click

Me.Close()

FrmATM.Show()

End Sub

Private Sub cmdexit_Click(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles cmdexit.Click

Me.Close()

End Sub

Private Sub FrmMainMenu_Load(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles MyBase.Load

End Sub

Private Sub cmdReports_Click(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles cmdReports.Click

Me.Hide()

Frmlogin.Show()

End Sub

Private Sub cmdabout_Click(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles cmdabout.Click

Me.Hide()

frmAbout.Show()

End Sub

End Class

Select Transaction Form:

Public Class frmgeneral

Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles Button1.Click

Me.Close()

„rsTrans.Close()

„rslog.Close()

„rsUser.Close()

FrmMainMenu.Show()

End Sub

Private Sub cmdBalance_Click(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles cmdBalance.Click

Me.Close()

frmAccountBalance.Show()

End Sub

Private Sub cmdWithdraw_Click(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles cmdWithdraw.Click

Me.Close()

frmAmount.Show()

End Sub

Private Sub cmdReport_Click(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles cmdReport.Click

Me.Close()

frmReport.Show()

End Sub

Private Sub frmgeneral_Load(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles MyBase.Load

End Sub

End Class

Balance Inquiry Form:

Public Class frmAccountBalance

Private Sub frmAccountBalance_Load(ByVal sender As System.Object, ByVal e

As System.EventArgs) Handles MyBase.Load

lblName.Text = Client_Name

lblcardNum.Text = Account_Number

lblDate.Text = ExpireDate

lblBalance.Text = Account_Balance

End Sub

Private Sub cmdclose_Click(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles cmdclose.Click

Me.Close()

frmgeneral.Show()

End Sub

End Class

Cash Withdrawal Form:

Imports Microsoft.VisualBasic.Strings

Public Class frmAmount

Private Sub frmAmount_Activated(ByVal sender As Object, ByVal e As

System.EventArgs) Handles Me.Activated

End Sub

Private Sub frmAmount_Load(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles MyBase.Load

End Sub

Private Sub txtRs_TextChanged(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles txtvalue.TextChanged

If Not IsNumeric(txtvalue.Text) Then

txtvalue.Text = “”
txtvalue.Focus()

End If

End Sub

Private Sub Button2_Click(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles cmdno.Click

Me.Close()

frmgeneral.Show()

End Sub

Private Sub cmdyes_Click(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles cmdyes.Click

Dim res As Integer

conncall()

„frmgeneral.Hide()

rsUser.Close()

rsUser.Open(“Select AccountBalance,cardnumber from client where

cardnumber = „” & Account_Number & “„”, conn,

ADODB.CursorTypeEnum.adOpenKeyset,

ADODB.LockTypeEnum.adLockOptimistic)

„Print(CStr(Account_Number))

If rsUser(0).Value < Val(txtvalue.Text) Then

MsgBox(“Your Account Balance is Not enough” & vbCrLf & “Please Reenter the

amount”, vbCritical, “Limit Exceeded”)

txtvalue.Text = “”

ElseIf Val(txtvalue.Text) > 25000 Then

MsgBox(“You cannot withdraw more than $10000″ & vbCrLf & “Please enter a

coorect amount again”, vbCritical, “Limit Exceeded”)

txtvalue.Text = “”

txtvalue.Focus()

ElseIf Val(txtvalue.Text) < 100 Then

MsgBox(“Invalid Amount” & vbCrLf & “You Can not withdraw amount less $

100″, vbCritical, “Invalid Input”)

txtvalue.Text = “”

txtvalue.Focus()

ElseIf Microsoft.VisualBasic.Strings.Right(txtvalue.Text, 2) <> “00” Then

MsgBox(“Invalid Amount” & vbCrLf & “Enter amount which is divisible by

100″, vbCritical, “Invalid Input”)

txtvalue.Text = “”

txtvalue.Focus()

Else

res = MsgBox(“Are you sure ?”, MsgBoxStyle.YesNo, “Confirm Transaction”)

End If

If res = 6 Then

rsUser.Close()

rsUser.Open(“Select * from Client”, conn)

cmd.CommandText = “update client set AccountBalance = AccountBalance – „”

& Val(txtvalue.Text) & “„ where CardNumber= „” & Account_Number & “„”

cmd.ActiveConnection = conn

cmd.Execute()

rsTrans.Close()

rsTrans.Open(“Select

AccountID,TransactionDate,TransactionTime,AmountWithdrawal from trans”)

cmd.CommandText = “insert into

trans(AccountID,TransactionDate,TransactionTime,AmountWithdrawal)

values(„” & Account_Number & “„,'” & Date.Today & “„,'” & DateTime.Now & “„,'”

& Val(txtvalue.Text) & “„)”

cmd.ActiveConnection = conn

cmd.Execute()

cash = Val(txtvalue.Text)

txtvalue.Text = “”

Me.Hide()

Form2.Show()

ElseIf res <> vbNo Then

txtvalue.Text = “”

txtvalue.Focus()

End If

End Sub

End Class

Statement Form:

Public Class frmReceipt

Private Sub frmReceipt_Load(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles MyBase.Load

conncall()

lblName.Text = Client_Name

lblcardNum.Text = Account_Number

lblcash.Text = cash

rsUser.Close()

rsUser.Open(“Select AccountBalance from Client where CardNumber = „” &

Account_Number & “„”, conn)

lblBalance.Text = rsUser(0).Value

rsUser.Close()

„lblamount.Caption = cash

End Sub

Private Sub cmdclose_Click(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles cmdclose.Click

Me.Close()

Client_Name = “”

Account_Number = “”

cash = 0

frmFinal.Show()

End Sub

End Class

Report Form:

Public Class frmReport

Private Sub frmReport_Load(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles MyBase.Load

GridTitle()

FillData()

End Sub

Private Sub GridTitle()

grid.Cols = 3

With grid

.set_TextMatrix(0, 0, “Transaction Date”)

.set_TextMatrix(0, 1, “Transaction Time”)

.set_TextMatrix(0, 2, “Amount Withdrawals”)

End With

End Sub

Private Sub FillData()

conncall()

Dim i As Integer

If rsTrans.State = 1 Then rsTrans.Close()

rsTrans.Open(“select * from trans where AccountID = „” & Account_Number &

“„”, conn)

i=1

If rsTrans.EOF <> True Then

While rsTrans.EOF <> True

grid.Rows = i + 1

With grid

.set_TextMatrix(i, 0, rsTrans(2).Value)

.set_ColWidth(0, 1500)

.set_TextMatrix(i, 1, rsTrans(3).Value)

.set_ColWidth(1, 2500)

.set_TextMatrix(i, 2, rsTrans(4).Value)

.set_ColWidth(2, 2500)

End With
i=i+1

rsTrans.MoveNext()

End While

rsTrans.Close()

Else

rsTrans.Close()

grid.Clear()

GridTitle()

End If

rsUser.Close()

rslog.Close()

End Sub

Private Sub cmdclose_Click(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles cmdclose.Click

Me.Close()

frmgeneral.Show()

End Sub

End Class

Administrator Login Form:

Public Class Frmlogin

Private Sub cmdok_Click(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles cmdok.Click

„check for correct password

If txtPassword.Text = “abc123″ And LCase(txtUsername.Text) =

“administrator” Then

„place code to here to pass the

„success to the calling sub

„setting a global var is the easiest

„LoginSucceeded = True

MDIMain.ReportsToolStripMenuItem.Enabled = True

Me.Close()
frmReportWindow.Show()

Else

MsgBox(“Invalid Password, try again!”, , “Login”)

txtPassword.Focus()

„SendKeys(“{Home}+{End}”)

End If

End Sub

Private Sub Frmlogin_Load(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles MyBase.Load

End Sub

Private Sub cmdcancel_Click(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles cmdcancel.Click

Me.Close()

FrmMainMenu.Show()

End Sub

End Class

Report:

Public Class frmReportWindow

Private Sub cmdClose_Click(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles cmdClose.Click

Me.Close()

FrmMainMenu.Show()

End Sub

Private Sub cmdDaily_Click(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles cmdDaily.Click

reportstr = “Daily”

Me.Hide()

frmview.Show()

End Sub

Private Sub cmdAll_Click(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles cmdAll.Click

reportstr = “All”

Me.Hide()

frmview.Show()

End Sub

Private Sub frmReportWindow_Load(ByVal sender As System.Object, ByVal e

As System.EventArgs) Handles MyBase.Load

End Sub

End Class

Public Class frmview

Private Sub frmview_Load(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles MyBase.Load

Dim obj As New CrystalReport1

CrystalReportViewer1.ReportSource = obj

If reportstr = “Daily” Then

CrystalReportViewer1.SelectionFormula = “{trans.TransactionDate} = #” &

Trim(Date.Today) & “# “

CrystalReportViewer1.Refresh()

„ElseIf reportstr = “Monthly” Then

„ CrystalReportViewer1.SelectionFormula = “{trans.TransactionDate} = #” &

Trim(Date.Today.Month) & “# “

„ CrystalReportViewer1.Refresh()

ElseIf reportstr = “All” Then

„CrystalReportViewer1.SelectionFormula = “{trans.TransactionDate} = „” &

Trim(Date.Today.Month) & “„ “

CrystalReportViewer1.Refresh()

End If

reportstr = “”

End Sub

End Class

8. SOFTWARE DESCRIPTION

8.1. The Front-End

Vb.Net 2019

Visual Basic (VB) is a programming language based on the original DOS

language called BASIC (Beginners‟ All-purpose Symbolic Instruction Code).

VB.NET 2019, an offshoot of Visual Basic, is an object-oriented programming

language based on VB that is implemented using the Microsoft .NET

framework. The basic syntax of the Visual Basic language remains unchanged in

VB.NET 2005, but includes additional features such as structured exception

handling and short-circuited expressions to enhance the infrastructure of the

programming language. Developers have found VB.NET to be controversial as

some of the software and developmental changes clash with the original

language within VB and have caused compatibility issues. Visual Studio .NET is

the predominant integrated development environment (IDE) that VB.NET

developers employ.

Visual Basic programmers supporting VB.NET indicate that language

constructs and user interface features in the newer system have caused

programming issues within the original VB system. Developers using VB.NET

recognize that the upgraded VB system incorporates contemporary object

oriented programming paradigms in a more stable environment than was

originally thought possible.

Visual Basic .NET is a programming language that can be used to create

WinForms or webapp applications and create programming based in any object-

oriented programming language (OOP), ADO.NET, Multithreading or Windows

Services. VB.NET programming utilizes concepts connected to string

encryption, forms inheritance, regular expressions and deployment.

8.2. The Backend

Ms-access:

In this project the backend is Microsoft Access.

Microsoft Access provides three methods to create database:

Create a database using a database wizard.

Create a database using a template

Create a database without using a database wizard

Queries:

We use queries to view, change, and analyze data indifferent ways. You can also

use them as a source of records for forms, reports and data access pages. There

are several types of queries in MS-ACCESS.

Types of queries in ms-access:

1. Select Queries

2. Parameter Queries

3. Cross tab Queries

4. Action Queries

5. SQL Queries

Accessibility features in ms-access:

View and print lists of all available shortcut keys Use the keyboard to define

relationships or copy text boxes or other controls on forms and reports, and

rearrange columns in Datasheet view.

Create a toolbar that contains only the buttons and menus you use most often

for the current database or for all your databases. You can also increase the size

of the buttons and group related buttons together. Set menus to display all

commands all the time. You can also change toolbars to appear as they did in

earlier versions of Office.

Create custom colors or change the background color for a section or control on

a form or report.

Insert repeated entries in a column quickly by using the keyboard.

Automatically correct common typing errors and even specify a list of errors

you want corrected as you type.

The MS-ACCESS is a good and easier environment for creating database and

also includes reliable connectivity to this project. Just we have to write coding

for database connectivity (odbc) for our datasource is enough.

9. TESTING

Description:

v Software testing is a critical element of software quality assurance and

represents the ultimate review of specification, design and code

generation. The increasing visibility of software as a system element and the

attendant “cost” associated with a software failure are motivating force for well

planned, through testing.

10. Testing:

v Testing is the one of step in the software process that could be viewed as

destructive rather than constructive.

v Software is tested from different perspectives :

1. White box test.

1. Black box test

10.1 Whitebox Test:

v White box tests focus on the program control structure, internal program

logic is exercised using these techniques.

10.2 Blackbox Test:

v Black box testing is software requirements are exercised and derive sets of

inputs conditions that will fully exercise all functional requirements for a

program this testing is also called “behavioural testing”.

10.3 Level Of Testing:

The details of software functionality & test conditions are satisfied fully on

behavioural based so that choose for black box testing.

10.3.1 Blackbox Testing:

v by incorrect or missing function

applying block box testing in my project “ATTM SYSTEM”

v interface errors

v errors in external database access behaviour (or) performance error

v initialization and termination error its mainly used for uncover errors in

software functions

10.3.2 Behavioural testing:

It is possible to simulate the behaviour of a real time system and consequence of

external events. In this test, we check in client side if the client enters incorrect

pin number for more than “three” times the applications will be closed.
10.3.3 System Testing:

Software and hardware are integrated and full range of system test is conducted

so that we check for interrupt priority and the performance of each interrupt

handling procedures. In this test check on each options of banking process.

11. USER MANUAL

The client can only login if the Server is at run.

The client can give their account number, password to login. If their login is

correct the client main menu is displayed.

The client can view the account, and they can withdrawal the required amount,

view the transaction details.

These operations can also do if they enter the pin number correctly. if they

enter the pin number incorrectly the application will be closed.

The client has right to deposit the money.

12. CONCLUSION

Future Enhancements

Loan Facility

Email and mobile alerts.

Active Tracing of Fraudulent activities

Security upgrades like Visual Sensors with burglar alarms, Biometric

Identification procedures etc.

Additional Features

Double Layered Security

Secure Login.