Online Banking System

ONLINE BANKING SYSTEM
AIM: To create a system to perform the Online Banking System.

Problem Statement for Online Banking System :
As the banking industry increasingly shifts towards digital solutions, there is a growing demand for
efficient, secure, and user-friendly online banking services. Customers seek the convenience of managing
their finances from anywhere at any time, leading to the need for a robust online banking system that
provides a wide range of services.
Current Challenges:
1. Limited Access to Banking Services: Traditional banking methods often require physical visits to
branches, leading to time constraints and inconvenience for users.
2. Security Concerns: With the rise of cyber threats, customers are concerned about the safety of
their financial information and transactions.
3. Inefficient Transactions: Users face delays in processing transactions, especially for transfers and
bill payments, which can lead to frustration.
4. Poor User Experience: Existing online banking platforms may lack intuitive interfaces, making
navigation difficult for users of all ages.
5. Inadequate Customer Support: Many systems do not provide timely and effective customer
support, leaving users without assistance when issues arise.
Objectives:
The goal of the online banking system is to:
1. Provide Seamless Access: Enable users to access their accounts and perform transactions anytime
and anywhere via a secure web or mobile platform.
2. Enhance Security: Implement robust security measures, including encryption and multi-factor
authentication, to protect user data and transactions.
3. Streamline Transactions: Ensure quick processing of deposits, withdrawals, transfers, and bill
payments.
4. Improve User Experience: Design an intuitive and responsive user interface that caters to users of
varying technical expertise.
5. Offer Comprehensive Support: Develop a reliable customer support system to assist users with
inquiries and technical issues.
Scope:
The online banking system will include features such as:
● User registration and authentication
● Account management (viewing balances, transaction history)
● Fund transfers between accounts
● Bill payment services
● Transaction history and statement generation
● Security features (password recovery, account locking)
● Customer support (live chat, FAQs)
USE CASE DIAGRAM
In UML, use-case diagrams model the behavior of a system and help to capture the requirements of the
system. Use-case diagrams describe the high-level functions and scope of a system. These diagrams also
identify the interactions between the system and its actors.
DOCUMNETATION OF USECASE DIAGRAM

1.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.
2.Each customer is an actor for the Use-Case Diagram and the functionality offered by Online Banking
System to Add Account is Use-Case.
3.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.
4.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.
5.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.
6.A customer can also request loan from bank where customer must add request for loan with the
appropriate details.
7.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.
8.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.
9.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.
CLASS DIAGRAM
A UML class diagram is a visual tool that represents the structure of a system by showing its classes,
attributes, methods, and the relationships between them. It helps everyone involved in a project—like
developers and designers—understand how the system is organized and how its components interact.
DOCUMENTATION OF CLASS DIAGRAM

The class diagram outlines the structure of an online banking system by showing the system's
classes, their attributes, methods, and relationships. This diagram provides a blueprint for the system's
object-oriented design.
User ↔ Account: One-to-Many (A user can have multiple accounts)
Account ↔ Transaction: One-to-Many (An account can have multiple transactions)
User ↔ NotificationService: One-to-Many (A user can receive multiple notifications)
User ↔ Customer Support: One-to-Many (A user can have multiple support tickets)
Transaction ↔ Payment Gateway: Many-to-One (Multiple transactions can use the same
payment gateway)
SEQUENCE DIAGRAM.
A sequence diagram is a Unified Modeling Language (UML) diagram that illustrates the sequence of
messages between objects in an interaction. A sequence diagram consists of a group of objects that are
represented by lifelines, and the messages that they exchange over time during the interaction.
DOCUMENTATION OF SEQUENCE DIAGRAM

A sequence diagram illustrates the interactions between different components of an online banking
system over time. It helps visualize the flow of messages and the order in which they occur during
specific processes, such as funds transfer or account management.
COLLABRATION DIAGRAM
In UML (Unified Modeling Language), a Collaboration Diagram is a type of Interaction Diagram that visualizes the
interactions and relationships between objects in a system. It shows how objects collaborate to achieve a specific task or
behavior. Collaboration diagrams are used to model the dynamic behavior of a system and illustrate the flow of messages
between objects during a particular scenario or use case.
DOCUMENTATION OF COLLABORATION DIAGRAM

The collaboration diagram illustrates the interactions between different components of the online
banking system during specific use cases. It emphasizes the relationships and message flow among
objects to achieve a specific task.
User interacts with Authentication Service to log in.
Upon successful authentication, User communicates with Transaction Service to initiate the fund
transfer.
Transaction Service interacts with the respective Account objects to validate and process the
transaction.
Finally, Transaction Service sends a notification through NotificationService to inform the User about the
transaction status.
STATE CHART DIAGRAM
A state diagram (also known as a state machine or state chart diagram) is an illustration of all the possible
behavioral states a software system component may exhibit and the various state changes it's predicted to
undergo over the course of its operations.
DOCUMENATATION OF STATE CHART DIAGRAM

The user can access services by logging in the system using valid login credentials which are unique for
every registered customer at the bank. As the first state in the diagram represents the action to enter
login credentials to verify and validate the user. However, if the login credentials are incorrect there
occurs a transition to the next state to display the error message. Also, the user can now retry to log in
the system. After several attempts, if the user fails to enter the correct OTP(One Time Password) the
user can not try again and the process encounters a final state.
If the user credentials are verified the user is allowed to either check balance or get details of a cheque
under processing or avail other services offered by the bank. If the action is to check balance, the system
retrieves the data for the user from the database and the balance in the account of the user is displayed
in the next state. The process to check balance terminates and the process encounters the final stage.
However if the user chooses to initiate a transaction, the user selects to initiate a transaction
represented as a specific state in the diagram. Also, an after the transaction is successfully initiated the
user has to select the account type in the next state. The user selects the account, which acts as an
internal event to trigger the next state which allows the user to enter the amount to be transacted over.
After the transaction is executed the flow of control again shifts to check balance where the user can
check the balance in the account after the transaction. The process again terminates as described above
at the final stage.
ACTIVITY DIAGRAM
Activity diagrams are an essential part of the Unified Modeling Language (UML) that
help visualize workflows, processes, or activities within a system. They depict how
different actions are connected and how a system moves from one state to another. By
offering a clear picture of both simple and complex workflows, activity diagrams make it
easier for developers and stakeholders to understand how various elements interact in
a system.
DOCUMENATATION OF ACTIVITY DIAGRAM

The activity diagram for an online banking system illustrates the sequence of activities and the flow of
control within various banking processes conducted through an online platform. It outlines how users
interact with the system to perform essential tasks such as logging in, viewing account details,
transferring funds, paying bills, and logging out. The diagram captures the flow from the initial login
phase, where the user authenticates their identity, through various transactional activities like checking
balances, initiating transfers, and confirming transactions. It also includes decision points for activities
requiring additional authentication or user inputs, ensuring security and accuracy.
COMPONENT DIAGRAM
In UML, component diagrams show the structure of the software system, which describes the software
components, their interfaces, and their dependencies. You can use component diagrams to model
software systems at a high level or to show components at a lower, package level.
This type of diagram supports component-based development in which a software system is divided into
components and interfaces that are reusable and replaceable.
DOCUMENTATION OF COMPONENT DIAGRAM

In an online banking system, a component diagram outlines the various components and their
interactions. Key components typically include:
User Interface: Web and mobile interfaces for customer interaction.

Application Server: Hosts the business logic, handling requests from the user interface.
Database: Stores user data, transaction records, and account information.
Authentication Service: Manages user authentication and authorization.
Payment Gateway: Facilitates online transactions and integrates with external payment services.
Notification Service: Sends alerts and updates to users via email or SMS.
Reporting Service: Generates financial reports and statements for users and administrators.
These components communicate through defined interfaces, ensuring modularity and scalability while
providing a clear view of system architecture.
DEPLOYMENT DIAGRAM
A Deployment Diagram is a type of Structural UML Diagram that shows the physical deployment of
software components on hardware nodes. It illustrates the mapping of software components onto the
physical resources of a system, such as servers, processors, storage devices, and network infrastructure.
Documentation of deployment diagram:

A deployment diagram for an online banking system helps to visualize the physical deployment of
software components on various hardware nodes, depicting how the system will be hosted, accessed,
and structured in terms of networking and infrastructure. Here’s a structured outline of the
documentation for an online banking system deployment diagram:
The deployment diagram consists of nodes (devices) and the components they host.
Describes the interaction between client devices, application servers, and the database.
Component Interactions
Client Device ↔ Web Server: User initiates requests (login, transaction, etc.) which are sent over HTTPS.
Web Server ↔ Application Server: Requests are forwarded to the application server to execute
business logic.
Application Server ↔ Database Server: The application server accesses the database server to retrieve
or store data.
Application Server ↔ External Systems: Processes certain payments through third-party systems.
Deployment Diagram
A visual diagram showing:
Nodes (Client Device, Web Server, Application Server, Database Server, and External Systems)
Relationships (secure connections and data flow)
Software components hosted on each node (e.g., Web Application, Business Logic Layer, Database
Schema)
Deployment Process
Installation: Set up each node (web, application, and database servers).
Configuration: Secure and configure servers, firewalls, and databases.
Testing: Validate secure connections, load balancing, and data transactions.
RESULT: Thus the project Online Banking System using Rational Rose Software and to implement the
software in visual basic is done successfully.

Online Banking System

Uploaded by

Copyright:

Available Formats

Online Banking System

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Online Banking System

Uploaded by

Copyright:

Available Formats

ONLINE BANKING SYSTEM

AIM: To create a system to perform the Online Banking System.

DOCUMNETATION OF USECASE DIAGRAM

DOCUMENTATION OF CLASS DIAGRAM

User ↔ Account: One-to-Many (A user can have multiple accounts)

Account ↔ Transaction: One-to-Many (An account can have multiple transactions)

User ↔ NotificationService: One-to-Many (A user can receive multiple notifications)

DOCUMENTATION OF SEQUENCE DIAGRAM

DOCUMENTATION OF COLLABORATION DIAGRAM

User interacts with Authentication Service to log in.

DOCUMENATATION OF STATE CHART DIAGRAM

DOCUMENATATION OF ACTIVITY DIAGRAM

DOCUMENTATION OF COMPONENT DIAGRAM

User Interface: Web and mobile interfaces for customer interaction.

Documentation of deployment diagram:

You might also like

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.