How tungnguyensnk/projectquanlydancu works
Project type and purpose
• This is a standalone Java desktop application built with JavaFX (FXML + controllers), backed by a MySQL database.
• It manages “nhân khẩu” (population) data, household registrations, complaints/cases (Case1..Case4), health declarations, and daily records.
• It uses external libraries: JDBC (for MySQL), JSON API, Apache POI (for reading/writing .xlsx), and JavaFX.
File structure
• src/com/project1/Main – contains Main.java, controllers (Controller.java, Alert.java, GiaoTiep.java), FXMLs (login.fxml, menu.fxml, alert.fxml).
• src/com/project1/Case1–Case4 – each “Case#” folder holds FXML view files and Java classes (controllers and models) for specific functionality (e.g., ChinhSuaNhanKhau, ToKhaiYTeHangNgay).
• src/com/project1/img + center.css, table.css – resources for UI styling and images.
• META-INF/MANIFEST.MF – packaging metadata.
• Top-level SQL/Excel/Word files (danso.sql, hokhau.xlsx, nhankhau.xlsx, etc.) are data fixtures or templates.
Key insights from README
• Requires JDBC, JSON API, Apache POI, JavaFX libraries on the classpath.
• MySQL database schema is provided in danso.sql.
Components
a. UI Layer (JavaFX)
– FXML view files (login.fxml, menu.fxml, change1.fxml, Case41.fxml, etc.)
– CSS files (center.css, table.css)
– Images (img folder)
b. Controller Layer (MVC Controllers)
– Main controllers (Controller, Alert, GiaoTiep)
– Case-specific controllers (Change1.java, Case41Controller.java, etc.)
c. Service / Business Logic Layer
– Data validation, transformation, JSON processing
– Health-declaration logic (ToKhaiYTeHangNgayGiaoTiep)
d. Data Access Layer (DAO)
– JDBC connector classes (HoKhau.java, NhanKhau.java, LichSH.java)
– CRUD operations to MySQL
e. External Libraries
– JDBC driver (mysql-connector)
– JSON API (parsing/serialization)
– Apache POI (reading/writing .xlsx)
– JavaFX runtime
f. Database
– MySQL (tables for nhân khẩu, hộ khẩu, cases, health logs)
– Schema imported from danso.sql
Relationships and interactions
• UI (FXML) → Controller: user events (clicks, form submissions)
• Controller → Service: business-rule execution, JSON parsing
• Service → DAO: data persistence and retrieval (via JDBC)
• DAO → MySQL: SQL queries, result sets
• Service → Apache POI: import/export Excel data
• Controller → Alert: pop-up dialogs (Alert.java)
• Main → Case modules: navigation (Menu → Case1..Case4 modules)
Architectural patterns
• MVC: FXML views (View), Controller classes (Controller), Model/DAO (Data)
• Layered architecture: UI → Controllers → Services → DAO → Database
• Resource separation: static assets (CSS, images) are in dedicated folders
Essential architectural elements to capture
• The MVC layering and flow from View → Controller → Service → DAO → Database
• How FXML files map to specific Controller classes in each Case module
• The use of Apache POI and JSON API in the Service layer
• The JDBC-based DAO connecting to MySQL tables from danso.sql
• Navigation component (Menu) orchestrating Case1–Case4 modules