How shivam-agarawal/hospital-management-system works
Project type and purpose
• This is a simple, console-based, monolithic Java application called “Hospital Management System.”
• Its purpose is to let users add/view Patients, Doctors, and Appointments via a text-menu interface.
File structure
• All source files live at the root (no frontend/backend split).
• Top-level files:
• HospitalManagementSystem.java (main/menu & logic)
• Patient.java (domain entity)
• Doctor.java (domain entity)
• Appointment.java (domain entity)
• No external config or persistence layer (data is managed in memory).
README for additional insights
• Confirms it’s for beginners to practice OOP and basic data management.
• No mention of a standalone service or external dependencies.
a. Main components
• User Console Interface (UI)
• Application Logic / Controller (in HospitalManagementSystem.java)
• Domain Model (Patient, Doctor, Appointment classes)
• In-Memory Data Store (e.g. Lists or Maps holding instances)
b. Relationships & interactions
• User → UI: enters commands
• UI → Controller: invokes methods (add/view)
• Controller ↔ Domain Model: creates or queries Patient/Doctor/Appointment objects
• Controller ↔ Data Store: inserts or retrieves entities
• Appointment links Patient and Doctor by reference
c. Architectural patterns & principles
• Simplified MVC:
– “View” = console menu
– “Controller” = menu‐driven methods in HospitalManagementSystem.java
– “Model” = domain entities
• OOP: encapsulation of entity data and behaviors
d. Key technologies
• Java (JDK 8+)
• No external frameworks or databases