Frontend
Frontend
JavaFX desktop interface for menu management, tables, order states, payments, and history views.
Étude de cas
RestManager
Java desktop application for restaurant operations: menu, tables, orders, kitchen workflow, payments, and sales tracking.
Rôle
Java desktop development, persistence modeling, business workflow design, and layered architecture.
- Java
- JavaFX
- Hibernate JPA
- MySQL
- MVC
- DAO
- Service Layer
- Maven
- IntelliJ IDEA
- phpMyAdmin
Contexte
Vue d'ensemble
RestManager focuses on operational restaurant workflows where order status, table activity, payments, and sales tracking must remain consistent.
Problème
Restaurant operations need reliable coordination between menus, tables, orders, payment status, kitchen workflow, and daily sales history.
Objectifs
- Menu, table, order, payment, and sales workflows modeled as restaurant operations.
- MVC, DAO, and service layers separate interface, persistence, and business rules.
- Automatic total calculation and order status workflow support operational consistency.
Solution
Ce qui a été construit
Built a JavaFX desktop application with Hibernate/JPA persistence, MVC structure, DAO and service layers, and business rules for data consistency.
Pourquoi cette approche
The layered Java architecture separates UI, services, DAO persistence, and business rules to keep the desktop application maintainable.
Architecture
Une lecture structurée des blocs techniques et des responsabilités prévues dans le projet.
Backend
Backend
Service layer and DAO structure separating business rules from UI interactions.
Base de données
Base de données
MySQL persistence through Hibernate/JPA with restaurant entities and relationships.
Authentification
Authentification
Authentication is not positioned as the core focus; business workflow consistency is the main concern.
Intégrations
Intégrations
Maven project structure, IntelliJ IDEA development environment, phpMyAdmin, and README demo video.
Défis techniques
- Maintaining order and payment consistency across table workflows.
- Separating business rules from JavaFX interface code.
- Designing persistence with Hibernate/JPA for restaurant entities.
Décisions d'ingénierie
Menu, table, order, payment, and sales workflows modeled as restaurant operations.
MVC, DAO, and service layers separate interface, persistence, and business rules.
Automatic total calculation and order status workflow support operational consistency.
Qualité & tests
La qualité est présentée comme une démarche progressive : tests ciblés, lisibilité, analyse statique et décisions documentées.
Approche de test
The project highlights data consistency through business rules, automatic total calculation, and clear workflow separation.
Maintenabilité et analyse
- Architecture lisible et responsabilités séparées
Résultats
- Demo video is available in the repository README.
- The project demonstrates layered Java desktop architecture with persistence.
- No production deployment or commercial restaurant usage is claimed.
Leçons apprises
Ces apprentissages transforment le projet en preuve de raisonnement technique, pas seulement en liste de fonctionnalités.
- Transformer "Restaurant operations need reliable coordination between menus, tables, orders, payment status, kitchen workflow, and daily sales history." en décisions techniques explicites.
- Présenter les compromis de manière claire pour faciliter la revue par une équipe.
- Relier l'architecture, les tests et la maintenabilité à un problème concret.