How manula-sameera/university-management-system works
Project type and purpose
• This is a “University Management System” written as a Windows-Forms desktop application in C#.
• It provides CRUD management of campuses, departments, courses, students, faculty, fees, salaries, reports, and user authentication (Login/Signup).
File structure
• Top level:
• University Management System.sln / .csproj – Visual Studio solution and project files
• Program.cs – application entry point
• *.Designer.cs + *.cs + *.resx – one folderless WinForms form per entity (Campus, Department, Courses, Student, Faculty, Fees, Salaries, Reports, Login, Signup, Menu, Home, etc.)
• UniversityDataBase.mdf / .ldf – local SQL Server database files
• App.config – connection strings and settings
• Properties – assembly info, resources, settings
• CODE_OF_CONDUCT.md, CONTRIBUTING.md, README.md – repo governance
• No separate “backend” or “API” folder; data access is embedded in code-behind of forms (ADO.NET or typed DataSet from the MDF file).
Key insights from README
• (Empty in this repo) → rely solely on file tree to infer architecture.
a. Presentation Layer (WinForms UI)
• Each form: Login/Signup → Main Menu → Home → Domain forms (Student, Faculty, Courses, Department, Campus, Fees, Salaries, Reports, DialogBox).
• Program.cs launches Login, then hands off to the Menu form.
b. Business/Data Access Layer
• Classes and methods in code-behind (.cs) files handling button clicks, validation, queries (ADO.NET commands, TableAdapters, DataSets).
c. Database Layer
• UniversityDataBase.mdf – SQL Server LocalDB database containing tables for Students, Faculty, Courses, Departments, Fees, Salaries, etc.
d. Configuration
• App.config – connection string connecting the UI/data-access code to the local MDF file.
Relationships and interactions
• User interacts with WinForms UI → UI invokes data-access calls in code-behind → data-access layer opens SQL connection to the MDF → CRUD operations on tables → results returned to UI → UI updates controls.
• Program.cs → Login form → on success → Menu form → navigation to various modules.
Important architectural patterns / principles
• Monolithic 3-tier style (Presentation / Data Access / Database)
• UI tightly coupled to data-access (no separate service layer or API)
• Typed DataSets or direct ADO.NET usage for data binding
Technologies / frameworks
• Microsoft .NET Framework (WinForms)
• ADO.NET or Typed DataSets
• SQL Server LocalDB (MDF file)
• Visual Studio solution/project
Final checklist
• Clear labels for each component (forms, layers, DB)
• A note callout for App.config’s connection string
• Related forms into functional modules (e.g., “Student Management” group: StudentForm, FeesForm, ReportsForm)