Bank Management System

P ROJECT R EPORT
BANK MANAGEMENT SYSTEM

By

Author Name: Maria Soomro

Course: Object Oriented Analysis & Design

Sukkur IBA University Khairpur Campus

1
 Bank Management System

TABLE OF CONTENTS

1. Introduction 03
1.1 Purpose 03
1.2 Scope 03
2. Problem Statement…………………………………………. 04
3. Vision ………………………………………………………. 05
1. Introduction ………………………………….... 05
1.1 Purpose………………………………. 05
1.2 Scope…………………………………. 05
2. Positioning …………………………………… 06
2.1 Business Opportunity………………… 06
2.2 Problem Statement …………………… 07
2.3 Product Position Statement ………… 07
3. Stakeholder and user Description……………… 08
3.1 Internal Stakeholder …………………. 08
3.2 Connected Stakeholder ………………… 09
3.3 External Stakeholder …………………. 09
3.4 User-Level Goals……………………… 10
3.5 Key Stakeholder or user needs ………. 10
3.6 Alternatives and Competition……………11
4. Product Overview………………………………… 11
4.1 Product Prospective…………………… 11
4.2 Assumptions and Dependencies……… 11
5. Product Features………………………………… 12
5.1 System Features ………………………… 12
5.2 Safety and Security Requirements ……… 13
6. Other Requirements and Constraints……………… 14
6.1 Other Requirements…………………………… 14
6.2 Constraints……………………………………. 15
4. Use Case Model …………………………………………... 16
4.1 Use Case # 1 Create Account …………………………… 17
4.2 Use Case # 2 View Customer List ……………………… 20
5. Case Study ……………………………………………………… 23
5.1 Find Candidate Classes…………………………………… 24
6. Domain Model ……………………………………………… 26
7. Sequence Diagram…………………………………………… 27
7.1 Create Account…………………………………………… 27
7.2 Log in……………………………………………………. 28
7.3 View Profile……………………………………………… 29
7.4 Transaction……………………………………………… 30
7.5 Request for Loan………………………………………… 31
7.6 View Customer List……………………………………… 32

2
 Bank Management System

[Link]
1.1 Purpose

The purpose of this document is to collect, analyze, and define high-level needs and features of

the Online Banking Application. It focuses on the capabilities needed by the stakeholders and the

target users, and why these needs exist. The further details of how the Application fulfills these

needs are discussed in the use-case and supplementary specifications.

1.2 Scope

This Vision Document applies to build a trustable and fault tolerant online banking system with

the flexibility to support the varying customers, easy to use, quick response and user interface

mechanism and integration with third-party supporting system.

3
 Bank Management System

2. PROBLEM STATEMENT

The existing software systems are inflexible, difficult, fault-tolerant, slow and not able to integrate

with the third-party system leading to problems in creating account, transfer the money, inaccurate

information of customer, time wasting and other related options. This affects the user and bank

manager, and other related stakeholders.

4
 Bank Management System

[Link]

[Link]

1.1 Purpose

The purpose of this document is to collect, analyze, and define high-level needs and features of

the Online Banking Application. It focuses on the capabilities needed by the stakeholders and the

target users, and why these needs exist. The further details of how the Application fulfills these

needs are discussed in the use-case and supplementary specifications.

1.2 Scope

This Vision Document applies to build a trustable and fault tolerant online banking system with

the flexibility to support the varying customers, easy to use, quick response and user interface

mechanism and integration with third-party supporting system.

5
 Bank Management System

2. POSITIONING

2.1 Business Opportunity

To be part of this world means busy life and where every second holds its importance, the existing

bank require your presence and time and have their time period to communicate with you after

which you are not allowed no matter how much it is important for you while the existing online

banking system are not that much trustable or easy to use, not able to respond quickly if various

customer are using at the same time resulting in failures and most of the time not able to integrate

with the third party system which in this case is (Nadra office). There is market dissatisfaction

with this inflexible system and require a better system to replace it.

2.2 PROBLEM STATEMENT

The existing software systems are inflexible, difficult, fault-tolerant, slow and not able to integrate

with the third-party system leading to problems in creating account, transfer the money, inaccurate

information of customer and time wasting and other related options. This affects the user and bank

manager, and other related stakeholders.

6
 Bank Management System

2.3 PRODUCT POSITION STATEMENT

For The person above 18 years can use this system

Who The people who want to save their time and easily

transfer their money or other related stuff.

The Online Banking System Is a software application

That Is trustable and have the ability to respond quickly, is

easy to use and can integrate with third-party system

Unlike The currently available systems that are slow to

respond, are not trustable, difficult, in tolerant and

have problem to integrate with third-party.

Our System Will help users to easily create account and use it

whenever he/she want, able to transfer money in

another account, see balance and transaction and can

easily get loan.

7
 Bank Management System

3. STAKEHOLDER AND USER DESCRIPTIONS

3.1 Internal stakeholders:

Directors & Managers:

Their main interest is basically on the salary, share portion as well as decision making. Job

satisfaction and status also affect. They got the major insider information of the bank.

Operators:

Several operators are engaged with the bank. They can be called as the employees. But in

online bank some special operators are required to operate the main program, they may also

hold the ownership to secure the functions.

8
 Bank Management System

3.2 Connected stakeholders:

Shareholders & investors:

They are the parties who concern about the share price growth, profit growth and dividends.

They also hold the right of election of directors.

Customers:

Based on the Reliable quality, value for money, product availability, customer service different

customers are the most important stakeholder for an online bank. They influence the revenue of

the bank.

3.3 External Stakeholders:

Government:

The Government is responsible for the framework in which public- and private organizations

operate. They create legislation and regulations, influencing the way bank can operate.

Nadra Office:

Insure that the provided CNIC is correct and then verify the customer provided data.

9
 Bank Management System

3.4 USER-LEVEL GOALS

The users (and external system) need a system to fulfill these goals:

1. Customers: Create an account, transfer the money, see balance and transaction, request

for loan or log in already sign in account.

2. Manager: Manages the customer account, view the customers list, verify the customer

request, remove an account, and verify the request for loan.

4.5 KEY STAKEHOLDER OR USER NEEDS

Need Proximity

Easy to use High

Flexible High

quick High

trustable High

3.6 ALTERNATIVES AND COMPETITION

 Other online banking systems

10
 Bank Management System

4. PRODUCT OVERVIEW

4.1 Product Perspective

This System creation idea is based upon the problems that are faced by the ordinary busy

Person. The bank management system to be developed benefits greatly the ordinary person and

bank management. This system can help the busy people to create the new account while sitting

anywhere if they have access to our application or they can even login into their already created

account and view their profile, they can do transaction of money and can even request for loan. It

also helps the manager to view the customer list and approve the request for new account if he

want to, he can also accept the request for loan if the reason seems validate to him.

4.2 Assumptions and Dependences

1. In using the onscreen keyboard, it is assumed that the user is literate and can type.

2. The default language for the software shall be US English.

11
 Bank Management System

5. Product Features

5.1 System FEATURES

Log in software

1. user

 Account create or log in already account.

 Transfer money

 See transaction

 See balance

 View profile

 Request for loan

2. Manager

 View customer list

12
 Bank Management System

5.2 Safety and Security Requirements

Safety Requirements

The database may get crashed at any certain time due to virus or operating system failure.

Therefore, it is required to take the database backup.

Security Requirements

Some of the factors that are identified to protect the software from accidental or malicious access,

use, modification below. Keep specific log or history data sets assign certain functions to different

modules

Software Quality Attributes

The Quality of the System is maintained in such a way so that it can be very user friendly to all

the users. The software quality attributes are assumed as under:

 Accurate and hence reliable.

 Secured.

 Fast speed.

 Compatibility.

13
 Bank Management System

6. Other Requirements and Constraints

6.1 Other Requirements:

Applicable Standards Proper Hardware must be provided.

System Requirements

The system needs to have .net environment installed.

The system must be configured with a database.

Documentation Requirements

User Manual

The User Manual describes the use of the system to client and manager. The user manual should

be available as a hard copy.

Installation Guides, Configuration, Read Me File

This document includes the installation instructions and configuration guidelines, which is

important to a full solution offering. Also, a Read Me file is typically included as a standard

component. Most users also appreciate documentation defining any known bugs and

workarounds in the Read Me file.

14
 Bank Management System

Labeling and Packaging

As this system is Open Source so there will be no sales for it and Package label will defined by

Company.

6.2 Constraints

Usability Requirement: The systems uses a pc screen as an interface. Since all the users are

familiar with the general usage of pc, no special training is required. The system is user-friendly.

Avability Requirement: The System is available 100% for the user and is used 24 hours a day and

2365 days in a year. The System shall be operational 24hours a day.

Efficiency Requirement: Mean Time to Repair (MTTP) - even if the system fails, the system will

be recovered backup within an hour or less.

Accuracy: The system shall provide 100% access reliability.

Performance Requirement: The information is refreshed at regular intervals depending upon

whether some updates have occurred or not. The system shall respond to the member in not less

than two second from the time of the request submittal.

15
 Bank Management System

[Link] Case Model

16
 Bank Management System

2.1 USE CASE: CREATE ACCOUNT

SCOPE: Banking System

Level: User goal

Primary actor: User

Stakeholder and interests:

user: simple and understandable language, fast entry, save data accurately, able to update

data.

Nadra authorization service: wants to receive the user verification authorization request in

the correct format.

Bank: trustworthy customer and customer satisfaction.

Bank management system: proper format of user information, accurate records of user,

properly saved data files.

Pre-condition: user knows how to use the computer and can read the English language.

17
 Bank Management System

Success Guarantee (or Post-condition): user account is created successfully, his/her data

is saved and nadra authorization approvals are recorded.

Main Success Scenario (or Basic Flow):

1. User opens the system.

2. User clicks on create account option.

3. The user enters the personal information.

4. The nadra authorization service approves the CNIC of the user

5. The system checks if similar account is already created or not, if not the account is

successfully created, and the data is saved.

6. The customer can also update the data if he/she want.

Extensions (or Alternative Flows):

3. If age is below 18

a. The system will not allow access to the account creation.

4. If CNIC is not approved from nadra or any error occur

[Link]-try message should be shown.

5. If data is not saved then,

a. message should be shown that “data is not saved, save again”.

18
 Bank Management System

Special Requirements:

 Touch screen UI on a large flat panel monitor. Text must be visible from 1-meter

distance.

 The quick responses should be there.

 Language internationalized on the text displayed.

Technology and Data Variation list:

*The user can enter information via keyboard or screen.

19
 Bank Management System

2.2 USE CASE: VIEW CUSTOMER LIST

SCOPE: Banking System

Level: User

Primary actor: Bank Manager

Stakeholder and interests:

Bank Manager: want proper format of list, customer data in proper order with no error,

able to search through the list, quick response.

Bank: trustworthy customer and customer satisfaction.

Bank management system: proper format of user information, accurate records of user,

properly saved data files.

Pre-condition: proper list format is saved, and signed customer data is available to view.

Success Guarantee (or Post-condition): Bank manager can view the list and search

through the list successfully.

Main Success Scenario (or Basic Flow):

[Link] Manager opens the system.

[Link] Manager log in the system.

20
 Bank Management System

[Link] manager click on view the customer list option

4. A proper format list is opened with customer information in order.

[Link] Bank Manager can view the accounts.

Extensions (or Alternative Flows):

2. if incorrect password is entered.

[Link] access to the system.

b. a re-try option is given.

4. if no proper format of list is in view,

a. the Manager can refresh the system.

b. can go back and again click the option.

Special Requirements:

 Touch screen UI on a large flat panel monitor. Text must be visible from 1-meter

distance.

 The quick responses should be there.

 Language internationalized on the text displayed.

21
 Bank Management System

Technology and Data Variation list:

*The Bank Manager can click via keyboard or screen.

22
 Bank Management System

[Link] STUDY: A BANKING SYSTEM

features to help the customer to create the account, sign in already created account, view profile,

transfer money, view balance and view transaction. It will provide access to already signed in

account.

The bank manager views the customer list. The manager can approve the request for loan judging

at the reason provided by the user. If the account has not been used for more than three months an

automatic warning will be sent to the user , the system will re-check the response of user if still

there is no sign system will again generate the second warning to the user, nadra authorization

service will work as third party in this system by providing the verification of customer on the

basis of CNIC provided by customer.

23
 Bank Management System

3.1 FIND CANDIDATES CLASSES

By removing the duplicates and other synonyms we get the following initial list of candidates

Software, operation, banking system, bank, customer, account, create account, view profile,

transfer money, transfer charges list, balance, transaction, database, customer list, databases,

money, bank manager, request, period, due date, deposit, nadra authorization service, manager.

Filter candidate classes

Software: itself system = discard

Operation: irreverent noise = discard

Banking system: no need = discard

Bank: is it system itself? No, it is the collection of accounts and saved data= yes

Customer: our user = yes

Account: owns the number and amount = yes.

Create account: hold the information about the customer = yes

view profile: require the order form of customer information by sorting so needed = yes

transfer money: it has a whole process associated with account = yes

transfer charges list: and come in transfer money or need a new class = on hold

balance: no need to create new class can come in view profile = discard

transaction: same as view balance = discard

database: it doesn’t require a new class = discard

customer list: same as view profile but it has a lot of changes a search icon would be provided

= yes

money: no need = discard

bank manager: the actor= yes

request: out of problem = discard

nadra authorization service: a third party = yes

manager: no need = discard

25
 Bank Management System

3. Domain Model

26
 Bank Management System

4. SEQUENCE DIAGRAM

4.1 CREATE ACCOUNT

27
 Bank Management System

4.2 LOG IN

28
 Bank Management System

5.3 VIEW PROFILE

29
 Bank Management System

5.4 TRANSACTION

30
 Bank Management System

5.5 REQUEST FOR LOAN

31
 Bank Management System

5.6 VIEW CUSTOMER LIST

32
 Bank Management System

33