this is atm database system

1. ATM
DATABASE
SYSTEM

2.  INTRODUCTION
 Introduction to the project
 Objectives of the project
 Scope of the project
 Hardware and Software Requirements
 Technology used
 DESIGN
 Design
 System Design
 Architecture Design
 Detailed Design
 Diagrams
 SCREENSHOTS
 CONCLUSION
 Conclusion
 Perspective Users
 Limitations
CONTENTS

3. INTRODUCTION
 An automated teller machine (ATM) is a computerized telecommunications device
that provides the customers of a financial institution with access to financial
transactions in a public space without the need for a human clerk or bank teller. On
most modern ATMs, the customer is identified by inserting a plastic ATM card with
a magnetic stripe or a plastic smartcard with a chip, that contains a unique card
number and some security information, such as an expiration date or CVC(CVV).
Security is provided by the customer entering a personal identification
number(PIN).
 Using an ATM, customers can access their bank accounts in order to make cash
withdrawals (or credit card cash advances) and check their account balances as
well as purchasing mobile cell phone prepaid credit.
 ATMs are known by various other names including automated banking machine,
money machine, bank machine, cash machine, hole-in-the-wall, cashpoint,
Bancomat (in various countries in Europe and Russia), Multibanco and Any Time
Money eased ATM usage is also helped by the fact that customers have now the
flexibility of using ATMs of other banks, as most of the banks are part of major
interbank networks like National Financial Switch (NFS), Milr, BANGS, Cashtree and
Cashnet. The interbank networks have brought together ATMs of several banks so
that consumers would gain access to any of the participating banks' ATMs.

4.  Before making this application, we assumed that a fictitious bank which
had recently started its operations found it very difficult to handle their
customers.
 It was due to their great customer service and efficient handling of daily
operations that they customer base started growing, and in a day, they
started to handle lot of customer requests.
 When this happened, the bank authorities realized that the customer had
lot of different queries like Account opening, Account information,
Deposit, Withdrawal etc.
 Slowly & slowly the count of such customers started to grow very rapidly
and the bank employees had to devote their maximum time in handling
such customers.
 This resulted in large response times of the bank employees who found
themselves unable to give adequate time to other important customers
like NRIs.
1. Slowly, the bank started loosing its important or gold customers due to
poor response times by the bank employees and they even started
loosing those customers whose requests could not be fulfilled.
 After this, the bank decided to install a centralized system that can help
its customers fulfill their queries efficiently and at the same time help the
bank undertake important tasks securely which can improve the response
times and can ease up the tasks of the employees who were already
overburdened with handling all the processes manually till date.
OBJECTIVE

5.  Keeping the problem in mind, we have developed a solution which would
help the bank, achieve its overall objectives. The application can be securely
accessed by bank employees & the administrator who has got system-level
rights to access confidential information of the bank employees in the
database.
 The administrator can perform the following tasks:
 Account Opening: In this module, all the relevant personal information details
like Name, Address, Contact, PAN etc. of the prospective customer who wants
to open an account with the bank are entered.
 Modification: In this function, an administrator can modify the details of a
customer like Name, Address etc. Before the details are modified, the
account-id of the customer is inputted which is cross-checked in the database
for correctness.
 Kiosk status: In this application, we have assumed 3 kiosk / ATM machine
locations namely Vikas Puri, Dwarka & South Ex- II. Additionally, we have
assumed that all of these kiosks will have Rs. 25 lakh each in a day to serve
customer’s withdrawal requests efficiently.
 Lock/Unlock Accounts: Through this functionality, administrator would be able
to lock or unlock a customer’s account. We have assumed that one condition
in which the customer’s account would be locked will be if he/she wrongly
inputs the pin no. for 3 instances while logging in. This is a special security
feature that has been implemented to encourage security.
SCOPE OF THE PROJECT

6.  Close Accounts: An administrator can close a customer’s account upon bank’s
request only if the customer has not done any transaction for a long period,
say 1 year. It is assumed that when a customer does not make any transaction
for a long period, his account becomes dormant and reminder letters are
being given to that customer by the bank regarding conversion of his/her
account to dormant. If the customer still does not respond to the reminders,
his/her id finally closed.
 Deposit: We have assumed that the customers can make deposit requests
through cheques wherein they can deposit their cheques through inputting all
the necessary & important details like cheque no, cheque date & cheque
amount in the application. The application will not accept post-dated cheques
and the customer will be duly notified about same.
 Withdrawal: Under this function, the customer can withdraw amount from his
account. His present balance is being shown before the withdrawal. After the
withdrawal, revised balance is being shown. It is assumed that in any day, a
customer is not allowed to withdraw more that Rs. 50,000/-.
 Account Status: Through this feature, the customer can have complete details
regarding his present account balance and the last deposit & withdrawal
transaction being done with all the details.

7. HARDWARE & SOFTWARE
REQUIREMENTS
Hardware:
Intel Pentium D Processor with 3.00 GHz CPU
clock speed
01 GB of RAM
80 GB of Hard Disk space
Software:
Microsoft Windows XP Professional (Service pack 2)
Java 6 Update 12 (JDK1.6)

8. • FRONT END :-
Java:
Java is a general-purpose, Object Oriented programming language. Its syntax is very much
similar to C & C++, but it omits features that make C & C++ complex, confusing and
insecure. Java was initially developed to address the problems of built in software for
small-distributed systems to embed in consumer devices.
• Back End:-
Microsoft SQL Server :-
Microsoft SQL Server is a relational database management system(RDBMS) produced
by Microsoft. Its primary query languages are MS-SQL and T-SQL. Protocol layer
implements the external interface to SQL Server. All operations that can be invoked on
SQL Server are communicated to it via a Microsoft-defined format, called Tabular DatA
Stream (TDS).
TECHNOLOGY USED

9.  We performed the analysis in 02 parts i.e. Feasibility Analysis & Requirements
Analysis.
 Feasibility Analysis:
 We studied the whole system & its objectives. Calculated the total time & resources
incurred on every function being done manually.
 Bifurcated the complete system into a list of functions & the users who operate on
them.
 Further subdivided all the functions into a list or source of requirements/inputs &
clearly defined the output/expectation from each function.
 The interaction, communication & dependency of all the functions between each
other were carefully analyzed in terms of sequence & information.
System Design

10.  The source & flow of the information was determined & how would it be processed &
used was considered.
 Finally, we visualized the complete system with automated functions & compared the
total time & resources being incurred to check the feasibility & see whether it is fulfilling
all the necessary objectives.
 Requirement Analysis:
 This was a subset of feasibility analysis in which we defined a set of objectives for the
complete system after thoroughly analyzing it.
 All the objectives were further subdivided into a set of function(s).
 The input(s) required by each function & the expected output(s)/behavior was/were
clearly defined.
 The source of information/input to every function was determined & its corresponding
processing, usage & storage were also taken into account.
 After this the interdependency & communication was finalized.

11.  Under architectural design, after defining the whole system into a set of objectives &
further subdividing them into functions, we defined the basic dependency &
communication between them.
 This means that all the prime functions, their required inputs, expected
output/behavior & interdependency between other functions were clearly defined.
The corresponding interfaces for the user for each function were designed to ensure
user-friendliness.
 We actually addressed the system-level problems here and made a conscious effort
to build a robust design which can result in an effective communication within itself
and with the system in terms of raw data or processed information.
• All the primary database design for data storage was also done in this phase.
Architectural Design

12. Model Diagram

13.  In this phase, we further subdivided every function into a set of modules & defined
required inputs & expected behavior for each of them. All the minute correlations,
interdependencies, communication between the modules were clearly defined. The
source, usage & processing of data for every module was carefully done. The database
design was also normalized at this stage to ensure that the data is efficiently stored &
retrieved.
 Detailed design helped us to exactly concretize every problem into inputs & outputs and
visualize them in terms of their communication with each other. We focused on
interdependency & interoperability between the broken modules here.
 It was this design phase where the factors like user-friendliness ease of use, scalability and
self-explanation of interfaces & outputs were actually realized. For all the modules, the
placement of controls, passing of information, communication of different interfaces, user
messages, data transfer to databases was defined.
Detailed Design

14. DFD DIAGRAMS
 A data-flow diagram (DFD) is a graphical representation of the "flow" of data
through a information system. DFDs can also be used for the visualization of
data processing
 On a DFD, data items flow from an external data source or an internal data
store to an internal data store or an external data sink, via an internal process.
 shown

15. Level-0 MAIN

16. • In this diagram, overall control is with administrator when we login as an administrator.
An administrator can create a new account by providing a user ID and password, where a
new customer and his all the details are acting as an input to the machine. Kiosk status
fills the ATM machine which the desired amount that should present in the machine.
Administrator can close a user account if he/she wants to do that.
• Now user can make transaction from the ATM machine in the form of withdraw and
deposit and check his account.

17. Level-1 Administrator

18.  Logging in as administrator, an administrator can add a new customer in which he
enters his personal details he can create current or saving account. User can
modify his details. He can temporary lock his account.
 Administrator can check the kiosk status of the accounts of the customer and if
the balance in the machine is not enough than the administrator can fill up the
machine with the desired amount now if and user wants to closes account than he
can requested that administrator to do that and his account permanently.

19. Level-2 User DFD

20. • In this DFD, user can make transaction in the form of withdrawal and deposit.
This two boxes acts as an input that the user enters. A user can add money to
his previous account and can withdraw money from his existing account. He
can then check his account status which acts as output to the user.

21. Use Case diagram

22. interaction diagram

23. Activity diagram

24. SCREENSHOTS
The Main Page

25. When logged in as the administrator

26. Logging in as the user

27. CONCLUSION
• The project development has been an enriching experience. Its technological
components challenged us to use most current tools and techniques of Java.
Developing a live system is a work of high responsibility and is not as simple
as it finally appears to client who is going to use it. It not only requires in
depth study of the system already used but also understanding of the
problem analysis and design issues.

28. Perspective Users
 It is used by customers in payment of the bills, tax debates, money transfer,
sales of products and recharge of mobile bills.
 Bank employees use ATM to transfer their transaction made at their branch
to the main branch of the Bank.
 It is used in the financial sector regarding the credit card information.
 It is used in the different parts of the world to carry out the work related to
money.
• Providing customers with all the money transactions & debits in a convenient
way.

29.  Researchers who work for an Israeli computer security company say they have
discovered a fundamental weakness in the system that banks use to keep debit card PIN
codes secret while they are transported across bank networks - a flaw that they say
could undermine the entire debit card system Accordingly its limitations include three
types of feasibility:-
• Economic Feasibility: Economic analysis includes the use or rather n some sense misuse
of the ATM machines in foreign countries. it can be misuse in any part of the world. the
money can be used by some unauthorized agency for their brutal purpose. again here
the verification of the PIN no. plays a very important role. ln the financial sector this is
regarded as the PIN cracking.
• Technical Feasibility: Technical feasibility includes the proper functioning of atm database
system when it comes to the remembering of the PIN no. Many cardholders walk up to
an ATM and pull out a piece of paper containing four numbers. If you are not sure, make
it a point that you don't keep the PIN and ATM card together in your wallet - If someone
comes up and hits you over the head, they're going to have all your information right
there. But ideally, one should never write down the PIN number - it should be
memorized.
• Social Feasibility: Illiterate People cant handle the functioning of ATM. So to teach them
the use instructions are also provided regarding its transactions & debits, transfer of
money to people at any part of the world
Limitation And Constraints of project

30. QUERIES??