Software Engineering Project:-

Bank Management System

Submitted To: Submitted By:-

Mr. Prabhat Verma Saumitra Bajpai (190231061)
Rajat Dixit (190231051)
Shivam Bansal (19021066)
Ayush Gautam (190231020)
Syed Ahmad Aziz (190231071)
 INDEX
S. No. Topic Name Page No.
1. Introduction
1.1 Problem Statement
1.2 Feasibility Study
2. Waterfall Model
3. SRS Document
3.1 Functional Requirements
3.2 Hardware Requirements
3.3 Software Requirements
4 Data Dictionary
4.1 Data Flow Diagram(DFD)
5. Risk Analysis
6. Design and Implementation
6.1 ER Diagram
6.2 Use Case Diagram
7. Testing
7.1 White Box Testing
8. References
 1. INTRODUCTION
Today, banks are looking beyond the transactions to the fullopportunity on how to
manage their customers. Accordingly, they are moving beyond managing clients as simple
contacts to a whole new level of client relationship management, crafting a superior commercial
client experience that gives the bank a competitive advantage and a more loyal, profitable and
committed customers. Internet Banking System refers to systems that enable bank customers to
access accounts and general information on bank products and services through apersonal
computer or other intelligent device. But most of these systems do not focus on how best to
manage and keep their customer’s data more secured. The chances and threats that the internet
symbolizes is no longer news to the present day banking sector. No traditional bank would dare
face investment analysts or new customers without an internet strategy. The main intention
behind the commencement of electronic banking services is to provide the customers with an
alternative that is more responsive and with less expensive options. With options more secured,
customers have more control than ever. Their expectations are how safe and secured their
personal information would be. They also want personal attention and highly customized
products and services.
Customer management is a broad concept that essentially covers the following:
Understanding customer needs, matching customer needs to the best offers in terms of product,
service anddelivery channels, and effectively managing the critical moments during the
customer life cycle. Present experience shows that most of the banks in emerging markets are
not fully managing their customers effectively due to lack of the necessary capabilities to
manage these customer. Better customer management has been shown to directly affect the
profitability of banking institutions. No doubt that this Bank customer’s management system
would provide such bank with much better profits and other benefits. However, financial
products and services, include commercial banks and otherinterested institutions in the financial
services space would bemore than satisfied and also provides a better customersatisfaction. I
was motivated to develop this Bank Customers Management System by various bank specific
experiences I had with some banks, my current existing research on other bank systems, and
interviews with users of such systems. More importantly, this system is not designed to be
prescriptive and does not advocate for a single approach to customer management in the
banking sectors. Rather, to encourage financial services providers in making informed choices
in the challenges, opportunities, and effective practices in providing a safe and secured
customer management across the globe.
 1.1 Problem Statement:
At present most of the banking applications are yet to overcome the rapidly growing
attacks on their customerprivate data. Issues suck fraud operating within a conventional
environment. However current systems are still trying to cope with the existing institutional
structure, which is really meant for usual banking system only and not managing their
customer’s information more effectively. Lack of adequate security measure is making it really
challenging to successfully transform the bank customers’ management systems from where it
is now to where it should be. This challenge still lingers.

1.2 Feasibility Study

The only tangible benefit provided by the proposed system is that the paper work is
reduced to the minimum and hence the reduction in cost incurred on Stationary and its storage.
The system provides many benefits that can't be measured in terms of Money.
For e.g. User's friendliness, more user response being more efficient.

TECHNICAL FEASIBILITY
The proposed system is technically feasible as it can be developed easily with the help of
available technology. The proposed system requires MS – VISUAL Studio 2005 using VB.Net
as a Interface for Programming & back-end as MY SQL Server 2000 for storing/maintaining
database. The database can be easily interconnected using MS-SQL Server 2000.

OPERATIONAL FEASIBILITY
Automation makes our life easy. The proposed system is highly user friendly and is much
easily able to interact with the system. Therefore the users will readilyaccept the system as data
entry and making queries can be easily done.
 2. WATERFLL MODEL
We will use the “WATERFALL MODEL”. This is because the client is a bank that is
trying to install a system that merges operations in all its branches in order to benefit from
centralized decision making. The Waterfall Model of SDLC was selected because all the stages
and activities are all cleary defined. Further, each phase has specific deliverables.
In using this model, the bank will implement the use of the new information systems in
five phases; definition and initiation; planning, execution, monitoring and control, and closure.

Waterfall Model
 Home Page

Login Interfaces
User Interface

User Account
User’s Fund Transfer

Cashier’s Interface
Manager’s Interface
 3. SRS Document

Objectives
The objective of this project is develop a bank customer management system to the best
satisfaction of the customer and for profit maximization to the Banks.
The objectives are:
1. To create a banking system that is easily via internet
2. Reduce the flow of human traffic and long queues at banks
3. Reduce the time wasted in going to banks to update personal details.
4. To develop a bank customer management system with a multi-level security measure
that will restore the customer’s confidence.

Scope
The scope of this project is limited to some activities of the operations unit of a banking
system which include opening of account, deposit of funds, withdrawal of funds, transfer
of funds from one account to another and updating personal details. This application does
not focus on other online services such as; purchasing items online, bill payment loan
application etc.

3.1 Functional Requirements

A functional requirement defines the internal workings of the system: that is, the
calculations, technical details, data manipulation and processing, and other specific
functionality that shows how the use cases are to be satisfied. The functionalities of the system
or modules are mean what the system supposes to do.

For Admin Module

1. This system allows the admin to login with username and password
2. This system allows the admin to add a Bank branch details
3. This system allows the admin to accept or reject a manager/customer
4. This system allows the admin to approve or reject customer transaction request.
 5. This system allows the admin to View Managers & Customers details.

For Manager Module

1. This system allows the manager to login with email and password.
2. This system allows the manager to send notices to branch customers.
3. This system allows the manager to view customer’s transactions.
4. This system allows the manager to view account holder’s information.
5. This system allows the manager to Register New Customer.
6. This system allows the manager to delete any existing customer.

For Customer Module

1. This system allows the customer to login withemail and password.
2. This system allows the customer to view his/her account balance.
3. This system allows the customer to transfermoney from his account to another account.
4. This system allows the customer to check his/her transactions.
5. This system allows the customer to submit any feedback.
6. This system allows the customer to check his/her account’s information.

3.2 Hardware Requirements

Processor: Intel(R) Pentium IV or above
Memory: 8.00GB
RAM: 2 GB or more
Speed: 1.70GHz or faster
3.3 Software Requirements
Operating System: 64-Bit Operating system, Windows 7 or above
Data Base: Microsoft SQL Server -2012
Web Technologies: HTML, CSS, Asp. Net
Client Application: Internet Explorer, Chrome, Mozilla Firefox etc.

4. Data Dictionary

4.1 Data Flow Diagram

0 Level DFD (Context Diagram)

Level-1 DFD
Level 2 Dfd

1. Transaction
2. Modify account
3. LoanApplication

4. Database
6. Searching information
 5. Risk Analysis
Risk analysis is the process of assessing the likelihood of an adverse event occurring
within the corporate, government, or environmental sector. Risk analysis is the study of the
underlying uncertainty of a given course of action and refers to the uncertainty of forecasted
cash flow streams, the variance of portfolio or stock returns, the probability of a project's
success or failure, and possible future economic states.

Risk Identification:

Product Size: The customer’s system should have the capability to fulfil the system’s size.

Business Impact: No risk associated with constraints imposed by management.

KEY TAKEAWAYS
 Risk analysis is the process of assessing the likelihood of an adverse event occurring
within the corporate, government, or environmental sector.
 Risk can be analyzed using several approaches including those that fall under the
categories of quantitative and qualitative.
 Risk analysis is still more of an art than a science.

When to Use Risk Analysis

Risk analysis is useful in many situations:

 When you're planning projects, to help you anticipate and neutralize possible
problems.
 When you're deciding whether or not to move forward with a project.
 When you're improving safety and managing potential risks in the workplace.
 When you're preparing for events such as equipment or technology failure, theft, staff
sickness, or natural disasters.
 When you're planning for changes in your environment, such as new competitors
coming into the market, or changes to government policy.
 RISK CATEGORY PROBABILITY IMPACT

1) Size estimation may be significantly low PS 80% 2

2) Larger number of users then planned PS 60% 3

3) Less reuse than planned PS 30% 2

4) End user resist system BU 40% 3

5) Delivery dead line will be tightened BU 60% 2

6) Funding will be lost CU 30% 1

7) Technology will not meet expectations TE 5% 1

8) Staff turnover will be high ST 50% 2

Limitations of Risk Analysis

Risk is a probabilistic measure and so can never tell you for sure what your precise risk
exposure is at a given time, only what the distribution of possible losses are likely to be if and
when they occur. There are also no standard methods for calculating and analyzing risk, and
even VaR can have several different ways of approaching the task.

Assessing Overall Project Risk:

1. Have top software and customers, managers formally committed to support the
project? YES
2. Are end users enthusiastically committed to the project and the system/product to be
built? YES
3. Are requirements fully understood by the software engineering team and its
customers? YES
4. Have customers been involved fully in the definition of requirements? YES
5. Do end users have realistic expectations? YES
6. Is the project’s scope stable? YES
7. Does the software engineering team have the right mix of skills? YES
8. Are project requirements stable? YES
9. Does the project team have experience with the technology to be implemented? YES
10. Is the number of people on the project team adequate to do a job? YES
11. Do all customer /user constituencies agree on the importance of the project and on
the requirements for the system/product to be built? YES
6. DesignAnd Implementations
To present the relationship between various entities, we use ER diagram:

6.1 ER-Diagram
ER Diagram for Withdrawal
6.2 Use Case Diagram
 7. Testing

7.1 White box testing:

White box testing, sometimes called glass box testing, is a test case design philosophy
that uses the control structure described as a part of component level design to derive test cases.
Using white box testing technique we can derive test cases that:
1. Guarantee that all the independent paths within a module have been exercised at least once.
2. Exercise all logical decisions on their true and false sides.
3. Execute all loops at their boundaries and within their operational bounds and
4. Exercise internal data structures to ensure their validity.

Basis – Path Testing

It is a white-box testing technique which enables the test case designer to derive a logical
complexity measure as a guide for defining a basis set of execution paths. Test cases derived to
exercise the basis set are guaranteed to execute every statement in the program at least once
during testing.

PSEUDOCODE:
1. Read user-id and password
2. If valid user-id
3. { retrieve password from database for entered email-id
4. If entered password = retrieved password
5. Authentication successful
6. Else
7. Invalid password }
8. Else
9. Invalid user-id
Number of regions=1
Predicate nodes (P) =2
Independent paths:
1-2-8-9
1-2-3-4-5
1-2-3-4-6-7

Cyclomatic complexity = E-N+2P

=8-9+2*2
=3
8. References

Websites
1. www.w3schools.com
2. www.github.com
3. www.geeksforgeeks.com
4. www.stackoverflow.com

Books
1. Learning PHP, MySQL and JavaScript by Robin Nixon
2. Beginning PHP and MySQL by W.J .Gilmore