Student Management System — Java Programming

Project Overview

The Student Management System is a complete Java Spring Boot application that manages student records, course enrollments, grade tracking, attendance management, and academic report generation. It implements full CRUD operations with a clean layered architecture (Controller → Service → Repository) and provides both REST API access and an optional Thymeleaf-based web UI.

This project is ideal for:

• Java beginners building their first Spring Boot project
• Students learning CRUD operations with JPA/Hibernate
• Developers preparing for Java developer interviews with hands-on code
• Anyone wanting to understand the complete request-response lifecycle in Spring Boot

The system manages multiple entities (Students, Courses, Enrollments, Grades, Attendance) with proper relationships, implements comprehensive search and filtering, and generates PDF report cards with GPA calculation.

Features

1. Student Registration — Register students with personal info, contact details, and photo
2. Course Management — Create and manage courses with credits, department, and prerequisites
3. Course Enrollment — Enroll students in courses with semester tracking
4. Grade Management — Record grades for assignments, midterms, and finals
5. GPA Calculation — Automatic CGPA/SGPA calculation based on grade points and credits
6. Attendance Tracking — Daily attendance marking with percentage calculation
7. Search & Filter — Search students by name, ID, department, or enrollment year
8. Pagination & Sorting — Efficient listing with configurable page size and sort options
9. Report Card Generation — PDF report cards with grades, GPA, and attendance
10. Batch Operations — Bulk student import from CSV/Excel
11. Dashboard — Overview with total students, department distribution, top performers
12. Semester Management — Track academic semesters and year progression
13. Fee Management — Track fee payment status per semester
14. Parent/Guardian Info — Store emergency contact and guardian details
15. Document Upload — Upload student photo, ID proof, and certificates
16. Email Notifications — Registration confirmation, grade published alerts
17. Export Data — Export student list as Excel or CSV
18. Validation — Comprehensive input validation with meaningful error messages
19. Audit Trail — Track record modifications with timestamps
20. Role-Based Views — Admin (full access), Faculty (grades/attendance), Student (view own)

Project Structure

Database Schema

students Table

courses Table

enrollments Table

grades Table

attendance Table

Entity Relationships

Key Code Snippets

Student Entity

Student Service Implementation

GPA Calculator Service

Student Controller

Student Repository

API Endpoints

How to Run

Setup Steps

Step 1: Create MySQL database

Step 2: Configure application.yml

Step 3: Build and run

Step 4: Access

• REST API: http://localhost:8080/api/v1
• Swagger UI: http://localhost:8080/swagger-ui.html
• Web UI: http://localhost:8080/students (Thymeleaf)

Screenshots Description

1. Student List — Table with roll number, name, department, semester, CGPA with pagination
2. Registration Form — Student creation form with validation error messages
3. Student Profile — Complete student details with enrolled courses and attendance
4. Grade Sheet — Semester-wise grades table with GPA calculation
5. Report Card PDF — Generated PDF with student info, grades, and CGPA
6. Dashboard — Pie chart (department distribution), bar chart (CGPA ranges), stats cards
7. Attendance Report — Calendar view showing present/absent days with percentage

Future Enhancements

1. Online Exam Module — MCQ-based exams with auto-grading
2. Timetable Management — Class schedule generation with conflict detection
3. Placement Portal — Company registrations, student applications, interview scheduling
4. Hostel Management — Room allocation and mess management
5. Library Integration — Connect with library management for book borrowing
6. Parent Portal — Guardian login to view child's progress
7. Mobile App — Student app for attendance, grades, and notifications
8. Analytics — Predictive analytics for at-risk students (low attendance/grades)
9. Alumni Network — Graduate tracking and networking
10. Multi-institution — SaaS model supporting multiple colleges

Interview Questions

Q1: How does the GPA calculation work in this system?

Answer: CGPA uses the formula: Σ(Grade Point × Credits) / Σ(Credits). Each course has a credit value (1-5). When grades are entered, the system converts percentage marks to grade points (A+=10, A=9, B+=8, etc.) and calculates the weighted average. SGPA is per-semester, CGPA is cumulative across all semesters. The GpaCalculatorService fetches all completed enrollments with grades, multiplies each grade point by course credits, sums them, and divides by total credits.

Q2: How do you handle the relationship between Student, Course, and Grade?

Answer: It's a many-to-many relationship between Student and Course, resolved via the Enrollment junction entity. Each enrollment has exactly one Grade (OneToOne). This design allows: tracking enrollment status (enrolled/completed/dropped), storing semester context, and linking grades to specific student-course-semester combinations. We don't put grades directly on the student or course table to maintain normalization.

Q3: Why use pagination instead of returning all records?

Answer: With thousands of students, returning all records in one response causes: (1) High memory usage on the server (loading all entities from DB), (2) Large JSON response increasing network transfer time, (3) Client-side rendering performance issues. Pagination with PageRequest.of(page, size) generates SQL LIMIT/OFFSET, loading only the requested page. The response includes metadata (totalElements, totalPages, hasNext) for the client to build navigation.

Q4: How do you generate the roll number?

Answer: The RollNumberGenerator creates a unique ID using: Department code (2 chars) + Admission Year (4 digits) + Sequential number (3 digits). Example: CS2024001. It queries the max existing roll number for that department and year, extracts the sequence, increments it, and formats with leading zeros. Thread safety is ensured using @Synchronized or database sequence. The format makes it easy to identify a student's department and admission year.

Q5: How would you implement bulk student import from Excel?

Answer: (1) Controller accepts MultipartFile, (2) Use Apache POI to read each row, (3) Map columns to StudentDTO, validate each record (email format, required fields, no duplicates), (4) Collect valid records and errors separately, (5) Save valid students in batch using saveAll() with hibernate.jdbc.batch_size=50, (6) Return response: {success: 95, failed: 5, errors: [{row: 12, message: "Invalid email"}]}. We process in a single transaction with rollback only for critical errors.