Tribhuvan University
Institute of Science & Technology
Mechi Multiple Campus
Bhadrapur, Jhapa
B.Sc.CSIT
Fifth Semester
Report of System – Online Banking System
Submitted By: Submitted To:
Name: Sandhya Khanal Name: Er. Prakash Koirala
Roll No:27 Signature:
Table of Contents
1. Introduction ........................................................................................... 2
1.1 Problem Scenario............................................................................... 3
1.2 Project as a Solution ....................................................................... 4
2. Aims and Objectives ............................................................................. 5
3. Expected outcomes and Deliverables ................................................. 6
4. Project risks, threats, and contingency plans ................................... 7
5. Methodology ...................................................................................... 8-9
6. Resource Requirements .................................................................... 10
7. Work breakdown structure ................................................................ 11
8. Milestones chart ................................................................................. 12
9. Project Gantt chart ............................................................................. 13
10. DFD Diagram ............................................................................... 14-16
11. ER Diagram ...................................................................................... 17
12. Physical Database Design ................................................................ 18
13. Relational Database Design ............................................................. 19
14.Tables and Attributes .................................................................. 20-21
17. Decision table/tree ............................................................................ 22
18. Use case Diagram ........................................................................ 23-24
19. Class Diagram ................................................................................... 25
20. Sequence Diagram ............................................................................ 26
1
1.Introduction
As we all know, increase in technology has leads people to use internet facilities more.
The internet has indeed made life simpler and easier.People can communicate with
ease,shop online, and even work from anywhere.There are various services provided by
internet.Here,I am planning to develop an app which helps the customers for payments
and transaction through internet.
The name of my app is “Online Banking System”.Online Banking System is an electronic
payment system that enables customers of a bank to conduct range of financial
transaction.Online banking is also known as Internet banking or web banking. Online
banking offers customers almost every service traditionally available through a local
branch including deposits, transfers, and online bill payments.
Nowadays customers prefer online payment as it’s more convenient and saves
time.There will be less chances of payments delay and a customers can transfer money
from anywhere,at any time,without having to go to a physical location and can save time
of waiting on the queue.
2
1.1 Problem Scenario
There are different issues and challenges in online banking industry. One of the main
issues is Security.As online system come with a lot of security risks. Without proper
security measures,fraudsters can easily hack important financial information and
data.Issues like weak passwords and using unsecured networks make people vulnerable
to online attacks, like login credential theft and phishing, which could result in fraudulent
bank transactions.
Another problem is online banking system is subject to technical failures just like any
other software that is dependent on technology.System stability and efficiency can affect
your ability to access your accounts if your internet is slowed or stopped entirely. Similarly,
no matter how sophisticated the tech, bank servers are still prone to both intentional and
accidental downtime.System downtime can be a challenge as not only are users unable
to make payments or conduct transactions but concerns about data and fund security
also start to emerge.
3
1.2 Project as a Solution
In this app I will focus on demonstrating and explaining the security of online banking
system,and also educate customers on how to be more conscientious online by improving
their privacy and security habits. I would recommend to use multi-factor authentication to
the customers.I would make sure by explaining to customers that their funds are not at
risk if any technical issue occurs.
Changing consumer habits, as well as security and technical concerns are all major
challenges of online banking. By solving this problem banks will grow more advanced and
meet new customers.
Some of the safety tips include:
Never provide personal information including your passwords, credit card
information, account numbers to unknown persons.
Be cautious while providing bank details via online, before proceeding further
confirm with bank about the email you received.
Subscribe to SMS alerts and, wherever available, register for e-mail alerts, for
electronic banking transactions.
Notify the bank of any unauthorized electronic banking transaction at the earliest
after the occurrence of such transaction.
4
2. Aims and Objectives
The BANK has been working for Accounts information, Withdrawal, Deposit amount. In
this Software you can keep record for daily Banking transactions.
The Online Banking System's aims are to improve the efficiency and efficiency of
customers' business matters by providing a users-as-market solution, as well as to
improve the customer's customer service experience.
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,
with100% accuracy. Software is completely computerized, so it is not time consuming
process. No paper work required & can be implemented further.
5
3. Expected Outcomes and Deliverables.
This App is expected to provide various services to customers. Consumers aren't required
to visit a bank branch in order to complete most of their basic banking transactions. Basic
banking transactions such as paying bills and transferring funds between accounts can
easily be done 24 hours a day, seven days a week, wherever a consumer wishes. There
will be less chances of payments delay and a customers can transfer money from
anywhere, at any time, without having to go to a physical location. Some of the things
used in this system are listed below.
A user can create a new account and login to a variety of websites.
The user can easily find information about their finances and other aspects of
their life.
The user can easily find out about other online banking systems and how to
use them.
The user can always rely on the user manual and know the basic steps to get
started.
The system can track one's progress and whether or not they need to continue
a session.
6
4.Project risks, Threats and Contingency Plans
As risks and threats are not something new in software development. So, here are some
of risks and threats that can be expected in the software to be developed along with its
contingency plans.
SN Risks and Threats Probability Contingency
1. Code Issues Medium Testing code frequently and creating
coding standards for software
developers
2. Deadlines Low Creating a thorough project plan
3. Users review high Organizing surveys and testing
software
4. Low Productivity High Creating well placed project plan
5. Stake holder issues Medium Communication and setting clear
project goals
6. Poor risk management medium Identifying potential risks, creating risk
mitigation plans and carefully
monitoring tasks.
7
5. Methodology
Various software development life cycle methodologies are used to guide professionals
through their project-based work. The SDLC gives structure to the challenges of
transitioning from the starting to the conclusion of the project without overlooking a step.
The most common SDLC methodologies are given below:
• Waterfall Model
• V-Shape Model
• Iterative Model
• Spiral Model
• Big Bang Model
• Agile Model
For developing this app, I have chosen the Rational Unified Process (RUP) methodology
which is an agile methodology. The goal of Agile is to produce shorter development cycles
and more frequent product releases than traditional waterfall project management. This
shorter time frame enables project teams to react to changes in the client’s needs more
effectively. The different phases of RUP are as given below:
1.Project Planning:
As with any project, before beginning team should understand the end goal, the value to
the organization or client, and how it will be achieved. We can develop a project scope
here, but the purpose of using Agile project management is to be able to address changes
and additions to the project easily, so the project scope shouldn’t be seen as
unchangeable.
2.Product RoadMap Creation:
A roadmap is a breakdown of the features that will make up the final product. This is a
crucial component of the planning stage of Agile, because team will build these individual
features during each sprint. At this point, team will also develop a product backlog, which
is a list of all the features and deliverables that will make up the final product.
8
3.Release Planning:
When using Agile, project uses shorter development cycles (called sprints) with features
released at the end of each cycle. Before kicking off the project, team make a high-level
plan for feature releases and at the beginning of each sprint, It’ll revisit and reassess the
release plan for that feature.
4.Sprint planning:
Before each sprint begins, the stakeholders need to hold a sprint planning meeting to
determine:
What will be accomplished by each person during that sprint
How it will be achieved
Assess the task load
5.Daily stand-ups:
To help your team accomplish their tasks during each sprint and assess whether any
changes need to be made, hold short daily stand-up meetings.
6.Sprint review and retrospective:
After the end of each sprint, your team will hold meetings.Team will hold a sprint review
with the project stakeholders to show them the finished product. This is an important part
of keeping open communication with stakeholders. An in-person or video conference
meeting allows both groups to build a relationship and discuss product issues that arise.
9
6. Resource Requirements
We all know that; we need various kinds of resources to complete a project or any system.
The basic resources that are required for completing this project are given below:
• PC with window 8 or above
• IDE: Android Studio for writing code
• Draw.io for the construction of different charts and figures
• Programming language: Java
• Markup language: XML for UI design
• Database: MySQL
• Customers Account information
• Microsoft Word: for documenting project
10
7. Work breakdown structure
Figure 1: Work breakdown structure
11
8. Milestones chart
Figure 2: Milestone Chart
12
9. Project Gantt chart
Figure 3: Gantt Chart
13
10.DFD Diagram
A data flow diagram (DFD) is a graphical or visual representation using a standardized
set of symbols and notations to describe a business's operations through data
movement.
DFD 0:
DFD Level 0 is also called a Context Diagram. It's a basic overview of the whole system
or process being analyzed or modeled. It's designed to be an at-a-glance view, showing
the system as a single high-level process, with its relationship to external entities.
Figure 4: DFD 0
14
DFD 1:
Level 1 DFDs are still a general overview, but they go into more detail than a context
diagram. In level 1 DFD, the single process node from the context diagram is broken
down into sub-processes. As these processes are added, the diagram will need additional
data flows and data stores to link them together.
Figure 5: DFD 1
15
DFD 2:
2-level DFD goes one step deeper into parts of 1-level DFD. It can be used to plan or
record the specific/necessary detail about the system’s functioning.
Figure 6: DFD 2
16
11.ER-Diagram
An Entity Relationship (ER) Diagram is a type of flowchart that illustrates how “entities”
such as people, objects or concepts relate to each other within a system.
Figure 7: ER Diagram
17
12.Logical Database Table
A Logical Database is a special type of ABAP (Advance Business Application and
Programming) that is used to retrieve data from various tables and the data is interrelated
to each other. Also, a logical database provides a read-only view of Data.
13.Physical Database Design
Physical database design is the process of transforming a data model into the physical
data structure of a particular database management system (DBMS). Normally, Physical
Design is accomplished in multiple steps, which include expanding a business model into
a fully attributted model (FAM) and then transforming the fully attributed model into a
physical design model.
18
14.Relational database diagram
A relational (database) schema is a set of table definitions (stored base tables or derived
views), constraints, and derivation rules. A table scheme is a named set of attributes
(columns) that draw their values from domains. Each column, or column set, spanned by
a minimal uniqueness constraint is a candidate key.
19
15. Tables and Attributes:
Table1:Customer
Table2:Admin
20
Table3:Account
Table4:Transaction
21
18.Decision table/tree
A decision tree is a decision support tool that uses a tree-like model of decisions and their
possible consequences, including chance event outcomes, resource costs, and utility. It
is one way to display an algorithm that only contains conditional control statements.
22
19. Use Case Diagram
A use case diagram is a graphical depiction of a user's possible interactions with a
system. A use case diagram shows various use cases and different types of users the
system has and will often be accompanied by other types of diagrams as well. The use
cases are represented by either circles or ellipses.
Here, we will try to understand the design of a use case diagram for the Online
Banking System. Some possible scenarios of the system are explained as follows
:
A Customer is required to create an account to avail services offered by Bank.
Bank verifies detail and creates new account for each new customer. Each
customer is an actor for the Use-Case Diagram and the functionality offered by
Online Banking System to Add Account is Use-Case.
Each customer can check the balance in bank account and initiate request to
transfer an account across distinct branches of Bank. Cashier is an employee at
bank who supports service to the customer.
A customer can execute cash transactions where the customer must either add
cash value to bank account or withdraw cash from account. Either of two or both
that is credit as well as debit cash, might be executed to successfully execute one
or multiple transactions.
After each successful transaction customer might or might not want to get details
for action. Manager can check interest value for each account corresponding to
transaction to ensure and authenticate details.
A customer can also request loan from bank where customer must add request for
loan with the appropriate details.
The type of loan in accordance with purpose or the need for loan and term or
duration to pay back the loan must be provided by customer.
The manager of each branch of bank has choice to either accept or approve loan
to initiate process further or just reject request for loan based on terms and
conditions.
The record for each employee of bank is maintained by bank and bank manages
all employees of each branch of bank. The manager of each branch has choice to
offer bonus to employees. Note here that each employee is paid as part of
management of staff but promotion or bonus might or might not be offered certainly
to each employee.
23
24
20. Class diagram
In software engineering, a class diagram in the Unified Modeling Language is a type of
static structure diagram that describes the structure of a system by showing the system's
classes, their attributes, operations, and the relationships among objects.
25
21.Sequence diagram
A sequence diagram or system sequence diagram shows process interactions arranged
in time sequence in the field of software engineering. It depicts the processes involved
and the sequence of messages exchanged between the processes needed to carry out
the functionality.
26
27
