SecureBank Internet Banking System
Document 1: Project Overview
Version: 1.0
Prepared By: Muqaddas Rasheed
Role: Manual QA Engineer
Project Type: Web Application
Testing Type: Manual Testing
Methodology: Agile Scrum
Repository: Manual-QA-Banking-Project
1. Project Introduction
Project Name
SecureBank – Internet Banking System
Project Description
SecureBank is a fictional online banking application that enables customers to
securely access and manage their bank accounts through a web browser. The system
provides essential banking services such as account management, money transfers,
bill payments, beneficiary management, debit card services, profile management, and
transaction history.
The objective of this project is to perform comprehensive manual testing to ensure
that the application meets functional, usability, security, and performance
expectations before release.
This project simulates a real-world banking application and demonstrates industry-
standard QA documentation and testing practices suitable for a professional portfolio.
2. Business Objective
The primary objectives of SecureBank are:
Provide secure online banking services
Enable customers to manage accounts anytime
Reduce dependency on physical bank branches
Ensure safe and fast financial transactions
Improve customer experience
Protect customer financial data.
3. Project Scope
Included in Scope
User Registration
Login
Logout
Forgot Password
OTP Verification
Dashboard
Savings Account
Current Account
Balance Inquiry
Transaction History
Money Transfer
Beneficiary Management
Bill Payments
Card Management
Profile Management
Security Settings
Notifications
Out of Scope
ATM Software
Mobile Banking Application
Internal Bank Employee Portal
Loan Processing
Credit Card Approval System
Investment Services
Insurance Services
4. Users of the System
Customer
Can:
1. Login
2. View balance
3. Transfer money
4. Pay bills
5. Manage beneficiaries
6. Update profile
7. View statements
Bank Administrator
Can:
1) Manage users
2) Monitor transactions
3) Freeze accounts
4) Generate reports
5) Handle customer requests
Customer Support
Can:
1. Reset passwords
2. Verify customer identity
3. Resolve complaints
4. Monitor service requests
5. Technology Stack (Sample)
Component Technology
Frontend HTML5, CSS3, JavaScript
Backend Java
Framework Spring Boot
Database MySQL
API REST API
Browser Chrome, Edge, Firefox
OS Windows 11
6. Application Modules
Module 1 – Authentication
Features
Login
Logout
Forgot Password
OTP Verification
Change Password
Remember Me
Module 2 – Dashboard
Features
Account Summary
Current Balance
Quick Transfer
Notifications
Recent Transactions
Module 3 – Accounts
Features
Savings Account
Current Account
Mini Statement
Full Statement
Download Statement
Module 4 – Fund Transfer
Features
Transfer Within Bank
Transfer to Other Bank
Scheduled Transfer
Immediate Transfer
Cancel Transfer
Module 5 – Beneficiary Management
Features
Add Beneficiary
Edit Beneficiary
Delete Beneficiary
Activate Beneficiary
View Beneficiary List
Module 6 – Bill Payments
Features
Electricity Bill
Gas Bill
Internet Bill
Water Bill
Mobile Recharge
Module 7 – Debit Card Services
Features
1. Block Card
2. Replace Card
3. Change PIN
4. Set Daily Limit
5. Enable International Transactions
Module 8 – Profile Management
Features
Update Address
Update Phone Number
Update Email
Upload Documents
Security Questions
7. Assumptions
User has a valid bank account.
User has an active internet connection.
OTP service is available.
Email and SMS services are operational.
Browser supports JavaScript.
Backend services are available.
8. Constraints
Internet connectivity is required.
OTP expires after 5 minutes.
Maximum transfer limit is configurable.
Password policy must be followed.
Session expires after 10 minutes of inactivity.
9. Risks
Risk Impact Mitigation
Server downtime High High-availability infrastructure
Incorrect transactions High Validation and confirmation screens
Unauthorized access Critical MFA, OTP, session timeout
Database failure High Regular backups and replication
Slow response time Medium Performance optimization
10. QA Objectives
The QA team will verify:
All business requirements are implemented correctly.
Functional workflows operate as expected.
Invalid inputs are handled gracefully.
Security controls work correctly.
Critical banking transactions complete successfully.
Data is stored accurately in the database.
APIs return correct responses.
No critical defects remain before release.
11. Deliverables
The QA team will produce:
Test Plan
Test Scenarios
Test Cases
Requirement Traceability Matrix (RTM)
Bug Reports
Test Execution Report
SQL Validation Scripts
API Test Cases
Jira Defect Reports
Test Summary Report
12. Entry Criteria
Testing begins when:
1. Requirements are approved.
2. Build is deployed to QA.
3. Test environment is ready.
4. Database is configured.
5. Test data is available.
13. Exit Criteria
Testing is complete when:
1) All critical test cases pass.
2) No Critical or High severity defects remain open.
3) Regression testing passes.
4) Test Summary Report is approved.
5) Stakeholders approve the release.
6) Business goals
7) Stakeholders
8) Functional requirements
9) Non-functional requirements
10) Business rules
11) Assumptions and constraints
12) Acceptance criteria