How omerkurgun/staffmanagementprojects works
Project Type and Purpose
• This is a multi-tier, full-stack ASP.NET staff management system.
• It consists of:
• A UI layer (Web – ASP.NET MVC) for staff and department management pages
• A Web API layer (WebApi – ASP.NET Web API) exposing REST endpoints
• A Business Logic Layer (BLL) encapsulating domain rules and workflows
• A Data Access Layer (DLL) containing entity models and ORM mappings
• A relational database (SQL Server) storing staff, department, city, country and user data
File Structure Analysis
• Top-level solution file: StaffManagementProjects.sln
• BLL/ – Business rules, validation & services (references DLL)
• DLL/ – Entity classes (StaffDBModel, staff, department, city, country, users) – likely Entity Framework models
• Web/ – ASP.NET MVC project with Controllers, Views, client assets (CSS, JS, images)
• WebApi/ – ASP.NET Web API project with controllers under /Controllers and HelpPage area
Key Insights from README
• Both Web and WebApi have an ApplicationSettings.config for:
• ConnectionString (to the SQL database)
• WebApiUrl (Web project calls the API)
• Build/publish instructions – confirms separate deployment targets for Web and API
a. Main Components
1. Client Browser / UI
2. ASP.NET MVC Web App (Web)
3. ASP.NET Web API (WebApi)
4. Business Logic Layer (BLL)
5. Data Access Layer / ORM Models (DLL)
6. SQL Server Database
7. (Optional) Static file store for staff images
b. Relationships & Data Flows
• Browser → HTTP(S) → MVC Controllers (Web)
• MVC Controllers call REST endpoints on WebApi (configured via WebApiUrl)
• WebApi Controllers invoke BLL services
• BLL calls DLL methods/entities to query/update the DB
• DLL interacts with SQL Server via ADO.NET/Entity Framework
• BLL returns DTOs/models → WebApi → JSON → Web UI
• User uploads (e.g., StaffImage) stored on disk or blob storage referenced by Web
c. Architectural Patterns & Principles
• Layered Architecture (Presentation → API → Business → Data)
• Separation of Concerns (UI vs. API vs. BLL vs. DAL)
• Repository/ORM pattern in DLL using EF model classes
• Configuration-driven endpoints and connection strings
d. Technologies & Frameworks
• ASP.NET MVC 5
• ASP.NET Web API 2
• C# .NET Framework projects (DLL, BLL, Web, WebApi)
• Entity Framework (or custom ORM) in DLL
• Client assets: Bootstrap, jQuery, FastClick, FontAwesome