How vikesh8860/hospital-management-project works
Project type and purpose
• This is a standalone Java desktop application (built in NetBeans) for hospital management.
• It uses Java Swing forms for the user interface and MySQL (via JDBC) as its backend database.
• Key functionality: patient registration, room allocation, billing, medicines/tests management, and employee information management.
File structure
Top‐level files and directories:
• build.xml, nbproject/ – NetBeans project and build scripts
• src/hospital_management/ – all Java source files and NetBeans .form definitions (UI + code)
• Databse_querries.txt – SQL statements used by the app
• dist/ + lib/mysql‑connector*.jar – packaged JAR and JDBC driver
• build/ – compiled classes
Patterns & layers implied:
• Presentation layer: Swing forms (AdminLogin, PatientRegForm, BillGeneration, etc.)
• Business logic: code inside each form class (event handlers, validations)
• Data access: JDBC calls (SQL from Databse_querries.txt) embedded in the form classes or utility methods
• Persistence layer: MySQL database with tables for Patients, Employees, Rooms, Bills, Medicines, Tests
README for additional insights
• Technologies: Java (NetBeans), DBMS: MySQL (WAMP server)
Main components & how to represent them
• Client Application (Java Swing UI)
• Business Logic / Controller layer (event handlers and service methods)
• Data Access component (JDBC driver + SQL queries)
• MySQL Database (tables for Patient, Employee, Room, Bill, Medicine, Test)
• External libraries (mysql‑connector‑java.jar)
b. Relationships & interactions
1. User → Swing UI forms (e.g., Login, Registration, Billing)
2. UI forms → Business Logic (validate input, apply rules)
3. Business Logic → Data Access (execute SQL via JDBC)
4. Data Access → MySQL DB (CRUD operations)
5. Data returns back up through the layers to the UI
c. Architectural patterns & principles
• Layered architecture (Presentation → Business → Data Access → Database)
• Modularization by feature: each form handles its slice of functionality
• Use of NetBeans project structure for clean build and packaging
d. Technologies & frameworks
• Java Swing (javax.swing)
• JDBC (java.sql)
• MySQL (WAMP server)
• NetBeans build scripts (Ant)
Detail without overcomplication
• Break the app into as many logical components as make sense (UI screens, service modules, DAO module, DB).
• Essential elements: user interactions, core modules, data flow, and persistence.