How sanjoy-kundu/education_management_system works
Main System Components
a) Client Layer
• Frontend components (resources/views)
• Both authentication and main application views
• Component-based architecture using Blade
b) Application Layer
• Controllers (app/Http/Controllers)
• Middleware (app/Http/Middleware)
• Models (app/Models)
c) Database Layer
• Database tables from migrations
• Relationships between models
Architectural Pattern Representation
[Client Tier]
• ↑↓
[Application Tier]
• ↑↓
[Data Tier]
Detailed Component Breakdown
• Blue: Frontend components
• Green: Controllers
• Yellow: Models
• Red: Database tables
• Purple: Middleware
• Gray: Service providers
Specific Components
Frontend Layer:
• Login Component
• Dashboard Component
• Class Management Components
• Subject Management Components
• Exam Schedule Components
• Navigation Components
Controller Layer:
• UserController
• DashboardController
• StudentClassController
• SubjectController
• SubSubjectController
• ExamScheduleController
Model Layer:
• User
• StudentClass
• Subject
• SubSubject
• ExamSchedule
Database Layer:
• users
• student_classes
• subjects
• sub_subjects
• exam_schedules
Additional Elements
Supporting components:
• Authentication flow
• Middleware stack
• Service providers
• Static assets (public/assets)
[Client Browser]
• ↓
[Frontend Components]
• ↓
[Middleware Layer]
• ↓
[Controllers]
• ↓
[Models]
• ↓
[Database]
Technical Details
• Laravel version
• Database type
• Authentication mechanism
• Key dependencies
• Asset compilation flow (Vite)