How aabdoo23/scheds works
Main Architecture Components
The project follows a Clean Architecture pattern with distinct layers:
• Presentation Layer (Scheds.MVC)
• Application Layer (Scheds.Application)
• Domain Layer (Scheds.Domain)
• Infrastructure Layer (Scheds.Infrastructure)
a) Client-Side Components (Top Layer):
• Web Browser
• Frontend Assets (CSS/JS/Images)
• View Components
• jQuery/Bootstrap
b) Application Layer (Middle Layer):
• MVC Controllers
• View Components
• Service Interfaces
• Repository Interfaces
c) Domain Layer:
• Entities (CourseBase, CourseSchedule, Instructor, CardItem)
• DTOs
• ViewModels
d) Infrastructure Layer (Bottom Layer):
• Database Context (SchedsDbContext)
• Repository Implementations
• Service Implementations
• External Service Integration (Self-Service System)
User Interface → Controllers
• Schedule generation requests
• Course search
• Room availability checks
Controllers → Services
• ICardItemService
• IEmptyRoomsService
• IParsingService
• ISelfServiceLiveFetchService
Services → Repositories
• ICardItemRepository
• ICourseBaseRepository
• ICourseScheduleRepository
• IInstructorRepository
Repositories → Database
• Entity Framework Core operations
• Data persistence
External Integration
• Self-Service Live Fetch connection
• Data synchronization flow
Component Grouping
Related components:
Schedule Generation
• GenerateController
• CardItemService
• CourseScheduleRepository
Room Management
• RoomController
• EmptyRoomsService
• Room-related repositories
Course Management
• CourseBaseController
• CourseScheduleController
• Related services and repositories