BANKING MANAGEMENT SYSTEM

GANDHI INSTITUTE FOR TECHNOLOGICAL ADVANCEMENT BHUBANESWAR,ORISSA

PRESENTED BY STHITI PRAGYAN DEVIDARSHINI 0801287119 IT GUIDED BY- Banchhanidhi Das

1.Introduction 2. Objective of the project 3. Software Requirement Specification 4. Hardware Requirement 5. Project Design a. Tables b. E-R Diagram c. DFD 6. Web page Layout 7. Project Testing 8. Future Scope 9. Conclusion 10. References

Banking management system (window application) has been developed using AWT, Swing, JDBC as font end and My Sql as backend. Using this software a bank can maintain their records easily. So that the overall performance of the bank greatly increase.

A Bank organization needs a system where store all the information regarding its business and manage the data easily by which it can save time, money, and labour. There should be a system where it can store the information about his/her customer, buyer, seller etc and manipulate the data easily. Banking Management System is useful to record customers details along with their request. It also records the buyer details, seller details and renter details. Banking Management System also provides the management reports like properties requested by the customers, income, expenditure, profit or loss of the company. The administrative user can create new users and change their passwords. He can add the users information as well as new customers details. He can add information related to buyer, seller, renter, properties availability, income and expenditures etc. The administrator can view the management reports.
Thus the banking management system ensures the smooth operation of bank and stores all informations.

The project is divided into seven modules such as: Homepage: This module represents the total system of banking. Customer: This module represents how the customers are doing transaction with bank. Transaction: This module represents how the transactions are doing everyday. Holidays: These module represents lists of holidays are available within in banking system. Branches: This module represents how many branches are present in orissa. Login : This module represents how a new user enter the banking application and doing there transactions details. Logout: This module represents logout the banking organization.

JDK1.6:This is a software which can be used for compilation & execution of the program. This is also provides a set of predefined classes interfaces, package,& methods. For being used in the java program write the program or save the program.JDK also provides the editor i.e. editor provides facility to save it into a folder of a file system. This can be a text editor(ex : notepad ,any integrated development environment i.e. netbeans) MYSQL: Generally sql provides the data structure table which will hold the information of the project i.e. (Banking management system project)which is used to see in the future. this data will store in the web server , to getting the data through web layout pages and it will go to the structure table , and it will save into the server. It is multi-threaded, multiuser database management system. The program runs as a server providing multi-user access to a number of databases.

IDE: NetBeans 6.0 it is a software where all coding of the banking

management project has been done. It had been help to generate the web layout page i.e. used directly by the customer. Through the database connector it will sent the data in my sql data structure to store the data in the structure table.

Hardware Requirements:Processor: Pentium 1.5 GHz Hard disk capacity: 1 GB RAM: 256 MB

TABLES
Field Type Null

(account)
Links to Comments MIME

Default

user

varchar(50)

Yes

account

varchar(50)

Yes

date

varchar(50)

Yes

obalance

bigint(50) varchar(50)

Yes Yes

atype

mbalance bigint(50)

Yes

issue

varchar(50)

Yes

online

varchar(50)

Yes

branch
Field Type Null Default Links to Comments MIME

name

varchar(50)

Yes

address

varchar(50)

Yes

online

varchar(50)

Yes

manager

varchar(50)

Yes

registration
Field Type Null Default Links to Comments MIME

slno

int(20)

Yes

NULL

userid

varchar(50)

Yes

password

varchar(50)

Yes

email

varchar(50)

Yes

transaction
Field
tmode acno

Type
varchar(50) varchar(50)

Null
Yes Yes

Default

Links to

Comments

MIME

transaction varchar(50)

Yes

trasaction

Varchar(50)

Yes

year month t_date balance

varchar(50) varchar(50) varchar(50) double

Yes Yes Yes Yes

bal_inword varchar(50)

Yes

Er Digram

Data Flow Diagram is a diagrammatic representation of data movement through a system manual or automated - from inputs to outputs through processing. The data flow diagrams help in the analysis of the flow of data through a system and thus help in identifying the system requirements. These are of two types Logical Data Flow Diagrams and Physical Data Flow Diagrams. The Data Flow Diagram (DFD) clarifies system requirements and identifies major transformations that will become programs in system design. It is the starting point of system design that decomposes the requirements specifications down to the lowest level of detail. Logical Data Flow Diagrams: The Logical Data Flow Diagrams represent the transformation of the data from input to output through processing logically and independently of the physical components that may be associated with the system. Physical Data Flow Diagrams: The Physical Dataflow Diagrams show the actual implementation and movement of data between people, departments, and workstations. Each component of a DFD is labeled with a descriptive name. Process names are further numbered that will be used for identification purposes. The number assigned to a specific process does not correspond to the sequence of processes. It is strictly for identification purposes.

USER

BANKING MANAGEME NT

DATABASE

INVALID USER ID AND PWD USER ID,PWD

USER

LOG IN

USER ID PASS WORD

USER ID OR PWD VERIFIED

USER DETAILS DETAILS

USER ID, PWD VERIFIED

VALID USER ID AND PWD

HOME

CUST OMER

ACCO UNT

TRAN SACTI ON

HOME

HOLI DAY

BRAN CHES

LOG OUT

THIRD LEVEL DIAGRAM

CREATE CUSTOM ER

CUSTO MER

EDIT CUSTOME R

USER

VIEW CUSTOME R

CREATE

TRANS ACTIO N

EDIT TRANSA CTION

TRAN SACT ION

TRANSACTION

UPDATE TRANSA CTION

VIEW TRANSA CTION

CREATE HOLIDAY

HOLI DAY HOLI DAY

UPDATE HOLIDAY

EXIT

LOG IN

LOG OUT

Testing is the process of executing the program with the intention of finding out errors. During testing , the program to be tested is executed with a set of test case and the output of the program for the test case is evaluated to determine if the program is performing as it is expected to be. The success of testing in revealing errors in program depends critically on the test case. In software system the use of testing is not titled to the testing phase. The results are used later on during maintenance also. During testing a test suite can be used to see that modification doesnt have any undesirable effect.

The basic levels of testing are: Unit testing Intergration testing System testing Acceptance testing

There are different levels of testing attempts to detect different types of faults. The relation o faults introduced in different phases and the different levels of testing are given below: UNIT TESTING: The level of testing is called unit testing. In this different modules are tested against the specifications produced during design for the module. Unit testing is essential for the verification of the code produced during the testing phase, and hence the goal is set to test the internal logic of the modules.

INTEGRATION TESTING: The next level of testing is often called the integration testing. In this, many tested modules are combined into subsystems, which are then tested. The goal here is to see if the testing interfaces between modules. The testing activity can be considered as testing design, and hence the emphasis on testing modules interactions.

ACCEPTANCE TESTING: It is sometimes performed with realistic data of the client to demonstrate them at the software is working properly. Testing here focuses on the external behavior of the system. The internal logic of the program is not emphasized.

As the system is scalable , more modules can be added as and when required The database that is used in the system can be connected to the any builder information system. It can be browser independent so that the site can be opened in any browser. The system content can be modified to accept new attributes for any criterion.

With the completion of my project I conclude that it has achieved its purpose and it is up to my satisfaction. The whole project provides a base for users to attempt the online BANKING SECTOR sitting at any corner of the world.

Hoping our project will hack the talented fresh mca from the software area..
wish that my project on Banking Management System would be beneficial for the user in this technical era.

WWW. BANK OF INDIA.COM WWW. BANKINGSYSTEM.COM WWW. SEMINAR FOR U.COM WWW.WIKIPEDIA.COM WWW. GOOGLE.COM