How nhviet03/java_project_restaurantms works
Project type and purpose
• This is a desktop, full-featured “Restaurant Management System” written in Java using JavaSwing for the GUI.
• It follows an MVC-style, layered architecture to manage customers, staff (including warehouse and admin roles), menu, orders, billing, inventory, and reporting.
• It connects to an Oracle database (via JDBC/ojdbc8.jar) for persistent storage and uses external libraries for exporting Excel, PDF, emailing, calendar components, etc.
File structure
• Top-level folders:
• src/RTDRestaurant/Model – domain model classes.
• src/RTDRestaurant/Controller – contains Connection (DatabaseConnection), Event (UI event handlers), Service (business-logic and utility services).
• src/RTDRestaurant/View – JavaSwing UI components, dialogs, forms, and main frames, organized by user role (Customer, Staff, Admin, Warehouse, Login/Register).
• src/DataBase – the Database.sql script.
• src/External_Library – third-party JARs (Excel, PDF, mail, layout, JDBC).
Key insights from README
• Three main user personas: Customer, Staff (including Receptionist, Warehouse, Admin).
• Functional layers: UI (JavaSwing), controllers, services, DB.
• ERD exists: multiple tables for Users, MenuItems, Orders, Invoices, Inventory, etc.
• Uses JDK 17, Oracle database.
Elements
• UI → Controller/Event → Service → DatabaseConnection → Oracle DB
• Service → External Library (for exports/email)
• Models returned back up the chain for rendering in the UI
• Presentation Layer (blue), Controller Layer (green), Service Layer (yellow), Data Access (orange), Database (red), External Libraries (gray)
Final recommendations
• User-role UIs and major feature flows (login, order process, inventory management, reporting).
• Detail the service classes that drive each major functional area (e.g., ServiceAdmin for reporting).
• Refer to the ERD as a separate inset or callout to show database structure in more detail.