1. System Overview The UasOOP Library Information System is a desktop-based application designed to streamline catalog management and circulation processes within a library environment. Built with a robust Java backend and a relational MySQL database, the system ensures data integrity and high availability. Its primary objective is to replace manual record-keeping with an automated, scalable architecture that tracks book inventory, manages student memberships, and processes daily transactions including automated penalty calculations for overdue returns. 2. Database Schema (ERD Design) The database is normalized to 3NF to eliminate data redundancy. Core tables include: - Users Table: PK: user_id (INT, Auto-increment) Columns: nim_or_id (VARCHAR), full_name (VARCHAR), role (ENUM: 'Librarian', 'Member'), password_hash (VARCHAR). - Books Table: PK: book_id (INT, Auto-increment) Columns: isbn (VARCHAR), title (VARCHAR), author (VARCHAR), stock_quantity (INT), category (VARCHAR). - Transactions Table: PK: transaction_id (INT, Auto-increment) FK: book_id (References Books.book_id) FK: user_id (References Users.user_id) Columns: borrow_date (DATE), due_date (DATE), return_date (DATE, Nullable), penalty_fee (DECIMAL). 3. UML Use Case Architecture Standard UML rules dictate that all actors are external entities interacting with the system. Therefore, the following actors reside strictly outside the system boundary diagram: - Actor: Librarian (External Admin) Use Cases: Manage Book Catalog, Manage Member Data, Override Penalty Fees, Generate Monthly Reports. - Actor: Student / Member (External User) Use Cases: Search Book Catalog, View Borrowing History. - Shared Use Cases (Inside System Boundary): Process Borrow/Return Transaction (Triggered by Librarian on behalf of Member), Calculate Late Penalty (System-triggered include). 4. Component Design The system follows an MVC (Model-View-Controller) architectural pattern organized into logical packages: - uasOOP.models: Contains data entity classes (Book, User, Transaction) and database access logic (DAO pattern). - uasOOP.views: Contains the GUI components (dashboards, forms, tables) for both Librarian and Member interfaces. - uasOOP.controllers: Contains the business logic, input validation, and handles the communication between views and models. - uasOOP.utils: Contains helper classes for MySQL database connection management and date formatting. 5. Implementation Focus - Connectivity: Utilize Java Database Connectivity (JDBC) for seamless and secure communication with the MySQL server, employing PreparedStatement to prevent SQL injection attacks. - User Interface: Implement Java Swing or JavaFX for a responsive, desktop-native user experience. - Error Handling: Ensure comprehensive try-catch blocks around all database queries to prevent application crashes during connection timeouts, providing user-friendly error dialogs.