How kiroooo-arch/it-faculty-scheduling-system works
This repository describes a planned scheduling product; it does not contain the frontend, backend, or AI-engine source named in the README. The graph therefore represents documented responsibilities and workflow, not verified runtime calls. The database schema is present, but implementation-level connections cannot be established from the available excerpts.
Main entry points: README.md Schedule generation · schema.sql Scheduling database
Components 15
Users and review
- Schedule review and approval
README.md
Scheduling data
- Record management
README.md - Availability
README.md - Curriculum and subjects
README.md - Rooms and labs
README.md
Schedule generation
- Schedule generation
README.md - Conflict detection
README.md - Schedule reports
README.md - Constraint solver
README.md
Planned platform
- Scheduling database
databasse/schema.sql - REST API
README.md - Web application
README.md
Other components
- Administrator
- Department head
- Faculty
Connections 12
- Administrator → Record management: manages
README.md - Administrator → Schedule generation: generates
README.md - Faculty → Availability: submits
README.md - Faculty → Web application: views schedules
README.md - Department head → Schedule review and approval: reviews schedules
README.md - Department head → Conflict detection: monitors
README.md - Schedule generation → Constraint solver: uses constraints
README.md - Constraint solver → Scheduling database: reads scheduling data
- Schedule generation → Conflict detection: detects conflicts
README.md - Schedule generation → Schedule reports: produces schedules
- Web application → REST API: uses REST API
- REST API → Scheduling database: stores records