A Library Management Web Application developed using Spring Boot follows the Model-View-Controller (MVC) architecture, where the Model represents the application data, the View provides the user interface, and the Controller handles user requests. Spring Boot simplifies the development process by offering auto-configuration, embedded servers, dependency injection, and seamless integration with databases through Spring Data JPA. The application consists of several modules, including user management, book management, issue and return management, search functionality, and report generation. There are two primary users of the system: the librarian (administrator) and the member (student or faculty). The librarian has privileges to add, update, delete, issue, and receive books, while members can search books, check availability, and view their borrowing history. The application architecture consists of the following layers: Presentation Layer * Developed using Thymeleaf, HTML, CSS, Bootstrap, or JavaScript. * Displays forms for login, registration, book management, and issue/return operations. * Sends HTTP requests to the controller. Controller Layer * Handles incoming HTTP requests. * Maps URLs using annotations such as `@Controller`, `@RestController`, `@GetMapping`, and `@PostMapping`. * Invokes service methods and returns appropriate views or JSON responses. Service Layer * Contains business logic. * Validates user input. * Implements operations such as issuing books only when copies are available and calculating overdue status. Repository Layer * Uses Spring Data JPA repositories. * Performs CRUD operations on the database. * Interacts with entities using interfaces