ONLINE BANKING SYSTEM

Scope
 This Product will automate of banking transaction process.
 The system provides easy solution to banks.
 Every bank will prefer the online banking system instead of the traditional banking system
as it contains many useful features and fastest methods for the transactions

Problem Statement:
The Traditional way of maintaining details of a user in a bank was to enter the details and
record them. Every time the user need to perform some transactions he has to go to bank and
perform the necessary actions, which may not be so feasible all the time. It may be a hard-
hitting task for the users and the bankers too. The project gives real life understanding of
Internet banking and activities performed by various roles in the supply chain.

Vision:
 Product perspective:
The client will alsohave client interface in which he can interact with the banking system. It is a
web based interface which will be the web page of the banking application.

 User Characteristics
There are four different ways for a user to interact with the system:
Viewers:
Many unknown persons or un-authenticated persons visit the Bank official site via internet. They
collect the information and search what are the schemes are available in the bank web page.
Those viewers or visitors became the customer of the bank.
New User:
Who all visited that Bank webpage or heard about the bank those persons getting ready to start
account in bank. They register the bank application form, submit and start account in the nearest
bank.
Existing User:
The Existing user is the most typical user of the Online Banking system. Each Users have their
own account and registered or authorized login access. The Existing user can login in online to
their account perform the operation of deposit, withdrawn, transfer, balance queries and
transactions. All the operation of the banking do in online it helpful for user because save time
and efficient process.
Administrator:
Admin is master user of the system because they are main role of the system. Admin grant and
maintain the database of the existing user and grant the permissions to users. It overrules all
other users
 Assumptions and Dependencies:
1)The details of customers such as username, password, account type and their corresponding
authority details should be manually entered by administrator before using the system.
2)Every user should be comfortable of working with computer and net browsing.
3)He should be aware of banking system.
4)He must have basic knowledge of English too.

 General Constraints:
1) The information of all the users must be stored in a database that is accessible by the Online
Banking System.
2) The Online Banking System is connected to the computer and is running all 24hours a day.
3) The users access the Online Banking System from any computer that has Internet browsing
capabilities and an Internet connection.
4) The users must have their correct usernames and passwords to enter into the Online Banking
System.

 Features :
This software will have following functionalities
1) Online balance check and transaction information:
Customer will be able to check his balance online while sitting at home by accessing the database
of the bank using his/her username and pin-code allotted him by the bank.
2) Balance transfer:
This system will provide a path to the customer of the bank to transfer his balance to other account
in easy steps. A small transfer fee will be applicable for this transaction.
3) Check book Allotment:
If the customer’s checks have been completed, a new check book will be allotted to him.

Cost Estimation:
One of the factors, which affect the development of a new system, is the cost it would require.: -
 The costs conduct a full system investigation.
 The cost of the hardware and software.

Schedule:
This product must be completed in 7 months.

Methodology:
WaterFall Model The waterfall model is a sequential design process, often used in
software development processes, in which progress is seen as flowing steadily
downwards (like a waterfall) through the phases of Analysis, Requirement Specification,
Design, Implementation, Testing and Integration and Operation and Maintenance. If in
the beginning of the project failures are detected, it takes less effort (and therefore time
and money) for this error. In the waterfall model phases to be properly sealed first before
 proceeding to the next stage. It is believed that the phases are correct before proceeding
to the next phase.
Why to use this model?
In our Project, all the requirements are clear and well known and the project is large.
All the activities in our project are carried out in above mentioned phases of waterfall
model.

Functional Requirements
. Various functional modules that can be implemented by the product will be –
1. Login
2. Feedback
3. Get balance information
4. Transfer Money

Non Functional Requirements

 Security
All users of the system shall not be able to perform actions or request actions from theBanking system,
which will cause harm to any person or damage to the system or itsenvironment.
 Reliability
The system should be highly reliable and it should generate all the updated information in correct
order.

 Availability
Any information about the account should be quickly available from any computer to the
authorized user. The previously visited customer’s data must not be cleared.

 Maintainability
The system should be maintainable in such a manner that if any new requirement occurs then it
should be easily incorporated in an individual module.

 Portability
There are no portability requirements.