|| JAI SRI GURUDEV ||

Sri Adichunchanagiri Shikshana Trust

SJB INSTITUTE OF TECHNOLOGY

No. 67, BGS Health & Education City, Dr. Vishnuvardhan Road, Kengeri, Bengaluru -
560060
An Autonomous Institute under VTU
Approved by AICTE - New Delhi, Accredited by NAAC A+, Accredited by
NBA

Department of Artificial Intelligence and Machine Learning

SOFTWARE ENGINEERING - BCS501
BANK MANAGEMENT SYSTEM

Presented by Under the guidance of

Kanish Rishab D-1JB22AI024 Mrs.Shridevi Sali
Bhavana Suresh-1JB22AI009 Asst. Professor Dept of
AI&ML,SJBIT
OBJECTIVE OF THE BANK MANAGEMENT SYSTEM
To develop a secure, efficient, and scalable Bank Management System that meets dynamic customer
needs, adheres to regulatory compliance, and mitigates fraud.
Dynamic Customer Needs:

Modern banking requires adaptability to changing user expectations, such as mobile banking, real-time
notifications, and personalized financial insights.
Example: Integrating features like loan calculators and AI-driven customer support.
Compliance Requirements:

Adherence to strict banking regulations, such as:

Anti-Money Laundering (AML) laws.
Know Your Customer (KYC) protocols.
General Data Protection Regulation (GDPR) for data privacy.
Fraud Prevention:

Protecting customer accounts from unauthorized access and suspicious transactions.

Incorporating robust security measures like multi-factor authentication (MFA) and end-to-end
encryption.
1
 ABSTRACT
The Bank Management System is a comprehensive software solution designed to streamline
banking operations and enhance customer experience. This system provides distinct
interfaces and functionalities tailored for users, managers, and cashiers. Users can manage
accounts, perform fund transfers, and view transaction history through a user-friendly portal.
Managers are equipped with tools for account management, customer feedback handling, and
new account creation. Cashiers can efficiently retrieve account details for seamless
transaction processing.

By automating key operations such as real-time account management and regulatory

compliance, the system improves operational efficiency, reduces manual workloads, and
ensures data security. Its modular design and role-based access control support scalability and
secure access. The system serves as a reliable platform to meet evolving banking needs,
aligning with customer expectations and industry standards.

2
 COMPARISON OF SOFTWARE DEVELOPMENT
LIFE CYCLE (SDLC) MODELS
Waterfall Model:

Definition: A linear, sequential development approach where each phase must be

completed before moving to the next.
Phases: Requirements → Design → Implementation → Testing → Deployment →
Maintenance.
Strengths:
Clear structure and documentation.
Easy to manage when requirements are well-defined.
Weaknesses:
Inflexible to changes after the project begins.
Delays issue detection as testing occurs late in the cycle.
Use Cases: Ideal for projects with fixed requirements, such as basic banking operations.

3
Agile Model:

Definition: An iterative and incremental approach emphasizing collaboration, adaptability,

and continuous delivery.
Phases: Conducted in short iterations called sprints: Requirements → Design → Development
→ Testing → Review.
Strengths:
Flexible to evolving requirements.
Faster value delivery through regular updates.
Focus on customer satisfaction via stakeholder collaboration.
Weaknesses:
May lack formal documentation.
Requires close coordination and skilled teams.
Use Cases: Best for dynamic projects like mobile banking platforms or AI-driven financial
tools.

4
 CHOSEN MODEL – AGILE:
The report justifies selecting Agile for the following reasons:
Adaptability: Banking regulations and technologies evolve rapidly; Agile
accommodates changes efficiently.

Incremental Delivery: Early delivery of core banking functions (e.g.,

account management) while refining advanced features in later iterations.

Risk Mitigation: Continuous testing reduces compliance risks and bugs.

Customer-Centric: Prioritizes usability for online banking, fund transfers,
and loan management.

5
 REQUIREMENTS GATHERING
1. Significance:
- Aligns development with customer needs, business goals, and regulatory compliance.
- Reduces rework and delays by clarifying expectations early.

2. Techniques:
- Interviews: Insights from bank staff on pain points.
- Surveys: Customer preferences for features.
- Use Cases: Documenting scenarios like secure fund transfers.
- Prototyping: Mock-ups for usability feedback.

3. Example Requirement:
- "The system must enable secure two-factor authenticated transactions."

6
 PROJECT MANAGEMENT METHODOLOGIES
PMBOK (Project Management Body of Knowledge):

Framework: Systematic and comprehensive, ideal for large-scale projects.

Phases:
Initiating: Define scope and stakeholders.
Planning: Detail tasks, allocate resources, and manage risks.
Executing: Assign tasks and ensure quality delivery.
Monitoring: Track progress and address changes.
Closing: Finalize deliverables and conduct reviews.
Example: Develop modules like fraud detection with quality assurance.
PRINCE2 (Projects IN Controlled Environments):

Framework: Process-driven, focuses on governance and control.

Principles:
Phased delivery and structured stages.
Clear roles, responsibilities, and product focus.
Processes: Start, plan, execute, control, and close stages sequentially.
Example: Sequential rollout of modules like loan management and compliance checks.
Application to Bank Management System:

PMBOK Strengths: Effective for managing the complexity of integrating regulatory, security, and user-centric features.
PRINCE2 Strengths: Ideal for clear accountability, phased rollouts, and strong governance. 7
DESIGN AND IMPLEMENTATION
System Design:
Architecture:
Modular Design: Separate modules for account management, loan processing, and compliance checks.
Three-Tier Structure:
Presentation: User interfaces (web and mobile).
Application: Business logic for transactions and fraud detection.
Database: Secure storage for customer and regulatory data.
Security Features:
Data encryption, role-based access control, and multi-factor authentication.
User Interface (UI):
Responsive, accessible, and user-friendly dashboards for customers, managers, and cashiers.
Implementation Phase:

Coding:
Development of modules like fraud detection and account management with adherence to standards.
Integration:
API connections for payment gateways and CRM tools.
Testing:
Unit, integration, system, and user acceptance testing (UAT) ensure functionality and usability.
Deployment: 8
Smooth rollout with training for bank staff and detailed documentation for users.
 RESULTS
Enhanced Functionality:

User Pages:
Features for login, account summary, fund transfers, and transaction history.
Enables users to manage accounts and view statements effortlessly.
Manager Pages:
Tools for account creation, reviewing customer feedback, and accessing branch data.
Cashier Pages:
Streamlines transaction handling by allowing retrieval of account details via account numbers.
Operational Efficiency:

Automated processes reduce manual workloads and errors.

Faster processing for tasks like loan approvals and recurring transaction reminders.
Improved User Experience:

Intuitive and responsive interfaces for both customers and bank staff.
Real-time notifications and seamless integration with digital banking platforms.
9
 User Pages

Manager Pages

10
 CONCLUSION
The project successfully achieved key objectives, including customer satisfaction,
operational efficiency, and regulatory compliance. Core functions such as real-time
account management, fund transfers, and loan processing were automated. The
approach's strengths included the use of Agile methodology, which allowed for
adaptability to evolving requirements, and a phased rollout that facilitated the early
delivery of critical features. Collaboration with experienced vendors ensured robust
security and compliance. Challenges were effectively addressed through improved
feedback mechanisms, which streamlined user testing and iterations, and the use of
data validation tools, which enhanced accuracy during legacy system migration.
Stakeholder involvement played a key role in minimizing overlooked requirements.
Key lessons learned included the importance of early user involvement in
comprehensive requirements gathering, iterative development for delivering user-
focused systems, and the value of structured processes and robust security in
building customer trust and long-term efficiency. 12
THANK YOU