How lunks41/aemsweb works
Main Components
• Authentication & Access Control: Represent components responsible for branch-wise logins and role-based permissions. This includes controllers and models in the Account area (e.g., AccountController.cs, Login views, and associated models).
• Dashboard & Navigation: A centralized dashboard that manages branch selection; include the NavigationViewComponent and DashboardControllers (like Controllers/DashboardController.cs and Views in the Shared/Dashboard folder).
– Master Module (under Areas/Master): Handles core entities like Customers, Suppliers, Banks, and Accounts.
– Account Module (under Areas/Account): Manages financial transactions including invoicing, receipts, adjustments, etc.
– HRMS Module (under Areas/HRM): Manages employee records, attendance, payroll, etc.
– Admin Module (under Areas/Admin): Covers system-wide administration features like user and role management, audit logs, and document numbering.
– Project Module (under Areas/Project): Manages job orders, quotations, tariffs, and project workflows.
– Setting Module (under Areas/Setting): For configurations and preferences.
• Data & Persistence Layers: Include the Data folder (e.g., Data/AppDbContext.cs), Entities (the detailed hierarchical folders for Accounts, Masters, Project, etc.) and the Repository/Services layers. This represents the business logic and data access layers.
• External Libraries & Assets: The wwwroot folder, which contains CSS, JavaScript, images, and third-party libraries (Bootstrap, jQuery, Kendo UI), should be depicted as part of the Frontend/UI/Resources.
Layers and their Relationships
• Presentation Layer (Web / UI): ASP.NET MVC controllers (located in top-level Controllers and within each Area), Views (cshtml files in each module's Views folders), and ViewModels (in the ViewModels folder).
• Business Logic & Service Layer: Services (under Services and its subdirectories), Repository pattern implementations (Repository folder), and Data Access (Data and Entities folders).
• Data Persistence Layer: Database interactions through AppDbContext and Entity Framework with models in the Entities folder.
• Infrastructure: Supporting components such as Helpers, Extensions, and Hubs (e.g., NotificationHub.cs) that allow real-time communication and utility operations.
• Configuration & Deployment: Configuration files (appsettings.json, launchSettings.json) and solution/project files (.sln, .csproj) are also worth noting.
• For a full-stack application like this one, clearly separate the web front-end (controllers/views) from the business logic and data access layers.
• Branch selection and role-based access control by adding annotations describing that each module’s operations are filtered using branch-specific identifiers and user roles.
• Optionally, use rounded rectangles for modules and standard rectangles for lower-level services.