CHAPTER-1

PROBLEM STATEMENT

To develop an “ Automatted Teller Machine” system for the global

reliable bank. It should be able to provide banking services for all the people
at any time and also give an easy access to everyone , anywhere. The client
can access the ATM by entering his/her pin [Link] client will be able to
withdraw ; deposit & transfer cash and also provide mini [Link] ATM
servicing executive will be one to replenish the cash in ATM and also the
account detail of the needed clients. This type of system is be implemented the
bank to increase their services and to reach all the possible cities.

1
 CHAPTER-2
PROJECT SCOPE

The project scope of the Automatted Teller Machine is that it can be used
by any of the clients registered with the bank and provide them with easy access and
safer way to do their [Link] scope of our product is the better and easy way
of interaction. This is used to manage the customer account and help them to access
all the transactions through ATM without any complexity and handled quickly by the
users.

2
 CHAPTER-3
SOFTWARE REQUIREMENT SPECIFICATION
1. INTRODUCTION

1.1 PURPOSE

The Automated Teller Machine system purpose of the product is to support the banking
system by which all the users can access account. The users can be benefited by this software by
performing the operation like money withdrawal, deposit, money transfer and so [Link] software
requirement document is an official statement of what is required of the system developers. It
should include both system and the user requirements.

1.2 DOCUMENT CONVENTIONS

The standard conventions that were followed when writing ‘SRS’ are the main headings
which was given the font size is 12,capitalized and bold faced. The font style of the entire
document is given in ‘TIMES NEW ROMAN’.

1.3 INTENDED AUDIENCE AND READING SUGGESTION

One has to start with the overview of the product to understand the application better. The
product mainly intended to all banking system who wants to provide ATM for easy banking for all
the Customers.

1.4 PRODUCT SCOPE

3
 The scope of our product is the better and easy way of interaction. This is used to manage the
customer account and help them to access all the transactions through ATM without any
complexity and handled quickly by the users.

1.5 REFERENCE

 [Link]
 [Link]

2. OVERALL DESCRIPITION

2.1 PRODUCT PERSPECTIVE

The product was mainly created to replace the existing system which was
very tedious and time consuming to follow.

Figure 1.2 Product perspective diagram

4
 DEPOSIT MONEY
WITHDRAWL

FUND
MINI MONEY
STATEMENT

ATM
AUTHENTICATIO
N

FUND ATM
TRANSFER SECURITY

2.2 PRODUCT FEATURES

 User login
 Money withdrawal
 Mini statement
 Money deposit
 Officer login
 Account detail
 Account deposit

2.3 USER CLASSES AND CHARACTERISTICS

The product document is written is simpler manner. So even the person who dont
have knowlege about product can understand in good manner. The document is also written
in their mother tongue language.

2.4 OPERATING ENVIRONMENT

5
 OPERATING SYSTEM - WINDOWS XP
PROCESSOR - Pentium4
RAM - 256 MB
HARD DISK - 40GB

2.5 DESIGN AND IMPLEMENTAION CONSTRAINT

FRONT END - JAVA(NETBEANS IDE)

BACK END - MS-ACCESS

PROTOCOL - HTTP,TCP/IP

2.6 USER DOCUMENTATION

 Along with the software product, a user manual would be written to help people
understand the working methodology and usage of the developed prototype
system.


 The user manual would follow common user documentation styles capturing
purpose and scope of the product along with key system features and
operations.

.2.5 DESIGN AND IMPLEMENTAION CONSTRAINT

FRONT END - JAVA(NETBEANS IDE)

BACK END - MS-ACCESS

PROTOCOL - HTTP,TCP/IP

6
2.6 USER DOCUMENTATION
 Along with the software product, a user manual would be written to help people
understand the working methodology and usage of the developed prototype
system.
 The user manual would follow common user documentation styles capturing
purpose and scope of the product along with key system features and
operations.

2.7 ASSUMPTION AND DEPENDENCIES

The entire product is based on networking. If u want to know any details about the
accounts you can ask the bank and they will give the details. Whenever you do the
transaction in atm it will automatical give the account [Link] limit for the transaction
process in my product.

[Link] FEATURES

The ATM machine software requires a various functional requirement (ie) the user login,
performing operation like withdrawal of money, money transfer, mini statement, deposit and so
on.

3.1 FEATURE 1:USER LOGIN

3.1.1 Description and priority:

The user login is used to provide a pin number for all the user who have the account in the
bank which is unique.

3.1.2 Stimulus/response sequences:

[Link] the pin number in the given box.

2. If both matches the specified account will be opened to perform the
desired operation.

7
3. Else the dialogue box with invalid user name and password is
displayed. Then press submit button.

3.1.3 Functional requirement:

 Username
 Password

3.2 FEATURE 2:MONEY WITHDRAWAL

3.2.1 Description and priority:

This module is used to withdraw money from ATM which is the main function of the
ATM as specified by the user. This has the highest priority.

3.2.2 Stimulus/response sequences:

[Link] the desired amount.

[Link] ok button.
3. The specification money will be made available to the user.

3.2.3 Functional requirement:

 Amount
 Password

3.3 FEATURE 3:MINI STATEMENT

3.3.1 Description and priority:

This module is used to print the details of the balance amount and the various
transaction that were done previously by the specified user.

8
3.3.2 Stimulus/response sequences:

[Link] the user need to know the transaction that have been previously ,the user can
request.

3.3.3 Functional requirement:

 Pin number

3.4 FEATURE 4:MONEY DEPOSIT

3.4.1 Description and priority:

This module allow the user to deposit the specified amount of their account. This
makes the work of the user very easy. It has medium priority.

3.4.2 Stimulus/response sequences:

[Link] the user is made to enter the amount that is to be deposited.

[Link] the account number of the user to which it has to be given is asked to enter.

3.4.3 Functional requirement:

 Amount
 Pin number

3.5 FEATURE 5:OFFICER LOGIN

3.5.1 Description and priority:

9
 The officer login is used to provide a pin number for the officer who able to access
the specified operation.

3.5.2 Stimulus/response sequences:

[Link] the user name.
[Link] the pin number
[Link] both matches the specified account will be opened to perform the
desired operation.
[Link] the dialogue box with invalid user name and password is displayed

3.5.3 Functional requirement:

 User name
 Password

3.6 FEATURE 6:ACCOUNT DETAIL

3.6.1 Description and priority:

This module allows the officer to view the account detail of all the users who
have account in the bank which is unique. The officer has to enter the pin number of the
user to get all his/her details of the account maintained in the bank.

3.6.2 Stimulus/response sequences:

[Link] the pin number

[Link] both matches the specified account will be opened to perform the
desired operation.
[Link] the dialogue box with invalid user name and password is displayed

3.6.3 Functional requirement:

10
  Amount of deposit

3.7 FEATURE 7:ACCOUNT DEPOSIT

3.7.1 Description and priority:

This module allows the officer to deposit the amount into the ATM system. This
is given higher priority since every user can withdraw money only if the officer deposit the
money in the system.

3.7.2 Stimulus/response sequences:

[Link] the amount in the given box.

3.7.3 Functional requirement:

 Amount of deposit

3.7.2 Stimulus/response sequences:

[Link] the amount in the given box.

3.7.3 Functional requirement:

 Amount of deposit

4. EXTERNAL INTERFACE REQUIREMENT

4.1 USER INTERFACES

11
4.2 HARDWARE INTERFACE - Nil

4.3 SOFTWARE REQUIREMENT

Product Devoleped in Java and Ms access. Then we are using different prtotocols.

4.4 COMMUNICATION INTERFACE

12
  Client on internet will be using HTTP/HTTPS protocol.
 Client on intranet will be using TCP/IP protocol.

5. NON FUNCTIONAL REQUIREMENT

5.1 Performance requirements:

The software should be able to perform all the operations specified by the user
within certain allotted [Link] that the user may not wait too [Link] should also be able to
perform all the requests asked by the user.

5.2 Safety requirements:

Sometimes when the same account is used by different users at different places
may lead to wrong updating the money after withdrawal which can be presented by using
lock system (i.e.) the user who enters first into the account will make that account to appear
as locked to all the other users of the account.

5.3 Security requirements

The ATM machine is prone to malfunctions (ie) a wrong user who is using others
card and knows his/her .Pin number can be allowed to access others account

and withdraw money. Therefore these types of malfunctions can be prevented by

tightening the security by providing cameras,etc..

13
5.4 Software quality attributes

Some of the quality characteristics for the product that will be important to either the
customers or developers
Are listed below,
1. Adaptability
It is defined as the ability of the system to adapted to environmental and
functional needs

2. Availability.
It is defined as the probability that is fit for operation at time.

3. Correctness.
It is defined as the degree to which the software performs its required
functions.
4. Flexibility.
It is defined as the effort required to modify an operational program.

5. Interoperability
It is defined as the effort required to couple one system to another.

6. Testability
It is defined as the effort required to test a program to ensure that it performs
its intended functions.

7. portability
It is defined as the effort required to transfer the program from one
hardware or software to another.
[Link]

14
 It is defined as the effort required to learning, operating, preparing
input and output of the program

6. APPENDIX

ATM – Automated Teller Machine

CHAPTER-4
SYSTEM ANALYSIS

The next workflow in the RUP is the Analysis of the requirements which have been
specified in the SRS. The Analysis is done with the help of Rational Requisite Pro. The
three views or reports which form the basis for analysis are
1. Attribute Matrix
2. Traceability Matrix

15
 3. Traceability Tree
4.1 ATTRIBUTE MATRIX
The Attribute Matrix view is a spreadsheet like display that lists the requirements of
a specific requirements type and their attributes. Requirements are arranged in rows, listed
by tag number and followed by requirement name. Attributes are arranged in columns.

4.1.1 STACKHOLDER REQUIREMENT SPECIFICATION

4.1.2 USECASE REQUIREMENT SPECIFICATION

16
4.2 TRACEABILITY MATRIX

17
 Traceability Matrix is a view that illustrated the relationships between requirements
of the same or different types. We can use this matrix to create, modify and delete
traceability relationships and view indirect relationships and view direct relationships and
traceability relationships with a suspect state. We can also use the traceability matrix to
filter and sort the requirements and columns requirements separately.

4.2.1 STAKEHOLDER VS STAKEHOLDER REQUIREMENT TYPE

4.2.2 STAKEHOLDER VS USECASE REQUIREMENT TYPE

18
4.2.3 USECASE VS USECASE REQUIREMENT TYPE

19
4.3 TRACEABILITY TREE

20
 A view that displays all internal and external requirements traced to or from a
requirement. The traceability tree only displays the first level project traceability.

4.3.1TRACEABILITYTREE(TRACEDINTO)-USECASE
REQUIREMENT TYPE

4.3.3TRACEABILITYTREE(TRACEDINTO)-STAKEHOLDER
REQUIREMENT TYPE

21
4.3.3TRACEABILITYTREE(TRACEDOUTOFF)-STAKEHOLDER
REQUIREMENT TYPE

22
 CHAPTER-5
SYSTEM DESIGN

23
5.1 USECASE DIAGRAM
A Use Case Diagram is a graph of actors, a set of use cases enclosed by a system
boundary, communication association between the actors and the use cases and
generalization among the use cases. A use case corresponds to a sequence of transactions,
in which each transaction is invoked from outside the system and engages internal objects
to interact with each other. An actor is anything that interacts with the use case.
5.1.1 USECASE DIAGRAM FOR ATM SYSTEM

deposit
databaseadmin

a/c details

authentication
atmsystem
bank

ministatement

transaction

am ount deposit fund transfer accout holder

withdraw

Figure 5.1 Use Case Diagram

5.2 ACTIVITY DIAGRAM

24
 Activity Diagrams illustrate the dynamic nature of a system by modeling the flow
of control from activity to activity. An activity represents an operation on some class in
the system that results in a change in the state of the system. Typically, activity
diagrams are used to model workflow or business processes and internal operation.

5.2.1 ACCOUNT DETAIL

New Sw imlane : databaseadmin New Sw imlane2 : atmsystem

display admin
screen

enter acc no
check for existing accno

not valid valid

creates a new display acc

account details

Figure 5.2 Account detail Activity Diagram

5.2.2 AUTHENTICATION

25
 USER SYSTEM

Displays login
screen

Enter the Enter the

Username Password

invalid

valid

Log into the

system

Figure 5.3 Authentication Activity Diagram

5.2.3 MINI STATEMENT

26
New Sw imlane7 : accout holder New Sw imlane8 : atmsystem

displays
screen

choose the type

of acc

prints the latest

transaction

Figure 5.4 Mini statement Activity Diagram

27
5.2.4 FUND TRANSFER

New Sw imlane9 : accout holder New Sw imlane10 : atmsystem

displays
transfer screen

enters senders enter amount

accno

enters receivers
acc no

if false

validation

if true

transfers amt displays msg to

both receivers

Figure 5.5 Fund transfer Activity Diagram

5.2.5 AMOUNT WITHDRAWAL

28
 New Sw imlane13 : accout holder New Sw imlane14 : atmsystem

displays
withraw screen

enters the enter the amt

accno

if not valid

accno&amt validation

if valid

provide the amt displays

balance amt

Figure 5.6 Amount withdrawal Activity Diagram

29
5.2.6 TRANSACTION SCREEN

New Sw imlane13 : accout holder New Sw imlane14 : atmsystem

displays
withraw screen

enters the enter the amt

accno

if not valid

accno&amt validation

if valid

provide the amt displays

balance amt

Figure 5.7 Transaction screen Activity Diagram

5.3 CLASS DIAGRAM

30
 A Class Diagram is a collection of static modeling elements such as classes and
their relationships, connected as a graph to each other and to their contents. These diagrams
show the static structures of the model.

5.3.1 AUTHENTICATION

authenticationbry authenticationctrl

username username
password password

submit the username & password() display screen()

check for validity()
next screen()
error message()

authenticationety

username
password

validate()
valid()
invalid()

Figure 5.8 Authentication Class Diagram

5.3.2 CASH WITHDRAW

31
 withraw bound withraw ctrl

acc no accno
amt amt

submit() process()
display()

withraw entity

acc no
amt

validation()

Figure 5.9 Cash withdraw Class Diagram

5.3.3 AMOUNT TRANSFER

32
 amtdep bound amt dep ctrl

acc no acc no
amt deposit amt deposit

submit() process()
display()

amt dep entity

acc no
amt deposit

validation()

Figure 5.10 Amount transfer Class Diagram

5.3.4 MINI STATEMENT

ministmt bound mini stmt ctrl

(from authentication bound)
accno
transaction detail accno
transaction detail
submit()
display() process()

mini stmt entity

accno
transaction detail

check validation()

Figure 5.11 Mini statement Class Diagram

5.3.5 ACCOUNT DETAIL

33
 a/c det bound a/c details ctrl

acc no acc no
a/c detail a/c detail

submit() process()
display()

a/c det entity

acc no
a/c detail

provide info()

Figure 5.12 Account detail Class Diagram

5.3.6 OFFICER AMOUNT DEPOSIT

deposit bound deposit ctrl

amt amt

submit() process()
display()

deposit entity
(from amt dep entity)

amt

privide info()

Figure 5.13 Officer amount deposit Class Diagram

5.4 SEQUENCE DIAGRAM

34
 Sequence Diagrams are easy and intuitive way of describing the behavior of a
system by viewing the interaction between the system and its environment. A sequence
diagram shows the interaction arranged in a time sequence. It shows the object
participating by their life lines and the messages they exchange, arranged in a time
sequence.
5.4.1 AUTHENTICATION

: Administrator : authenticationbry : authenticationctrl : authenticationety

display the screen()

username & password()

submit uid & pwd()

checks for validity()

validate()

if valid
valid()

nextscreen()

if not valid

not valid()
error message()

Figure 5.14 Authentication Sequence Diagram

35
5.4.2 CASH WITHDRAW

: accout holder : atmsystem : withraw bound : withraw ctrl : withraw entity

enter accno & amt provide info check accno &amt

validation

provide money provide msg

display msg error msg

Figure 5.15 Cash withdraw Sequence Diagram

36
5.4.3 AMOUNT DEPOSIT

: accout holder : amtdep bound : atmsystem : amt dep ctrl : amt dep entity

submit info check valid accno

enter the accno deposit amt
validation

valid:deposit amt valid: provide info

not valid display msg error msg

Figure 5.16 Amount deposit Sequence Diagram

5.4.4 AMOUNT TRANSFER

37
 : accout holder : atmsystem : fund transfer bound : fund transfer ctrl : fund transfer entity

sender&recever accno&amt provide info check accno&amt

validation

valid: transfer amt valid: provide info

not valid:disp msg not valid:error msg

Figure 5.17 Amount transfer Sequence Diagram

5.4.5 MINI STATEMENT

: accout holder : atmsystem : ministmt bound : mini stmt ctrl : mini stmt entity

enter accno provide accno check for valid acc

validation

valid:provide mini info valid:provide info

not valid:disp msg not valid:error msg

Figure5.18 Mini statement Sequence Diagram

5.4.6 ACCOUNT DETAIL

38
 : databaseadmin : a/c det bound : a/c details ctrl : a/c det entity
enter accno provide info check account
validation

valid:disp accdetail valid:provide info

not valid: display notvalid:error msg

Figure5.19 Account detail Sequence Diagram

5.5 COLLABORATION DIAGRAM

39
 A collaboration diagram represents a collaboration, which is a set of objects related
in a particular context, and interaction, which is a set of messages exchanged among the
objects within the collaboration to achieve a desire outcome.

5.5.1 AUTHENTICATION

2: username & password()

: Administrator : authenticationbry

1: display the screen()

8: nextscreen()
11: error message()

5: validate()
3: submit uid & pwd() 6: if valid
9: if not valid

4: checks for validity()

7: valid()
: authenticationctrl 10: not valid() : authenticationety

Figure 5.20 Authentication Collaboration Diagram

40
5.5.2 CASH WITHDRAW

1: enter accno & amt

: accout holder : withraw bound

6: provide money
8: display msg

4: validation
: atmsystem 2: provide info

3: check accno &amt

5: provide msg
7: error msg : withraw entity
: withraw ctrl

Figure 5.21 Cash withdraw Collaboration Diagram

5.5.3 AMOUNT DEPOSIT

41
 : amtdep bound 3: enter the accno deposit amt : atmsystem

6: valid:deposit amt
8: not valid display msg

1: submit info
: accout holder
4: validation

2: check valid accno

5: valid: provide info

: amt dep ctrl 7: error msg : amt dep entity

Figure 5.22 Amount deposit Collaboration Diagram

5.5.4 MINI STATEMENT

42
 1: enter accno

: accout holder : ministmt bound

6: valid:provide mini info

: atmsystem
8: not valid:disp msg

4: validation
2: provide accno

3: check for valid acc

5: valid:provide info
7: not valid:error msg : mini stmt entity
: mini stmt ctrl

Figure 5.23 Mini statement Collaboration Diagram

43
5.5.5 FUND TRANSFER

1: sender&recever accno&amt

: accout holder : fund transfer bound

6: valid: transfer amt

8: not valid:disp msg

4: validation
2: provide info
: atmsystem

3: check accno&amt

5: valid: provide info

7: not valid:error msg : fund transfer entity
: fund transfer ctrl

Figure 5.24 Fund transfer Collaboration Diagram

5.5.6 ACCOUNT DETAIL

1: enter accno

: databaseadmin : a/c det bound

6: valid:disp accdetail
7: not valid: display

4: validation
2: provide info

3: check account

5: valid:provide info
: a/c details ctrl 8: notvalid:error msg : a/c det entity

Figure 5.25 Account detail Collaboration Diagram

44
5.6 COMPONENT DIAGRAM
Component diagram models the physical components such as source codes,
executable programs, user interface in a design. These high level physical components may
or may not be equivalent to many smaller components we use in creation of application.

5.6.1 MAIN COMPONENT DIAGRAM

atm system

authentication

acc details

office deposit

transaction

ministatement

atm body atm Spec

atm exe

Figure 5.26 Main Component Diagram

45
5.6.2 AUTHENTICATION

Authentication

authenticationbody AuthenticationSpec

authentic
ationexe

authenbrybody authenbryspec
authenbr
yexe

authencrtlbody authencrtlspec
authencrt
lexe

authenetybody authenetyspec
authenet
yexe

Figure 5.27 Authentication Component Diagram

46
5.6.3 ACCOUNT DETAIL

account detail

accdt body accdtSpec

accdt
exe

accdt boundryBody accdt boundry spec

accdt
boundry exe

accdt ctrlbody accdt ctrl spec

accdt ctrl
exe

accdt entity body accdt entity spec

accdt
entity exe

Figure 5.28 Account detail Component Diagram

47
5.6.4 CASH WITHDRAW

transaction

trans Body trans Spec

trans exe

with boundBody with boundSpec

with bound
exe

with ctrlbody with ctrlSpec

with ctrl
exe

with entityBody with entitySpec

withentity
exe

Figure 5.29 Cash withdraw Component Diagram

48
5.6.5 TRANSACTION

transaction

trans Body trans Spec

trans
exe

with bound Body with bound Spec dep bound Body dep bound Spec fund bound Body fund bound Spec

with boun dep bound fund bound

exe exe exe

with ctrl body dep ctrl Body dep ctrl Spec fund ctrl Body fund ctrl Spec
with ctrl Spec fund ctrl
with ctrl dep ctrl
exe exe
exe

dep entity Spec fund entity Body fund entitySpec

with entity Body with entitySpec dep entity Body fund entity
dep entity exe
with entity exe
exe

Figure 5.30 Transaction Component Diagram

49
5.6.6 OFFICER DEPOSIT

office deposit

off depBody off dep Spec

off dep
exe

off dep bound Body off dep bound Spec

off dep
bound exe

offdep ctrl Spec

offdep ctrl Body
offdep
ctrl exe

offdep entity Body offdep entity Spec offdep

entity exe

Figure 5.31 officer deposit Component Diagram

50
5.7 DEPLOYMENT DIAGRAM

Deployment diagram shows the configuration of run time processing elements and
the software components, processes and objects that live in them.

5.7.1 ATM SYSTEM

client2

printer
client1

ATM
server

camera
scanner

Figure 5.33 ATM System Deployment Diagram

51
 CHAPTER-6
SYSTEM DEVELOPMENT

6.1 AUTHENTICATION
This feature of the product allows only the authentication user to work with the
[Link] ensures security and restricts any unauthorized persons from accessing the
application.
6.2 CASH WITHDRAW
This feature enables the authenticated user to enter into the system and withdraw
the desired cash after entering his/her unique pin [Link] the pin number matches then
the user will be provided with the cash.

6.3 AMOUNT DEPOSIT

This feature enables the authentication user to deposit the required cash into his/her
account in a very easy and a quicker way.
6.4 LECTURER DETAILS
The lecturer details are maintained by the administrator. This modules
update, view and insert Lecturer information. The lecturer name, date of birth, address, etc.,
are collected from the lecturer.
6.5 AMOUNT TRANSFER
This feature will enable the user to transfer the required cash from his/her account
to the desired receiver account When this is done,the user will get the desired message.
6.6 MINI STATEMENT
This feature will enable the user to get his/her current account balance along with
the type of lastly done transaction.
6.7 ACCOUNT DETAIL
This feature is exclusively meant for administrative [Link] the account
number of the required client.

52
 CHATER-7
SYSTEM IMPLEMENTATION

7.1 SYSTEM PREREQUISITE

HARDWARE REQUIREMENT
Processor – Pentium II 433 MHz or above
RAM – 256 MB
Hard disk – 10 GB or above
SOFTWARE REQUIREMENT
Operating system – Windows Xp
JAVA version 1.6
NET BEAN 6.1
MS Access
7.2 STEP TO INSTALL SOFTWARE
1. Check whether the system has Windows Xp OS, if not install the OS in the
corresponding system.
2. Check whether the system has java development kit 1.6, if not install the java
development kit 1.6 in the corresponding system.
3. Check whether the system has MS Access , if not install the MS Access in the
corresponding system.
4. Check whether the system has Rational Administrator, if not install the Rational
Administrator in the corresponding system.
5. Then load the application in a device.
6. Set the path of the application to the path where the prerequisite software is
installed.
7. Then double click on the application to use it.

53
 CHAPTER-8
SYSTEM TESTING

8.1. TEST PLAN

8.1.1 PROJECT DESCRIPTION

The four basic steps in project are
1. Extract the problem domain statement from the user.
2. Classify into nouns and verbs based on the Noun Phrase Approach.
3. Generate the classes.
4. Place the operations in appropriate classes.
8.1.2 RELATED DOCUMENTS
The related documents in our project are project proposal and plan, Software
Requirements Specification, Software Design Specification and test plan.
8.1.3 TESTING STRATEGY
Unit test and Functional test is used in each phase of testing.
8.1.4 TESTING LEVEL PLAN
White Box Testing is given higher priority than Black Box Testing.
8.1.5 UNIT TEST
Unit test is generally accomplished by the person who wrote the code. Generally
white box testing is used at this level, since errors in logic are easier to find when testing
each path through the code.
8.1.6 MODULE TEST
Module testing is usually done by a single programmer or a small group of
programmers writing units that work together in a single module. Test cases are often used
for the module testing, especially if the module is self contained.
8.1.7 INTEGRATION TEST
Usually the development team handles integration test. Integration test is best
accomplished incrementally, by adding one module at a time to isolate errors.

54
8.1.8 ALPHA TEST
In this test, “Internal” testers run live data through the system to shake out bugs not
found in integration test, the customer may wish to observe the alpha test or to provide
some o the “Real” data.
8.1.9 BETA TEST
Beta test is the next step, where the programmers actually released to the customer
with the understanding that the program is still being tested. The customer agrees to stress
the application and to report any discovered bugs or problems to the development team.
The team agrees to be a “Friendly” user but to really put the system through its paces,
trying to break it.
8.1.10 REGRESSION TEST
After the product is released, errors may be found or enhancements suggested by the
customers in the field. As these are corrected or implemented, the rest of the system must
also be tested again to make sure that the new fixes did not break any of the old code.
Regression test is usually an automated script that runs a set of test cases known to exercise
the entire system.
8.1.11 USABILITY TEST
Usability testing is a special form of testing that looks for bugs not in the
functionality of the program, but in the layout and utility of the user interface. This step is
often a prototype before the actual system code is written, so it is easy to change if needed.

55
 CHAPTER-9

CONCLUSION AND FUTURE ENHANCEMENTS

The automated teller machine was implemented to reach more number of cities
and also to provide easier,safer and secure way to access their accounts and also to do their
required transaction. In futher, the machine could be improved by setting videocamera’s
improve the security at ATM and also provide other services like cheque request,help
services etc.,

APPENDIX 1

56
 SAMPLE CODE

/* SELECT MAIN */
import [Link].*;
import [Link].*;
import [Link].*;
import [Link].*;
import [Link].*;
class selectmain extends JFrame implements ActionListener
{
Int t=0,s=0,m=0;
Connection con;
JFrame frame;
JButton b1,b2,b3;
JLabel l1,l2;
public int t=1;
ImageIcon i1;
public selectmain()
{
frame=new JFrame("Main screen");
Container cp=[Link]();
[Link](null);
l1=new JLabel("ATM SYSTEM");
[Link](new Font("Arial",[Link],36));
[Link](200,20,750,50);

[Link]([Link]);
[Link](l1);
i1=new ImageIcon("[Link]");

57
l2=new JLabel(i1);
[Link](0,0,1024,750);
[Link](l2);
b1=new JButton("ENTER THE ACCOUNT NO");
[Link](650,300,150,30);
[Link](this);
[Link]([Link]);
[Link](b1);
b2=new JButton("ENTER THE PIN NUMBER");
[Link](650,360,150,30);
[Link](this);
[Link]([Link]);
[Link](b2);
b3=new JButton("EXIT");
[Link](650,420,150,30);
[Link](this);
[Link]([Link]);
[Link](b3);
[Link](1024,750);
[Link](true);
}
public void actionPerformed(ActionEvent a)
{
if([Link]()==b1)
{
[Link](false);
new application1();
}
if([Link]()==b2)
{
[Link](false);

58
new login();
private void initComponents() {
label1 = new [Link]();
button1 = new [Link]();
button2 = new [Link]();
button3 = new [Link]();
button4 = new [Link]();
button5 = new [Link]();
setDefaultCloseOperation([Link].EXIT_ON_CLOSE);
setFont(new [Link]("Arial", 1, 12));
[Link](new [Link]("Arial", 1, 12));
[Link]("CHOOSE THE DESIRED OPTION");
[Link](new [Link]("Arial", 1, 12));
[Link]("CASH WITHDRAW");
[Link](new [Link]("Arial", 1, 12));
[Link]("CASH TRANSFER");
[Link](new [Link]("Arial", 1, 12));
[Link]("CASH DEPOSIT");
[Link](new [Link]("Arial", 1, 12));
[Link]("MINI STATEMENT");
[Link](new [Link]("Arial", 1, 12));
[Link]("HOME");{
try
{
con=[Link]("jdbc:odbc:crs");
st=[Link]();
frame=new JFrame("APPLICATION FORM");
Container cp=[Link]();
[Link](null);
ll=new JLabel("APPLICATION FORM");
[Link](new Font("Arial",[Link],34));

59
[Link](250,20,750,50);
private void initComponents()
{
public static void main(String args[]) {
[Link](new Runnable() {
public void run() {
new NewJFrame3().setVisible(true);
}
});
}
button2 = new [Link]();
label1 = new [Link]();
label2 = new [Link]();
label3 = new [Link]();
textField1 = new [Link]();
textField2 = new [Link]();
button1 = new [Link]();
textField3 = new [Link]();
button3 = new [Link]();
[Link]("button2");
setDefaultCloseOperation([Link].EXIT_ON_CLOSE);
[Link](new [Link]("Arial", 1, 12));
[Link]("CASH DEPOSIT");
[Link]("Enter amount");
[Link]("Enter pinno");
[Link]("2000");
[Link]("4321");
[Link]("OK");
[Link]("! Successfully deposit");
[Link]("OK");
[Link] layout = new [Link](getContentPane());

60
 getContentPane().setLayout(layout);ls2=new JLabel("Available:");
[Link](new Font("Arail",[Link],13));
[Link](100,140,80,30);
[Link]([Link]);
[Link](ls2);
ls3=new JLabel("");
[Link](new Font("Arail",[Link],13));
[Link](200,140,30,30);
// Variables declaration - do not modify
private [Link] button1;
private [Link] button2;
private [Link] jFrame1;
private [Link] jFrame2;
private [Link] jFrame3;
private [Link] jFrame4;
private [Link] label1;
private [Link] label2;
private [Link] label3;
private [Link] textField1;
private [Link] textField2;
private [Link] textField3;
// End of variables declaration
[Link](ls9);
t1=new JTextField(25);
[Link](500,100,230,30);
[Link](t1);
t2=new JTextField(25);
[Link](500,140,230,30);
[Link](t2);
t4=new JTextField(25);
[Link](500,220,230,30);

61
[Link](t4);
private void initComponents() {
label1 = new [Link]();
label2 = new [Link]();
textField1 = new [Link]();
button1 = new [Link]();
label3 = new [Link]();
label4 = new [Link]();
label5 = new [Link]();
label6 = new [Link]();
label7 = new [Link]();
label8 = new [Link]();
label9 = new [Link]();
label10 = new [Link]();
label11 = new [Link]();
label12 = new [Link]();
button3 = new [Link]();
setDefaultCloseOperation([Link].EXIT_ON_CLOSE);
[Link](new [Link]("Arial", 1, 12));
[Link]("MINI STATEMENT");
[Link]("Enter pin no:");
[Link]("4321");
[Link]("OK");
[Link]("name:");
[Link]("accno:");
[Link]("phno:");
[Link]("aarthi");
[Link]("101010");
[Link]("988888880");
[Link]("Trans type lastly done:");
[Link]("CASH DEPOSOIT");

62
 [Link]("current bal:"); [Link]("319901");
[Link]("EXIT");
[Link] layout = new [Link](getContentPane());
getContentPane().setLayout(layout);
[Link](
[Link]([Link])
addGroup([Link]()[Link]("JUL");
[Link]("AUG");
[Link]("SEP");
[Link]("OCT");
[Link]("NOV");
[Link]("DEC");
[Link](c3);
c4=new JComboBox();
[Link](660,180,70,30);
for(int i=1960;i<=1990;i++)
[Link](i);
[Link](c4);
ta1=new JTextArea(40,10);
[Link](500,260,230,65);
[Link](ta1);
sp=new JScrollPane(ta1,JScrollPane.VERTICAL_SCROLLBAR_ALWAYS,
JScrollPane.HORIZONTAL_SCROLLBAR_ALWAYS);
[Link](500,260,230,65);
[Link](sp);
addno();
[Link](false);
b1=new JButton("OK");
[Link](350,580,100,35);
[Link](this);
[Link]([Link]);

63
[Link](b1);
b2=new JButton("Cancel");
[Link](550,580,100,35);
[Link](this);
[Link]([Link]);
[Link](b2);
private void initComponents() {
label1 = new [Link]();
button1 = new [Link]();
button2 = new [Link]();
setDefaultCloseOperation([Link].EXIT_ON_CLOSE);
[Link](new [Link]("Arial", 1, 12));
[Link]("DO YOU WANT TO PROCEED WITH ANY TRANSACTION");
[Link]("YES");
[Link]("NO");
[Link] layout = new [Link](getContentPane());
getContentPane().setLayout(layout);
[Link]([Link]([Link]
[Link])[Link]("");
[Link]("");
[Link]([Link]([Link](1)));
[Link]([Link]([Link](2)));
[Link]([Link]([Link](3)));
}
}
catch(Exception e)
{}
}
public void actionPerformed(ActionEvent a)
{
try

64
 private void initComponents() {
label1 = new [Link]();
button1 = new [Link]();
button2 = new [Link]();
button3 = new [Link]();
setDefaultCloseOperation([Link].EXIT_ON_CLOSE);
setFont(new [Link]("Arial", 1, 12));
[Link](new [Link]("Arial", 1, 12));
[Link]("CHOOSE THE DESIRED OPTION");
[Link]("ACCOUNT DETAIL");
[Link]("AMOUNT DEPOSIT");
[Link]("HOME");
[Link] layout = new [Link](getContentPane());
getContentPane().setLayout(layout);
private void initComponents() {
label1 = new [Link]();
label2 = new [Link]();
textField1 = new [Link]();
button1 = new [Link]();
button2 = new [Link]();
label3 = new [Link]();
label4 = new [Link]();
label5 = new [Link]();
label6 = new [Link]();
label7 = new [Link]();
label8 = new [Link]();
label9 = new [Link]();
label10 = new [Link]();
label11 = new [Link]();
label12 = new [Link]();
label13 = new [Link]();

65
 label14 = new [Link]();
button3 = new [Link]();
setDefaultCloseOperation([Link].EXIT_ON_CLOSE);
[Link](new [Link]("Arial", 1, 12));
[Link]("\nACCOUNT DETAIL");
[Link]("Enter pin no:");
[Link]("1234");
[Link]("submit");
[Link]("retry");
[Link]("name:");
[Link]("account no:");
[Link]("address:");
[Link]("ph no:");

[Link]("Last transaction type:");

[Link]("current balance:");

[Link]("maha");

[Link]("10001");

[Link]("linemedu");

[Link]("9999999990");

[Link]("cash transfer");

[Link]("215080");

[Link]("EXIT");

[Link] layout = new [Link](getContentPane());

getContentPane().setLayout(layout);
[Link](
[Link]([Link])
.addGroup([Link](.addGroup([Link](javax.s
[Link], false)
.addGroup([Link]()
.addGap(126, 126, 126)

66
public class NewJFrame10 extends [Link]
{
/** Creates new form NewJFrame10 */
public NewJFrame10() {
initComponents();
} .
}private void initComponents() {
label1 = new [Link]();
label2 = new [Link]();
textField1 = new [Link]();
button1 = new [Link]();
textField2 = new [Link]();
button2 = new [Link]();
setDefaultCloseOperation([Link].EXIT_ON_CLOSE);
[Link](new [Link]("Arial", 1, 12));
[Link]("AMOUNT DEPOSIT");
[Link]("Enter amount:");
[Link]("20000");
[Link]("submit");
[Link]("! sucess");
[Link]("ok");
* @param args the command line arguments
*/
public static void main(String args[]) {
[Link](new Runnable() {
public void run() {
new NewJFrame10().setVisible(true);
}
}

67
 APPENDIX 2
SAMPLE SCREEN SHOTS

Main Screen

Figure A 1.1 Main Screen

68
Authentication window

Figure A 1.2 Authentication window

Transaction window

69
 Figure A 1.3 Transaction window

Cash withdraw

70
 Figure A 1.4 Cash withdraw

Cash deposit Window

71
 Figure A 1.5 Cash deposit Window

Successful Transaction message window

72
 Figure A 1.5 Successful Transaction message window

Message window

73
 Figure A 1.6 Message window

Mini statement window

74
 Figure A 1.7 Mini statement window
Officer options window

75
 Figure A 1.8 Officer options window

Officer Account detail window

76
 Figure A 1.9 Officer Account detail window

Officer Account deposit window

77
Figure A 1.10 Officer Account deposit window

78