How sonthicse/pmqlsvdh works
Project type and purpose
• This is a desktop “full-stack” application built with .NET 9.0 WinForms (PMQLSVDH stands for a university student‐management tool).
• The user interacts via multiple Forms and UserControls (LoginForm, AdminForm, GiangVienForm, ThemSinhVienForm, etc.).
• It persists data in a local SQLite database file (PMQLSVDH_v2.db).
File structure
• Top-level project artifact: PMQLSVDH.csproj + Program.cs (application entry point).
• UI layer:
• Forms (e.g., LoginForm.cs, AdminForm.cs, GiangVienForm.cs)
• UserControls (e.g., UserControlSinhVien, UserControlLopHoc, UserControlTaiKhoan, etc.)
• Data layer:
• Local DB file (PMQLSVDH_v2.db)
• Implicit or explicit data-access code in code-behind (no separate “DAL” folder, but likely ADO.NET/SQLite calls inside Forms or in helper classes).
• Build/system files: bin/ and obj/ for compiled outputs, .vs/ for IDE metadata.
README
• Contains only the project name; no further architecture details.
• We rely on file names and extensions to infer structure.
Detailed breakdown of components
• UI layer:
• LoginForm, AdminForm, GiangVienForm, ThemSinhVienForm, NavigationControl, various UserControls
• Responsibilities: authentication, CRUD operations for students, teachers, classes, etc.
• Business Logic:
• Validation of input, role checks (Admin vs. Teacher)
• Orchestration of data access calls
• Data Access:
• Classes/methods that open SQLite connections, execute SQL commands, map results to objects
• Database:
• PMQLSVDH_v2.db file storing tables for students, teachers, departments, accounts, etc.
Final advice
• Don’t over-complicate: even if there’s no strict boundary between logic and data-access files, represent them as separate layers for clarity.
• Flows (e.g., “Login → validate credentials → query Accounts table”).