Scribd
Upload
15 views9 pages

Online Banking System

Uploaded by

Aarchie Maggu
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
15 views9 pages

Online Banking System

Uploaded by

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

ONLINE BANKING SYSTEM

SRS Document
Describes software functionality and
performance expectations.
Outlines requirements to meet stakeholder
needs.
Details processes for creating, updating, and
closing customer accounts.
Outlines procedures for secure and efficient
deposits, withdrawals, and transfers.
Defines requirements for handling loan
applications, approvals, and repayment tracking.
Classifies user groups such as customers, bank
staff, and administrators, with distinct access and
permissions.
USE-CASE MODEL
1. Defines software requirements for banking
system functionality, performance, and
stakeholder needs.
2. Details account management processes,
including account creation, updates, and
closure.
3. Outlines transaction processing, covering
deposits, withdrawals, and transfers.
4. Specifies loan services requirements for
applications, approvals, and repayments.
5. Identifies user roles and permissions for
customers, bank staff, and administrators.
CLASS DIAGRAM
A class diagram visually represents a system's
structure in object-oriented modeling.
It displays classes with attributes (data fields)
and methods (functions or operations).
Classes are shown as rectangles containing both
data and behavior.
Relationships like association, inheritance,
aggregation, and composition are indicated by
connecting lines.
An online banking system example includes
Customer (attributes: customerID, methods:
login()) and Account (attributes: accountNumber,
methods: transferFunds()).
UML Sequence diagram

A UML Sequence Diagram is an interaction diagram


that shows object interactions in a time sequence.
It illustrates the objects involved and the sequence
of messages exchanged to fulfill a scenario.
Sequence diagrams help software developers and
business professionals document and understand
system requirements.
They capture how objects communicate to
complete specific functionality.
Example: In a banking system, a customer initiates a
money transfer from one account to another
through the bank's system.
State Chart and Activity Diagram

State Chart
illustrates the states and transitions an object
undergoes in response to events.
Represents the lifecycle of accounts or
transactions, such as "Pending," "Processing," and
"Completed."
Shows triggers that cause transitions, like
initiating a transfer or approving a transaction.
Displays how the system moves from one state
to another based on customer or system actions.
Helps developers understand object behaviors
and responses to specific events in the banking
process.
Activity Diagram
1. Visualizes the flow of activities and actions in a
system, showing step-by-step processes.
2. Represents the flow of a process, such as a
money transfer, from initiation to confirmation.
3. Includes activities like "Enter Transfer Details"
and decision points like "Insufficient Funds?"
4. Can show concurrent actions, such as
updating sender and receiver account
balances.
5. Provides a clear overview of the process flow,
aiding in identifying potential bottlenecks or
issues.
Test cases developed as per the use-case
diagram.

Ensure that all identified use cases in the diagram are covered by test
scenarios, confirming they meet functional requirements.
Test each scenario to verify that the system behaves as expected during
interactions, following the defined paths in the use-case diagram.
Evaluate edge cases and alternative flows outlined in the use-case diagram
to assess how the system handles exceptions or unusual conditions.
Involve stakeholders in reviewing test results for each scenario to ensure the
functionality aligns with their expectations and requirements.
Maintain traceability between use cases and test scenarios to ensure
comprehensive coverage and facilitate identification of any gaps or missing
scenarios.
Thank you!

You might also like