asif-jutt/messmanagementsystem

Purpose and runtime

This is a .NET 8 ASP.NET Core MVC mess-management system for administrators and members. It manages members, dishes/weekly menus, meal booking and daily records, deposits, rates, bills, and reports. The application entry point is Program.cs; project/runtime definition is Mess_Management_System_Semester_Project.csproj.

Delivery and presentation boundary

HTTP requests are handled by MVC controllers and rendered as Razor pages, with separate administrator and member experiences. Key entry controllers include Controllers/HomeController.cs, Controllers/AdminController.cs, and Controllers/MemberController.cs. Shared layouts define role-oriented shells: Views/Shared/_AdminLayout.cshtml, Views/Shared/_MemberLayout.cshtml, and Views/Shared/_Layout.cshtml.

Identity and access

Authentication is split between administrator/general user and member-facing flows, with protected endpoints and JWT support. Main boundary files are Controllers/AuthController.cs, Controllers/MemberAuthController.cs, Controllers/ProtectedController.cs, plus token abstraction/implementation in Services/IJwtService.cs and Services/JwtService.cs. User identity is represented by Models/User.cs, Models/Admin.cs, and Models/Member.cs.

Persistence model

Models/MessDbContext.cs is the database integration boundary, holding the relational model for operational records. Core persisted entities are members and meals (Models/Member.cs, Models/Meal.cs), financial records (Models/Deposit.cs, Models/Bill.cs, Models/MonthlyBill.cs), and menu/rate data (Models/Dish.cs, Models/WeeklyMenu.cs, Models/MealRate.cs). SQL setup and schema evolution are repository-managed scripts, notably Scripts/CompleteDatabaseSetup.sql and Scripts/UpdateWeeklyMenusSchema.sql.

Meal and menu operations

Administrators manage dishes and weekly menus; members can view menus and book meals, while staff can record daily consumption. Control paths are concentrated in Controllers/DishesController.cs, Controllers/WeeklyMenusController.cs, and Controllers/MealManagementController.cs. The weekly-menu domain is encapsulated further in Services/WeeklyMenuService.cs and represented for UI composition by Models/WeeklyMenuViewModel.cs.

Billing and payment flow

Operational data flows from meal records and meal rates into billing calculations, then to bills/monthly bills and member-visible payment history. Services/IBillingService.cs and Services/BillingService.cs form the explicit billing-calculation boundary. HTTP management/reporting endpoints are in Controllers/BillsController.cs, Controllers/MonthlyBillsController.cs, Controllers/DepositsController.cs, and Controllers/MealRatesController.cs.

Reporting and external surface

Reports draw on persisted meal and financial data, including the database-oriented aggregate model Models/VwDailyMealTotal.cs; reporting routes are in Controllers/ReportsController.cs and Controllers/MonthlyBillsController.cs. There is also a distinct API/chatbot surface through Controllers/ApiController.cs and Controllers/ChatbotController.cs, with corresponding member assistant UI at Views/Member/Assistant.cshtml. The repository contains a Web Deploy publish profile at Properties/PublishProfiles/site48989-WebDeploy.pubxml; the database provider and connection details are expected through appsettings.json / environment-specific settings.