How developmentt910/quanlysinhvien works
Project type and purpose
• This is a desktop, full-stack (client + local database) student-management application built on .NET (C# WinForms).
• The README calls out four main folders—DuLieu (data access), LopDoiTuong (domain objects), GiaoDien (UI forms), TienIch (utility code)—plus the entry point (Program.cs) and configuration (App.config).
File structure
Top-level items:
• Program.cs / App.config – application entry point & configuration
• DuLieu/ – Data Access Layer (DAL) classes
• LopDoiTuong/ – Domain Model classes (Student, Course, etc.)
• GiaoDien/ – Presentation Layer (WinForms UI)
• TienIch/ – Helpers & utilities (logging, validation, common routines)
• Properties/ and *.csproj/*.sln – Visual Studio metadata
README insights
• Mentions a three-layer separation: data access, domain objects, UI.
Main components and their roles
a. Presentation Layer (GiaoDien)
– WinForms UI Forms (AddStudentForm, EditCourseForm, MainDashboard)
– References Domain and Utilities
b. Domain Layer (LopDoiTuong)
– POCO classes: SinhVien, MonHoc, Enrollment, etc.
– Encapsulate business rules and object state
c. Data Access Layer (DuLieu)
– Repository or DAO classes: StudentRepository, CourseRepository
– Implements CRUD operations against the database (via ADO.NET / Entity Framework)
d. Utility Layer (TienIch)
– Static helper classes: ValidationHelper, Logger, ConfigurationManager
e. External Database
– SQL Server or local DB (specified in App.config connection string)
Relationships and interactions
• UI calls into Domain objects (e.g., create a SinhVien instance), then invokes Data Access methods to persist or retrieve data.
• Data Access uses App.config settings to connect to the database.
• Utility classes are used by all layers for logging, string formatting, validation, etc.
Architectural patterns & principles
• Three-tier architecture (Presentation / Domain / Data Access).
• Separation of concerns: each layer has its own responsibility.
• Dependency direction: UI → Domain → DAL → Database.
• Single Responsibility: each class or form has a focused role.
• Config-driven connection strings (App.config).