0% found this document useful (0 votes)
10 views7 pages

Online Banking System

The document provides an overview of an Online Banking System (OBS) and its architecture through various diagrams including Use Case, Class, ER, Sequence, Activity, and Data Flow Diagrams. Each diagram serves a specific purpose, such as defining user roles, structuring system entities, and illustrating data movement. The conclusion emphasizes the importance of these diagrams for efficient system development and understanding of the OBS architecture.

Uploaded by

m18961282
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
10 views7 pages

Online Banking System

The document provides an overview of an Online Banking System (OBS) and its architecture through various diagrams including Use Case, Class, ER, Sequence, Activity, and Data Flow Diagrams. Each diagram serves a specific purpose, such as defining user roles, structuring system entities, and illustrating data movement. The conclusion emphasizes the importance of these diagrams for efficient system development and understanding of the OBS architecture.

Uploaded by

m18961282
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 7

Online Banking System – Diagrams and Explanation

An Online Banking System (OBS) enables customers to perform financial


transactions, manage their accounts, and access banking services through the
internet. To understand the system's architecture, functionality, and interactions,
we use various diagrams such as Use Case Diagrams, Class Diagrams, ER
Diagrams, Sequence Diagrams, Activity Diagrams, and Data Flow
Diagrams (DFDs). Below is a detailed theoretical explanation of each diagram.

1. Use Case Diagram


Definition:
A Use Case Diagram represents the interaction between different users
(actors) and the functionalities they can perform within the Online Banking
System.
Actors in Online Banking System:
 Customer – Logs in, transfers funds, checks account balance, pays bills,
and requests loans.
 Admin – Manages customer accounts, staff, transactions, and system
configurations.
 Bank Staff – Approves loans and handles customer service requests.
 System – Sends notifications, processes transactions, and generates
reports.
Use Cases:
 Customer logs in and views account details.
 Customer transfers money to another account.
 Customer pays bills for utilities, credit cards, etc.
 Customer applies for a loan, and bank staff approves or rejects the
request.
 The system generates monthly account statements and transaction
reports.
Purpose:
The Use Case Diagram helps understand the system's core functionalities and
user interactions. It ensures that all user roles and their capabilities are well-
defined.
2. Class Diagram
Definition:
A Class Diagram represents the structure of the system by defining its classes,
attributes, methods, and relationships among different components.
Main Classes:
1. Customer
o Attributes: customerID, name, email, phone, accountType

o Relationship: Has an Account and may apply for a Loan.

2. Account
o Attributes: accountID, customerID, balance, accountType

o Relationship: Maintains multiple Transactions.

3. Transaction
o Attributes: transactionID, accountID, type, amount, date

o Relationship: Linked to an Account for recording deposits,


withdrawals, and transfers.
4. Loan
o Attributes: loanID, customerID, amount, interestRate, status

o Relationship: Linked to a Customer, approved by Bank Staff.

5. Bank Staff
o Attributes: staffID, name, role

o Relationship: Manages loan applications.

Purpose:
The Class Diagram is useful for database design and object-oriented
programming. It helps in defining relationships and system structure before
implementation.

3. Entity-Relationship (ER) Diagram


Definition:
An ER Diagram represents how entities (database tables) are related in the
system.
Entities and Their Relationships:
 Customer (PK: customerID) → Owns multiple Accounts.
 Account (PK: accountID) → Contains multiple Transactions.
 Customer → Applies for Loans.
 Bank Staff → Processes and approves Loans.
Purpose:
The ER Diagram helps in designing the relational database schema by clearly
showing relationships among tables.

4. Sequence Diagram (Funds Transfer)


Definition:
A Sequence Diagram shows the step-by-step interaction between users and
the system for a specific process.
Steps in a Funds Transfer:
1. Customer logs in to the system.
2. Customer initiates a transfer request.
3. System validates account details.
4. Bank server processes the transaction.
5. System updates the account balance and sends confirmation.
Purpose:
The Sequence Diagram is useful for understanding the communication flow
between different system components.

5. Activity Diagram (Loan Application)


Definition:
An Activity Diagram represents the workflow of a process.
Workflow for Loan Application:
1. Customer applies for a loan.
2. System validates customer details.
3. Bank staff reviews the request.
4. If approved, loan contract is generated and funds are disbursed.
5. If rejected, customer is notified.
Purpose:
The Activity Diagram helps in identifying decision points, conditions, and
workflow sequences.

6. Data Flow Diagram (DFD Level 0)


Definition:
A Data Flow Diagram (DFD) illustrates how data moves through the system.
Data Flow in Online Banking System:
 Customer logs in → System verifies credentials.
 Customer requests transaction → System processes the transaction.
 Bank staff processes loan requests → System updates loan records.
 System sends transaction notifications → Customer receives updates.
Purpose:
The DFD helps in understanding how data is processed and transferred between
different entities in the system.

Conclusion
The Online Banking System consists of multiple components that interact to
provide seamless banking services to customers.
Each diagram serves a specific purpose:
✅ Use Case Diagram defines user roles and system functionalities.
✅ Class Diagram structures the system's entities and their relationships.
✅ ER Diagram helps in database design.
✅ Sequence Diagram explains process flow.
✅ Activity Diagram outlines workflows.
✅ DFD showcases data movement within the system.
These diagrams ensure efficient system development, better visualization,
and improved understanding of the Online Banking System's
architecture. 🚀

You might also like