How asmit159/library-management-system works
Project type and purpose
• This is a standalone, console-based Java prototype (Library Management System v1.0) focused on practicing OOP, Java Collections (ArrayList, HashMap), and simple user authentication.
• It is not a web or distributed system yet—just a CLI tool with in-memory data storage.
File structure
• Top‐level:
• README.md, LICENSE, .gitignore, docs/ (project paperwork)
• src/ contains only two Java classes:
– Book.java (domain model for book attributes)
– LibraryManager.java (main program; handles console I/O, user authentication, and library operations)
• No DB or persistence layer yet; all data lives in memory via Collections.
• No external config, build scripts, or network services.
README for additional insights
• Features: user roles (admin, student), registration/login, add/show/search books, issue/return operations, availability tracking.
• Tech stack confirms use of Scanner for input, ArrayList/HashMap for storage.
• Future scope mentions file/DB persistence, GUI or web interfaces—points to possible architectural extensions.
a. Main components:
1. UI Layer (Console I/O)
2. Application/Orchestration Layer (LibraryManager.java)
3. Domain Model (Book.java; potential User model)
4. In-Memory Data Store (Collections: ArrayList<Book>, HashMap<User, List<Book>>)
b. Relationships & interactions:
• User (actor) → Console I/O → LibraryManager
• LibraryManager → Domain Services (e.g., authenticateUser(), addBook(), issueBook())
• Services → Data Store (persist into ArrayList/HashMap)
• LibraryManager → Domain Model (create Book instances)
c. Architectural patterns & principles:
• Layered (UI → Service → Domain → Storage)
• Single-Responsibility: Book.java holds only book data; LibraryManager.java orchestrates all workflows (could be refactored into more services later)
• Dependency on Java Collections and Scanner API
d. Key technologies/frameworks:
• Java SE (java.util.Scanner, java.util.ArrayList, java.util.HashMap)
• No external libraries or frameworks