Robust Web-Based Loan Management System

Software Requirements Specification (SRS)
Project Title:
Loan Management System

1. Introduction
1.1 Purpose
This document outlines the Software Requirements Specification (SRS) for the development of a Loan Management System. The system aims to streamline loan application, verification, repayment, and monitoring processes for a financial institution. It is intended to serve three primary user roles—Loan Admin, Loan Officer, and Customer—with additional automation features handled by the system itself.
1.2 Scope
The Loan Management System will be a web-based application that facilitates loan scheme management, customer onboarding, loan application processing, repayment tracking, and report generation. The system will support role-based access and include features such as automated officer assignment and email reminders.
1.3 Intended Audience and Reading Suggestions
 Students/Developers – For understanding the functional and non-functional requirements.
 Project Supervisors – For evaluating design and development progress.
 Testers – For verifying and validating the application against the requirements.
1.4 Definitions, Acronyms, and Abbreviations
 CRUD – Create, Read, Update, Delete
 NPA – Non-Performing Asset
 SRS – Software Requirements Specification

2. Overall Description
2.1 Product Perspective
This is a standalone web-based system designed for educational purposes. It will be modular in structure with clear separation between the front-end, back-end, and database components.
2.2 Product Functions
 User authentication and role-based access
 Loan scheme management (Admin)
 Customer registration and loan application (Customer)
 Document verification and loan approval (Loan Officer)
 Automatic officer assignment (System)
 Email notifications (System)
 Loan repayment tracking and NPA monitoring (Admin, Customer)
2.3 User Classes and Characteristics
 Loan Admin
o Performs CRUD on loan schemes
o Manages loan officers
o Views customer details
o Monitors NPAs
o Generates and views reports
 Loan Officer
o Verifies customer documents
o Handles customer queries
o Approves or rejects loans
 Customer
o Registers and logs in
o Browses loan schemes
o Applies for loans
o Makes repayments
 System
o Auto-assigns loan officers based on customer city
o Sends instalment due email reminders one week in advance
2.4 Operating Environment
 Web-based platform
 Frontend: HTML, CSS, JavaScript (React/Angular optional)
 Backend: ASP.NET
 Database: SQL / PostgreSQL / MongoDB / MySQL
 Email service: SMTP or external API (e.g., SendGrid)
 Payment Service : Pay Pal or Razor Pay
2.5 Design and Implementation Constraints
 Responsive web design
 Authentication required for all user types
 Use of MVC or similar architectural pattern
2.6 Assumptions and Dependencies
 Internet access is available to all users
 Customers provide accurate and verifiable documents
 Loan officers are evenly distributed across service areas

3. Specific Requirements
3.1 Functional Requirements
3.1.1 Loan Admin
 FR1.1: Add, update, delete, and view loan schemes
 FR1.2: Add, update, delete, and view loan officers
 FR1.3: View list of all customers and their loan status
 FR1.4: Monitor NPAs
 FR1.5: Generate loan-related reports
3.1.2 Loan Officer
 FR2.1: View pending loan applications
 FR2.2: Verify uploaded customer documents
 FR2.3: Approve or reject loan applications
 FR2.4: Handle customer queries[
3.1.3 Customer
 FR3.1: Register and login
 FR3.2: View available loan schemes
 FR3.3: Apply for loan by filling form and uploading documents
 FR3.4: Make loan repayments and view repayment history
3.1.4 System (Automated)
 FR4.1: Auto-assign loan officer based on customer city
 FR4.2: Send email reminders one week before loan instalment due date

3.2 Non-Functional Requirements
 Performance Requirements: System should support up to 100 concurrent users.
 Security Requirements: Data encryption for passwords and sensitive data.
 Reliability: 99% uptime for hosted system during the evaluation period.
 Maintainability: Code should be modular and well-documented.
 Usability: Intuitive and user-friendly interface for all roles.


4. External Interface Requirements
4.1 User Interfaces
 Login and Registration Pages
 Role-specific Dashboards
 Forms for Loan Application, Document Upload, Scheme Management
 Admin Reporting Tools
4.2 Hardware Interfaces
 Standard web browsers (Chrome, Firefox, Edge)
4.3 Software Interfaces
 Backend server (ASP.NET Core)
 Relational or SQL database
 Email service (SMTP or API-based)
 Payments – Paypal & Razor Pay

5. Appendix
A.1 Suggested Timeline (8–12 weeks)
1. Week 1-2: Requirement gathering and planning
2. Week 3-5: Frontend and backend development
3. Week 6-7: Integration and system testing
4. Week 8: Final testing and documentation