Personal banking system

1
Personal banking system

2
ABSTRACT

• Before the evolution of
  computers, all the details in a banking systems
  used to be maintained manually. This is not
  advisable because maintenance and retrieval of
  information becomes tedious.
• Our project on Personal
  Banking System is a fully computerized one which
  provides an account holder to view his account
  information such as checking balance, recent
  transactions, transfer of funds, etc. User can
  also view his account information on his personal
  computer.

3
ABSTRACT

• In our personal
  banking system we have two types of accounts,
  they are savings and current. only a person
  having savings account can avail this facility.
  A person should register at administrator
  manually to create account number and personal
  details. Once a person has registered with bank
  administrator, he will give a default password to
  an user, Which can be changed later by user. Thus
  user can login in and view his account
  information at their home computers.
• In this way,
  personal banking has emerged to be one of the
  greatest innovations of the modern world.

4
INTRODUCTON

• A customer
  can view his account details depending on the
  requirement and the services provided by the
  bank.
• The personal banking system has mainly two
  modules
• Customer Module
• Administration Module

5
INTRODUCTON

• Customer (i.e., user) is provided with various
  operations like view balance, view transactions,
  transfer of money etc., from his account.
• Administrator can login with username and
  password which is maintained as highly
  confidential. He can add/delete customers as well
  as the other bank related details.

6
PROBLEM ANALYSIS
7
EXISTING SYSTEM

• By using present system, work is done manually.
  So all transactions takes lot of time to
  complete.
• Whenever user wants to make any updations, it is
  difficult and requires more time to get
  particular information from a file.
• If the information is maintained manually the
  process becomes much complicated and difficult
  for understanding and retrieval
• of information.

8
PROPOSED SYSTEM

• By using proposed system , the whole system is
  computerized.
• so, the transactions takes less time.
• Only the registered members will be allowed to
  access the
• information from the system.
• Large amounts of information can be stored and
  can be easily retrieved from database.
• Login/password is required for accessing this
  software.

9
SOFTWARE REQUIREMENTS
SPECIFICATION
10
HARDWARE REQUIREMENTS

• Processor Intel Pentium 4 or equivalent
• RAM Minimum of 256 MB or higher
• HDD 20 GB or higher
• Monitor 15 or 17 color monitor

11
SOFTWARE REQUIREMENTS

• Front-endJ2EE (JSP, Servlets, JDBC, HTML,
  JavaScript)
• Back-end Oracle 9i or higher
• Server Apache Tomcat 5.5
• Operating system Microsoft Windows 2000 or XP
• Browser Microsoft Internet Explorer or any
  other

12
FEASIBILITY STUDY

• The objective of this system is to determine
  quickly and at a minimum expense to establish how
  to solve a problem
• The feasibility can be tested in two ways

1. Technical feasibility
2. Operational feasibility

13
FEASIBILITY STUDY

• Hardware selection
• This system works on a PC which act as server as
  well as client with a web browser.
• Software selection
• The system require Microsoft Windows operating
  system for the client as well as server.

14

• The server machine should be installed with web
  browser that supports JSP platform and Oracle 8
  data base manager for back end database
  management.
• The client system should be equipped with
  Internet Explorer 6.

15
DATA DICTIONARIES
16
DATABASE TABLES

• ACCOUNT
• FIELD NAME KEY TYPE
  DATA TYPE
• ------------------ ---------------
  -----------------
• ACC_NO PRIMARY KEY
  NUMBER(6)
• BALANCE
  NUMBER(10,2)
• TYPENO FOREIGN KEY
  NUMBER(3)

17
DATABASE TABLES

• ATYPE
• FIELD NAME KEY TYPE
  DATA TYPE
• ------------------ ---------------
  -----------------
• TYPENO PRIMARY KEY
  NUMBER(3)
• TYPE
  VARCHAR2(20)

18
DATABASE TABLES

• ACCDATA
• FIELD NAME KEY TYPE
  DATA TYPE
• ------------------ ---------------
  -----------------
• ACC_NO FOREIGN KEY
  NUMBER(6)
• BRANCH
  VARCHAR2(30)
• CITY
  VARCHAR2(25)

19
DATABASE TABLES

• CUSTOMER
• FIELD NAME KEY TYPE
  DATA TYPE
• ----------------- ---------------
  -----------------
• USID PRIMARY KEY
  NUMBER(6)
• ACC_NO FOREIGN KEY
  NUMBER(6)
• UNAME
  VARCHAR2(40)
• ADDRESS
  VARCHAR2(50)
• EMAILID
  VARCHAR2(40)
• BRANCH
  VARCHAR2(30)
• CITY
  VARCHAR2(30)

20
DATABASE TABLES

• BRANCH
• FIELD NAME KEY TYPE
  DATA TYPE
• ----------------- ---------------
  -----------------
• BRANCH_NAME PRIMARY KEY
  VARCHAR2(30)
• BRANCH_CITY
  VARCHAR2(25)
• ASSETS
  NUMBER(10,2)

21
DATABASE TABLES

• ULOGIN
• FIELD NAME KEY TYPE
  DATA TYPE
• ----------------- ---------------
  -----------------
• USID FOREIGN KEY
  NUMBER(6)
• UNAME
  VARCHAR2(30)
• PASSWORD
  VARCHAR2(15)

22
DATABASE TABLES

• TRANSACTION
• FIELD NAME KEY TYPE
  DATA TYPE
• ----------------- ---------------
  -----------------
• TRANS_ID PRIMARY KEY
  NUMBER(6)
• ACC_NO FOREIGN KEY
  NUMBER(6)
• ACCESS_DATE
  DATE
• TYPE_TRANS
  VARCHAR2(45)
• DEBIT
  NUMBER(10,2)
• CREDIT
  NUMBER(10,2)

23
DATABASE TABLES

• TRANSFER
• FIELD NAME KEY TYPE
  DATA TYPE
• ----------------- ---------------
  ----------FACCNO
  NUMBER(6)
• DACCNO
  NUMBER(6)
• DAMOUNT
  NUMBER(8,2)

24
DATABASE TABLES

• ZIP
• FIELD NAME KEY TYPE
  DATA TYPE
• ----------------- ---------------
  -------------------
• BRANCH
  VARCHAR2(30)
• CITY
  VARCHAR2(30)
• ZIPCODE PRIMARY KEY
  NUMBER(7)
• STATE
  VARCHAR2(30)

25
SCREEN SHOTS
26
(No Transcript)
27
(No Transcript)
28
(No Transcript)
29
(No Transcript)
30
(No Transcript)
31
(No Transcript)
32
(No Transcript)
33
(No Transcript)
34
(No Transcript)
35
(No Transcript)
36
(No Transcript)
37
(No Transcript)
38
(No Transcript)
39
(No Transcript)
40
(No Transcript)
41
(No Transcript)
42
(No Transcript)
43
(No Transcript)
44
(No Transcript)
45
(No Transcript)
46
(No Transcript)
47
(No Transcript)
48
(No Transcript)
49
(No Transcript)
50
(No Transcript)
51
(No Transcript)
52
(No Transcript)
53
(No Transcript)
54
(No Transcript)
55
(No Transcript)
56
(No Transcript)
57
(No Transcript)
58
(No Transcript)
59
(No Transcript)
60
(No Transcript)
61
(No Transcript)
62
TESTING

• Testing is process of executing program with the
  intent of finding an error
• Testing is the phase where errors remaining from
  the earlier phase are also detected.
• In this the program to be tested is executed with
  a set of test cases and the output of the program
  for the test case is evaluated to determine
  whether the program is performing as it is
  expected to do.

63

• The basic levels of testing are

1. Unit testing
2. Integration testing
3. System and Acceptance testing

64
Unit testing

• Unit testing focuses on the verification of
  smallest unit of software design module
• It is essential for the code produced during the
  coding phase
• Its goal is to test the internal logic of the
  module.

65
Integration testing

• In this many tested modules are combined into sub
  systems and they are tested
• The goal is to see whether the modules can be
  integrated properly.
• System testing
• Here the entire software system is tested for
  various types failures

66
CONCLUSION

• The entire implemented system mainly demonstrates
  the concept of a personal banking system.
• The developed system perfectly met all the
  objectives conceived at the design phase of the
  system.
• This project helps the user from avoiding the
  manual stress in maintaining the records.
• No system is always perfect or complete and there
  is scope for further development.