JEPPIAAR EDUCATIONAL TRUST
JEPPIAAR NAGAR, OLD MAHABALIPURAM ROAD,
SEMMENCHERI, CHENNAI- 600 119.
DEPARTMENT OF INFORMATION TECHNOLOGY
PROJECT REPORT
YEAR: IV
SEMESTER: VII
SUBJECT CODE: NM1117
SUBJECT NAME: FULL STACK WITH JAVA
EXAMINATION: NOVEMBER/ DECEMBER 2025
JEPPIAAR EDUCATIONAL TRUST
JEPPIAAR NAGAR, OLD MAHABALIPURAM ROAD,
SEMMENCHERI, CHENNAI- 600 119.
This is a certified Bonafide record work of DIVINE NANCY D,
Register Number 310822205031 submitted for the Anna University
Practical Examination held on in NM1117- Full
Stack with Java Laboratory during the academic year
2025-2026.
NM1117 – FULL STACK WITH JAVA
Project Created By:
1. BHARATHI S (310822205019)
2. DHANYA E (310822205027)
3. DIVINE NANCY D (310822205031)
4. JOSBA SANTHOSH ANIS J (310822205046)
Project Title: Complaint Management & Grievance Redressal
System
Project Created : 29-10-2025
Table of Content:
Project Objective
Scope
Methodology
Artifacts used
Technical Coverage
Results
Challenges and Resolutions
Conclusion
Certifications
1. Project Objective
The Complaint Management and Grievance Redressal
System is developed to provide an efficient platform where
users can register their complaints, track their progress, and
receive resolutions from administrators in a transparent and
timely manner.
The goal is to reduce manual handling of complaints and
ensure that every grievance is recorded, categorized, and
resolved systematically.
Key objectives include:
• To build an online platform for managing and resolving
complaints.
• To provide transparency and accountability between
complainant and administrator.
• To ensure all grievances are resolved in a timely manner
through a systematic workflow.
• To enhance institutional communication and reduce
workload for administrators.
• To generate reports and insights for monitoring
complaint resolution efficiency.
2. Scope
The system is designed to be a web-based application
that can be accessed by both end users and administrators. It
provides two primary modules:
User Module
• Allows users to register, log in, and submit complaints.
• Each complaint includes details such as category,
description, and date of submission.
• Users can view their complaint history and check
resolution status in real time.
Administrator Module
• Admin can view all submitted complaints, filter them by
category or status, and assign them to responsible
departments.
• Admins can update complaint statuses such as Pending,
In Progress, and Resolved.
• The system also enables administrators to generate
periodic reports for analysis.
System Boundaries
• Focuses on complaint handling within an organization
(college or company).
• Excludes external APIs, AI-based triage, and mobile app
support in the current version.
3. Workflow
The complete workflow of the system follows these major
stages:
1. User Registration & Login
o Users create an account using basic details like
name, email, and password.
o The system validates credentials and maintains
secure sessions.
2. Complaint Submission
o A user fills out a form specifying complaint category
(e.g., academic, infrastructure, service), description,
and attachments if necessary.
o The complaint is saved to the database with a
timestamp and “Pending” status.
3. Complaint Review by Admin
o Admin logs in to the dashboard, views new
complaints, and assigns them to appropriate
departments or personnel.
4. Processing & Updates
o The assigned staff updates the complaint’s progress
as it moves toward resolution.
o Users can track these updates in real time.
5. Resolution & Closure
o Once resolved, the admin updates the status to
“Resolved.”
o Users receive confirmation and can provide
feedback.
6. Reports & Analytics
o The system generates statistical reports showing
total complaints, average resolution time, and
department-wise performance.
4. Methodology
The project follows the Software Development Life Cycle
(SDLC) approach, emphasizing modular development.
Requirement Analysis
• Studied user requirements and institutional complaint
handling workflows.
• Identified core features: complaint submission,
categorization, status tracking, and resolution.
System Design
• Designed architecture diagrams defining client-server
communication using RESTful APIs.
• Database schema includes tables for users, complaints,
and admin.
Development
• Frontend: Developed using HTML, CSS, and JavaScript.
• Backend: Implemented using Java Spring Boot for REST
API development.
• Database: MySQL used for persistent storage.
Testing
• Conducted unit tests on backend endpoints and
integration tests for user–admin interactions.
• Manual testing was done to verify UI responsiveness and
data validation.
Deployment
• Backend deployed on Tomcat Server.
• Frontend hosted using a standard web hosting platform
or local server.
5. Artifacts Used
1. Software Requirement Specification (SRS) — defines all
functional and non-functional requirements.
2. System Design Diagrams — includes use case diagram,
DFD, and ER diagrams.
3. Database Schema — MySQL schema for complaints and
users.
4. API Documentation — endpoints for complaint CRUD
operations.
5. UI Mockups — sample layouts for user and admin
dashboards.
6. Test Case Reports — includes test inputs, expected
results, and actual results.
7. Deployment Guide — details of Tomcat setup and
database configuration.
6. Technical Coverage
Frontend (HTML, CSS, JS)
• Simple and responsive design using HTML5 and CSS3.
• JavaScript used for form validation and dynamic UI
updates.
• AJAX used for asynchronous communication with
backend APIs.
Backend (Java Spring Boot)
• Layered architecture with Controllers, Services,Model
and Repositories.
• RESTful endpoints handle CRUD operations for
complaints.
• Validation and exception handling for robust data
management.
Database (MySQL)
7. Result
• Successfully built a functional web system for complaint
registration and tracking.
• Enabled users to raise issues conveniently and
transparently.
• Reduced manual record keeping and improved
administrative efficiency.
• Achieved smooth data exchange between the frontend
and backend.
• Generated summary reports showing complaint trends
and resolution rates.
8. Challenges and Resolutions
Challenge Resolution
Created a flexible database
Handling multiple complaint
design and dropdown-
categories dynamically
based UI.
Ensuring proper
Configured CORS and tested
synchronization between
REST endpoints thoroughly.
frontend and backend
Used CSS media queries and
Maintaining UI
grid layout for mobile
responsiveness
compatibility.
Implemented transaction
Managing database
management in Spring
consistency
Boot.
9. Conclusion
The project effectively achieves its purpose by
providing a centralized digital solution for complaint and
grievance [Link] ensures transparency,
accountability, and quick resolution by automating the
[Link] integrating modern web technologies with a
robust backend, this project demonstrates strong full-stack
development skills and can be extended for larger
organizations or government services.
10. Future Enhancements
• Multi-language support for accessibility.
• SMS/email notifications for complaint status updates.
• Role-based access (e.g., Department Head, Student
Coordinator).
• Advanced analytics dashboards for administrators.
• AI chatbot to classify and route complaints
automatically.
• Cloud deployment for scalability and 24×7 access.
11. Certifications
Certificate 1:
Certificate 2:
Certificate 3:
