How deathzill/cs151-library-management-system-gamers works
Project Type & Purpose
• This is a full-stack, desktop Java application (Library Management System) with a Swing-based GUI (“frontend”) and core Java classes handling business logic and data persistence (“backend”). It uses Maven for build/dependency management and JSON files for runtime data storage.
File-Structure Analysis
• Top-level:
• src/main/java/frontend → user-interface classes (LibraryUI, custom Exceptions)
• src/main/java/backend → domain model & services (Book, User, Patron, Librarian, Tables, Searchable, Borrowable)
• src/test → unit tests for backend
• src/pom.xml → Maven configuration
• out/artifacts → packaged JAR
• This separation signals an MVC-style layering (UI vs domain logic vs persistence).
README Insights
• Distinguishes “Patron” and “Librarian” user roles.
• Data persistence via JSON.
• Key features: authentication, book management, search/filter, JSON-based database.
• Uses JDK 19, Swing (LibraryUI), Maven.
a. Main Components
1. Frontend/UI Layer
• LibraryUI class (Swing windows, panels, menus)
• Validation Exceptions (email/password rules)
2. Application/Service Layer
• Controllers (LibraryUI calls backend methods)
• Domain objects: User ← Patron/Librarian, Book
• Tables class (manages in-memory collections & JSON I/O)
3. Persistence Layer
• JSON files (books.json, users.json)
• JSON read/write via Tables
4. External/Infrastructure
• Maven build system
• JUnit tests (for backend)
• .jar packaging
b. Relationships & Data Flow
• User interacts with LibraryUI → UI invokes service methods on Tables, Patron, Librarian.
• Tables reads JSON at startup → populates in-memory collections.
• Operations (add/remove/search/checkout/return) update in-memory state → Tables writes JSON on each change or at shutdown.
• Authentication flow: LibraryUI → UserService (in Tables) → validation exceptions → domain creation.
c. Architectural Patterns & Principles
• Layered Architecture (UI → Business Logic → Persistence)
• MVC-style separation (LibraryUI is “View+Controller”, backend domain + Tables are “Model”)
• Single Responsibility (each exception class handles one validation rule).
• Dependency Injection is manual: UI directly instantiates backend objects.
d. Technologies & Frameworks
• Java 19, Swing (AWT)
• Maven (pom.xml)
• JSON (e.g., Gson or Jackson—depending on Tables implementation)
• JUnit 4 for testing