A

Micro project report on

“Banking System Management”

SUBMITTED TO M.S.B.T.E., Mumbai

For the Award of

DIPLOMA IN COMPUTER ENGINEERING

BY

Roll Name of Enrollment no Sign.

no Student

22 Sanskruti Mukund Wadkar 2210740188

53 Pratiksha Pradeep Kshirsagar 2210740220
55 Nandini Dipak Yadav 2210740222
67 Sanika Babruvan Galgunde 2212140226

UNDER THE GUIDANCE OF

Ms. S. A. Solankar
DEPARTMENT OF COMPUTER
ENGINEERING NBA

ACCREDIATED

SVERI’s College of Engineering

(Polytechnic),Pandharpur Gopalpur
Pandharpur-413304 2024-25
AFFILIATED TO

M.S.B.T.E.
Evolution sheet for Micro Project

Academic Year:- 2024-25 Name of Faculty:

Ms. R. S. Solankar

Course:- Computer Engineering Course code:- CO5I

Subject: Software Subject Code:-22518
Testing
Semester:- 5 Scheme:- I

Title of Banking System Management

Project:-

COs addressed by the Micro Project:

CO 2 Students learn game logic, coding, UI design, and debugging skills.

Comments/Suggestions about team work/leadership/inter-personal communication (if any)

Marks out Marks out of4 Total

of6 for for marks
performance performance in out of
Roll No Name of students oral/
in group 10
activity Presentation

22 Sanskruti Mukund Wadkar

53 Pratiksha Pradeep Kshirsagar
55 Nandini Dipak Yadav
67 Sanika Babruvan Galgunde

Name and
Signature of Ms. R. S. Solankar
faculty
 Project Title:

Software Testing for Banking Management System

Introduction:
In the contemporary digital landscape, banking systems have become central to our economic activities,
handling a vast array of transactions and personal data. The increasing reliance on these systems necessitates
robust software management to ensure their reliability, security, and efficiency. Software testing plays a crucial
role in achieving these objectives by systematically verifying and validating the functionality, performance,
and security of banking systems.

Project Description:
This project involves designing and executing a comprehensive software testing strategy for a
Banking Management System. The goal is to ensure that the system is reliable, secure, performs well,
and provides a user-friendly experience.

Project Objectives:
 Validate all functional requirements of the BMS.
 Ensure system performance under load conditions.
 Verify the security and data protection mechanisms.
 Assess the usability and accessibility of the system.

Methodology:
1. Test Planning:

a) Test Strategy:
Define the testing approach, including types of tests to be performed, tools to be used, and
testenvironments.
b) Test Plan:
Develop a detailed test plan outlining objectives, scope, resources, schedule, and risk management.

2. Test Design:

a) Test Case Development:

Create test cases based on functional and non-functional requirements. Include test scenarios, input
data,expected results, and execution steps.

b) Test Data Preparation:

Prepare necessary test data for various test cases, ensuring it covers a range of scenarios.

Test Planning:

1. Objectives:
 Verify that all functional requirements are met.
 Ensure the system performs well under expected loads.
 Validate the system’s security and data protection measures.
 Ensure the system is user-friendly and meets accessibility standards.
 2. Scope:
a. Functional Testing: Core functionalities such as account management, transactions,
and user authentication.

b. Non-Functional Testing: Performance, security, and usability.

3. Specification:-

1. Functional Specifications:

a) User Management:-

 Account Creation: Users can create new accounts by providing personal details and initial deposit.
 Account Deletion: Authorized users (e.g., admin) can delete accounts.
 User Authentication: Users must log in using valid credentials; includes password reset functionality.

b) Account Management:-

 Account Details: Users can view and update their account details (e.g., address, phone number).
 Balance Inquiry: Users can check their current account balance.
 Transaction History: Users can view past transactions.

c) Transaction Processing:-

 Fund Transfer: Users can transfer funds between their own accounts or to other accounts.
 Deposit: Users can deposit funds into their accounts.
 Withdrawal: Users can withdraw funds from their accounts.

d) Security and Compliance:-

 Encryption: Sensitive data (e.g., passwords, transaction details) should be encrypted.

 Access Control: Different user roles (e.g., customer, admin) have different access levels.
 Audit Trails: All transactions and account modifications are logged for auditing.

e) Reporting and Notifications:-

 Account Statements: Users can generate and download account statements.

 Alerts: Users receive alerts for critical activities (e.g., large transactions, login attempts).
2. Non-Functional Specifications:

a) Performance:-

 Response Time: The system should respond to user requests (e.g., balance inquiry) within 2 seconds
under normalload.
 Scalability: The system should handle up to 500 concurrent users without performance degradation.

b) Reliability:-

 Availability: The system should be available 99.9% of the time (excluding scheduled maintenance).
 Backup and Recovery: The system should have a backup and recovery plan to prevent data loss.

c) Usability:-

 User Interface: The system should have an intuitive and user-friendly interface.
 Accessibility: The system should be accessible to users with disabilities, following accessibility
standards.

d) Security:-

 Authentication: Strong authentication mechanisms (e.g., multi-factor authentication) should be in place.

 Authorization: Proper authorization checks should ensure users only access functionalities they are
permitted to.
 Data Protection: Compliance with data protection regulations (e.g., GDPR) to ensure user data is
handled securely.

e) Maintainability:-

 Code Quality: The system should be developed with maintainable code practices and documentation.
 Error Handling: The system should handle errors gracefully and provide meaningful error messages.

f) Compatibility:-

 Browser Support: The system should be compatible with major web browsers (e.g., Chrome,
Firefox, Safari, Edge).
 Device Compatibility: The system should be accessible on various devices (e.g., desktop,
tablet, smartphone).

Testing Types and Techniques:

a. Functional Testing:-

 Verify that all banking features work as expected.

 Test user scenarios such as account creation, transaction processing, and loan management.

b. Security Testing:-

 Ensure that sensitive data is protected.

 Test for vulnerabilities like SQL injection, cross-site scripting (XSS), and unauthorized access.

c. Performance Testing:-

 Assess system performance under load (e.g., multiple simultaneous transactions).

 Measure response times and system behavior under stress.
d. Usability Testing:-

 Evaluate the user interface for ease of use and intuitiveness.

 Gather feedback on user experience.

e. Regression Testing:-

 Ensure that new changes or features do not negatively impact existing functionality.

f. Compatibility Testing:-

 Check the system’s compatibility with various browsers, devices, and operating systems.

Testing Tools:

a. Test Management Tools:-

 JIRA: For tracking defects and managing test cases.

 TestRail: For managing and organizing test cases and results.

b. Automated Testing Tools:-

 Selenium: For automating web application testing.

 JUnit/TestNG: For unit testing Java-based applications.

c. Performance Testing Tools:-

 JMeter: For load and performance testing.

d. Security Testing Tools:-

 OWASP ZAP: For finding vulnerabilities and security issues.

Tes t Test Case Descripti Input Data Expected Actual Status
Case Name on Result Result
ID

TC01 Account Verify Name: John Doe, Account Account Pass

Creation account Email: created created
creation john@example.co successfully. successfully.
with m Confirmatio Confirmatio
valid , Initial Deposit: n email sent. n email sent.
details $500
TC02 Account Verify Name: Jane Account Account Pass
Creation account Doe, Email: creation creation
(Invalid creation janeexample.co should fail. failed. Error
Email) with m, Initial Error message
invalid Deposit: message displayed.
email $300 displayed.
format
TC03 Fund Validat From Account: Transfer Transfer Pass
Transfer e fund 12345, To successful. successful.
transfer Account: Both Both
betwee 67890, Amount: accounts accounts
n $200 updated. updated.
accounts
TC04 Balance Check Account Balance Balance Pass
Inquiry balance Number:12345 should updated
after reflect the correctly.
transactio latest
n transaction.
TC05 Login Verify Username: Login Login Pass
Functionality user login john_doe, successful. successful.
with valid Password: User User
credentials password1 dashboard dashboard
23 displayed. displayed.
TC06 Login Verify Userna Login should Login failed. Pass
Functionalit y user login me: fail. Error Error message
(Invalid with john_do message displayed.
Password) invalid e, displayed.
password Passwor
d:
wrongpassword
TC07 Account Verify Account Account Account Pass
Deletion account Number: 12345, deleted deleted
deletio Admin Access: successfully. successfully.
n Yes
process
TC08 Transaction Check Account Transaction Transaction Pass
History transactio Number:12345 history history
n displayed displayed
history for correctly. correctly.
an account
TC09 Performanc e Validate Number of System System Pass
under Load system concurrent should handled load
performan users:100 handle load well.
c e with without
concurren performance
tusers degradation.
Testing Strategy:

 Planning:- Define test objectives, resources, and timelines.

 Designing:-Create detailed test cases and test scripts.
 Execution:- Perform testing according to the test plan.
 Reporting:- Document defects, test results, and provide feedback.
 Review:- Assess the testing process and suggest improvements.

Importance of Banking Systems:

Banking systems are complex applications designed to manage financial transactions, customer accounts, and
other banking operations. These systems support critical functionalities such as:

 Account Management: - Enabling users to create, update, and delete accounts.

 Transaction Processing: - Facilitating deposits, withdrawals, and transfers.
 Security Measures: - Protecting sensitive financial data through encryption and secure access controls.
 Regulatory Compliance: - Ensuring adherence to financial regulations and standards.
 Reporting: - Providing detailed financial statements and transaction histories.
Conclusion:
Summarize the findings from the testing process, including identified defects, performance
metrics, and areas for improvement. Discuss how the testing contributed to the overall quality
and reliability of the banking system management application.

In summary, software testing is vital for ensuring that banking systems are reliable, secure,
and user-friendly. By systematically addressing functional, security, performance, usability,
regression, and compatibility aspects, testing helps maintain the integrity of banking
operations and protects against potential risks. As the financial sector continues to evolve
with technological advancements, the role of software testing in safeguarding banking
systems remains crucial for maintaining trust and operational excellence.
References:
 Books and Articles on Software Testing: Include any relevant textbooks or research
papers.
 Online Resources: Links to tools and tutorials used.