How tuannta2k/mediplat_prn231_sp25 works
Main Architectural Components
a. Presentation Layer:
• Two client applications:
• Razor Pages UI (MediPlat.RazorPage)
• API Endpoints (MediPlat.API)
b. Business Layer:
• Service Layer (MediPlat.Service)
• Model Layer (MediPlat.Model)
c. Data Access Layer:
• Repository Layer (MediPlat.Repository)
• Database Layer (SQL Server, based on MediPlat_v1.0.sql)
Component Details and Relationships
a. Client Layer (Top):
┌─────────────────────┐ ┌─────────────────────┐
• Razor Pages UI │ │ API Controllers │
• (MediPlat.RazorPage)│ │ (MediPlat.API) │
• ┘ └─────────────────────┘
b. Domain Model (Center):
┌─────────────────────────────────────────┐
• Domain Models │
• AppointmentSlot - Doctor │
• Patient - Review │
• Service - Specialty │
• Subscription - Transaction │
• ┘
c. Data Access (Bottom):
┌─────────────────────┐
• Generic Repository │
• ┘
• ↓
┌─────────────────────┐
• Database Layer │
• ┘
Interaction Flows
• Client → API Controllers
• API Controllers → Services
• Services → Repositories
• Repositories → Database
Additional Elements
a. Cross-Cutting Concerns:
• Authentication/Authorization
• Logging
• Error Handling
b. External Dependencies:
• Bootstrap
• jQuery
• Entity Framework Core
Technical Details to Note
Technical specifications:
• .NET Core framework
• Entity Framework Core
• Docker support (noted by Dockerfile presence)
• RESTful API endpoints
Deployment Context
• Docker container
• Database server
• Web server
Remember to:
• Use consistent spacing and alignment
• Clear labels for all components
• Both synchronous and asynchronous flows
• Primary data flows
• Significant design patterns (Repository Pattern, etc.)