You are on page 1of 24

1.

) INTRODUCTION
This project is about the Banking System. The project has the complete information regarding the account details (including create, withdrawal, deposit, summary etc). It also contains the information about the different customers opening their account in the bank. This project also helps to keep the information about all the details of the various customers who have opened their account. This project is stand alone and the various centers of banking can implement connected through the network (only WAN) and only authenticated Person of the Bank can check the details of the account holder, he can also create saving, fix, current account of the customer. Due to centralized database only authenticated Person of The Bank can handle the application. a) Purpose: The purpose of this document is to present a detailed description of the Online Banking System. It will explain the purpose and features of the system, the interfaces of the system, what the system will do, the constraints under which it must operate and how the system will react to external stimuli. This document is intended for both the stakeholders and the developers of the system and will be liable for the approval or disapproval of the project by the community of the Bank.

b) Document Conventions This project is about the Banking System. The project has the complete information regarding the account details (including create, withdrawal, deposit, summary etc). It also contains the information about the different customers opening their account in the bank. This project also helps to keep the information about all the details of the various customers who have opened their account. This project is stand alone and the various centers of banking can implement connected through the network (only WAN) and only authenticated Person of the Bank can check the details of the account holder, he can also create saving, fix, current account of the customer. Due to centralized database only authenticated Person of The Bank can handle the application. c) Intended Audience The objective is to prepare a software or application, which could maintain data & provide a user friendly interface for retrieving customer related details just in few seconds, with 100% accuracy. Software is completely computerized, so it is not time consuming process. No paper work required & can be implemented further. The application should also facilitate the addition of new Customer A/c, deletion of A/c& modification of existing customer A/C. To Search for every individual accounts for a particular customer, show all transaction & any account should be opened with minimum Rest. 500 etc.

d) Additional Information Cost saving benefits This project reduces the administrative and operational cost. Because of the reduction in the use of paper, the cost also reduces. Improve-service-level benefits Proposed system improves the systems performance because the current system is based on manual processing while the proposed system is based on computer processing. Improve-information benefits It provides better information in the stipulated space and time for decision-making. Time saving benefits It saves lots of time and provides the same result in a far lesser period of time

e) Contact InfoDhawal Bhatia -9827983820 Gaurav Rawal-9425110019 Gaurav Dubey-9713991294 Ashutosh Bharadwaj-9893470943

f) ReferencesJava Complete Reference Author(s): Herbert Schildt Publisher: TMH Publications Core Java2 volume I &II Author(s): Cay S Horstmann, Gary Cornel Publisher: Pearson Publications JAVA 2 Swing Author(s): Deitel & Deitel Publisher: prentice Hall Google search engine

2.) OVERALL DESCRIPTIONS


a) Product Perspective The product is banking software similar in functionality to the software run in most banks. The bank software will allow for two different methods of operation. The first method of operation will be through an ATM terminal. This operation is performed by the user. The user will be allowed to deposit funds, withdraw funds, check

balance, and transfer funds. It will all be done through a simple, easy to use graphic user interface. It will implement the standard buttons found on a standard ATM machine. The second part of the banking software is the bank operations software. It will run through a PC and will be manipulated by a bank teller or manager via keyboard and mouse. This will allow for a different type of GUI. Instead of a series of consecutive screens operated by ATM buttons this software will all be organized around a menu bar. All functions will be accessible at any time through a menu bar at the top of the screen. These functions include: authenticating, depositing funds, withdrawing funds, checking balance, requesting account creation, authorizing account creation, requesting loans, authorizing loans, and generating reports. The users will be classified into two different categories: Bank managers and bank officers. This classification determines what access privileges the user has.

b) Product Functions First draw the overall use-case diagram and give a brief description then describe the major use-case Deposit Money- Its primary function is to allow the user to deposit money into an account. Actors 1. Bank Customer 2. Banking System Main Flow 1. The user is presented with the main menu screen.

2. The user will request deposit by clicking on the deposit button of the main menu. 3. The user is presented with a screen that prompts the user for the account to where the money will be deposited and the amount of money to deposit. 4. The user enters the correct information and then clicks on the confirm button. 5. The banking system sets update Balance on the users account. 6. The user has been authenticated properly. For a withdrawal transaction, the system shall determine that sufficient funds exist in the requested account, that the maximum daily limit has not be exceeded c) User Characteristics The typical bank customer will be a person, from the age of 10 and up. There will more than likely be a fairly equal distribution of males and females. The typical customer will probably use the bank account a couple of times a week. The typical customer might not know anything about computers, so their system needs to be very simple and easy to use. The typically customer will probably be a busy person; therefore, they will need to do their transactions as quickly and efficiently as possible. The other user is a bank employee. The bank employee will be a different type of user. The bank employee is a fairly educated user, who is willing to sacrifice simplicity for functionality. They will use the software daily, for every transaction. This could quite possibly be 30-60 transactions per hour per employee. Due to this frequency of usage stability and speed of this software is incredibly important.

d) Operating Environment The system will primarily be developed and tested on Microsoft Windows based Operating Systems. But our goal is to make it a platform independent solution.

e) User environment User should know English and use of Computer at basic level.

f) Design and Implementation Constraints -Login and password is used for identification of customers account and there is no facility for non users to login. -This system works only on a single server. -GUI is only in English -Limited to HTTP/HTTPS protocols

g) Assumptions and Dependencies

-The details of customers such as username, password, account type and their corresponding authority details should be manually entered by the administrator before using this system. -Every user should be comfortable of working with computer and net browsing. -He should be aware of the banking system. -He must have basic knowledge of English too.

3.) External Interface Requirement a) User Interface Under the user interface of the toolbar there are two options: new user and manage user. When new user is chosen the bank manager can assign a username and password to the user. The manager also inputs the real and the role of the user. Once this information is entered the request is sent to the server to create the user. When a manger selects the Manage user option they are shown the manage user screen. This requires the employees username to be entered. This username can be discovered through a find username button. From this screen the manager has the option to change bank roles, change passwords, or delete user. Once the bank manager makes one of these selections the request is fulfilled by the server.

b) Hardware Required

Processor : Pentium 4 or Later Memory : 128 MB RAM

Hard disk : 40 GB

c) Software Required Operating System : Windows XP Web Browser : Internet Explorer 6 or Firefox 2 (Browser should be JavaScript and Flash enabled) Front End : JAVA 2 RDBMS : MS ACCESS

d) Communication Interface -Client on Internet will be using HTTP/HTTPS protocol. -Client on Intranet will be using TCP/IP protocol. -A Web Browser such as IE 6.0 or equivalent

4.) SYSTEM FEATURES


a) Description

The following sections describe the general factors that affect the product and its requirements. Customer must have a valid User Id and password to login to the system. After the valid user logs in he is shown the list of accounts he has with the bank. On selecting the desired account he is taken to a page which shows the present balance in that particular account number, user can request details of the last n number of transactions he has performed. User can make a funds transfer to another account in the same bank. User is provided with a transaction password which is different from the login password. User can transfer funds from his account to any other account with this bank. If the transaction is successful a notification should appear to the customer, in case it is unsuccessful, a proper message should be given to the customer as to why it failed. User can request for cheque book/change of address/stop payment of cheques. User can view his monthly as well as annual statements. He can also take print out of the same. Appropriate help to be provided as and when requested by the user.

b) Action/Result i) Administrator: He is the super user responsible for managing clients of the system, taking system backup, generating reports, maintaining organization details.

-Manage Clients: The Administrator assigns new users when a new client joins the online bank. Also he can delete an account when any of the clients leave the bank organization. -Maintain Organization Details: The Administrator maintains entire details of the organization that includes details of the clients, entrepreneur details etc. -Take System Backup: The Administrator Backup the database in order to prevent loss of data on system crashes. He can backup entire database or a particular section.. -Generate Reports: : Responsible for checking the logs of different system users for auditing and maintaining the integrity of the system Manage Clients -Name Of Use-Case: Manage clients. =Description: The Administrator assigns new users when a new client joins the online bank. Also he can delete an account when any of the clients leave the bank organization. =Preconditions: -Administrator is already logged in.

c) Functional Requirements:

Following are the services which this system will provide. These are the facilities and functions required by the customer. -Online balance check -Online shopping opportunity -Online data entry by the staff -Updating the data -Balance transfer -Check book Allotment

5.) NON-FUNCTIONAL REQUIREMENT


a) Performance Requirements System can withstand even though many no. of customers request the desired service. Access is given to only valid users of bank who requires the services such as balance enquiry, update profile, funds transfer, mini statements, and request for stop payments and for cheque book b) Safety Requirements The project must be safe and secure because cutomer will directly contact their account through the internet.Software will have to identify the valid customer according to his/her bank details and password. So it is a difficult task to prevent the system by major disasters preventing the unauthorized access to the system.

c) Security Requirements

Sensitive data is protected from unwanted access by users appropriate technology and implementing strict user-access criteria. Facility of unique user number and Password in such a way that unauthorized user cannot log in. Operational rights for each user/terminal can be defined. Thus, a user can have access to specific terminals and specific options only.

d) Software Quality Attribute Reliability The system shall save the data stored in the user data structures once every five minutes. The system shall save the data of an active user whenever that user has just completed a deposit transaction. The system shall save the data of an active user whenever that user has justcompleted a withdraw transaction. The system shall save the data of an active user whenever that user has justcompleted a transfer funds transaction. The system shall save the data of an active user whenever a new user iscreated.

The system shall save the data of an active user whenever a new account iscreated. The system shall save the data of an active user whenever a user passwordis changed. The system shall not save on a check balance transaction. The system shall reboot itself automatically if there is a power failure andrestore all saved data to the user accounts. e) User Documentation Operation systems are quickly taken for granted. Every system requires periodic evaluation after implementation. Unlike system testing which determines where the system fails, the user documentation review determines how well the system continues to meet performance specification. It also provides information as to determine whether major redesign is necessary. The user documentation review provides the evaluation of a system in terms of the extent to which the system accomplishes stated objectives and actual project costs exceed initial estimates. The initiating study begins with the review team, which gathers and reviews request for evaluation. It also files discrepancies notices after the system has been accepted. Unexpected changes in the system that affects the user or

system performance is a primary factor that prompts system review. Once a request is filed, the user is asked how well the system is functioning to specification. Suggestion is sought and this marks the beginning of the operation documentation review. The review team prepares formal review plan around the objective of review the type of object to be carried out and the time scheduled. f) Testing VERIFICATION The verification stands for are we building product right, means at the time of development it is continuous cycle to evaluate the functionality being implemented is as per requirement analysis correctly. IN our project there verification of functionalities lies mainly at presentation tier in JSP pages testing team tried to know is really we have correctly implemented the database transactions, interfaces and appropriate workspace along with access restricted functions. VALIDATION

Validation means are we building right product? It is a fundamental question while implementing a business solution there in a corporate where finally product will be deployed not are all computer engineers

as end users. Some all the functionality which the end user need we have to provide and before deployment validate the presence of customer needs. In validation phase team talked to members of corporate management showing the design models and corresponding functionality and sometimes we were glad to have advises from end users to change the interfaces, look and feel, not very deeply they said us to change code entirely but corporate was still enjoying with same code under newer captions. SRS contain testing specifications

TESTING STRATEGIES TESTING UNIT TESTING INTEGRATION TESTING TEST CASE DESIGN WHITE BOX TEST CASES WHITE/BLACK BOX TEST CASES/TOP-DOWN/BOTTOM UP BLACK BOX TEST CASES BLACK BOX TEST CASES COMBINED TESTING CASES

SYSTEM TESTING VALIDATION TESTING HIGH LEVEL

UNIT TESTING: In unit we have prepared test cases in white box testing criteria and taken each module separately to know the errors in individual functionality of modules. Basically we found some errors initially for example. -A user typed the wrong data type in field as directed in a form in marketing module, which was not recognized by software causing unwanted shutdown. Probably it was a test case. -A user tried print command from payment form but by default it was set to two copies each time. -User tried to open JSP but it was control flow mistake done which was unable to deliver login JSP. So in Unit testing following test areas are possible: Individual modules one by one, arithmetic precedence, incorrect initializations, precision inaccuracy, comparison of different data types. INTEGRATION TESTING

The integration testing is done to uncover errors associated with interfacing, objective is to take unit tested components and build a program structure that had been detected by design.

6.) OTHER REQUIREMENT


TERMINOLOGY -HTML: Hypertext Markup Language is a markup language used to design static web pages. -EJB: Enterprise Java Beans. -J2EE: Java 2 Enterprise Edition is a programming platform part of the Java Platform for developing and running distributed multitier architecture Java applications, based largely on modular software components running on an application server. -DB2: DB2 Database is the database management system that delivers a flexible and cost effective database platform to build robust on demand business applications. -WAS: Web sphere application server is an application server that runs business applications and supports the J2EE and web services standards. -WSAD: Web sphere studio application developer is a toolkit which is designed for the creation of more complex projects, providing fully dynamic web application utilizing EJBs. This consist of EJB tools , CMP ,data mapping tools & a universal test client that is designed to aid testing of EJB s. -HTTP: Hypertext Transfer Protocol is a transaction oriented client/server protocol between web browser & a Web Server. -HTTPS: Secure Hypertext Transfer Protocol is a HTTP over SSL

(secure socket layer) -TCP/IP: Transmission Control Protocol/Internet Protocol, the suite of communication protocols used to connect hosts on the Internet. TCP/IP uses several protocols, the two main ones being TCP and IP.

password
Customer id Admin id password

address

Phone no

manages

Customer

administrator

manages

Works in

Org_name

ISA

organization

Accounts_types Cheque_req
manage

Balance_enq

updations

Funds_transfer

Mini stmts

Generate the accounts

Grant request Update profile

Perform transacti ons Generate trans_list

Checks the available amount

Internal_admin Admin id password

displays

Data flow diagram (0-level):


REQUEST

USER

BANKING MANAGEMET SYSTEM

RESPONSE

Display Account Details Module DFD

Administrator /authenticated user

Enter id and password

Invalid login

Verification Checks

Valid login

Display Module

Process Display Page

Database