How miguel92245/ekuikui-lab-control works
This is a web system for managing professors, course constraints and institutional resources, then generating practical-class laboratory allocations and reporting conflicts. The main workflow runs from a secretary or professor using the web interface, through backend routes and controllers, to scheduling logic and MySQL; the secretary can preview or persist allocations and inspect results. The graph preserves the documented authentication, professor submissions, resource management and allocation capabilities. Frontend-to-API connections are shown as unverified because the sampled frontend excerpts do not expose their requests.
Main entry points: server.js HTTP server · api.js API client · database.js MySQL connection · professorRoutes.js Professor routes
Components 22
Web interface
- Professor portal
professor.html - Secretariat portal
secretaria.html - Login interface
index.html - API client
js/api.js - Login workflow
js/login.js - Professor workflow
js/professor.js - Secretary workflow
js/secretaria.js
Backend API
- HTTP server
backend/server.js - Authentication routes
backend/routes/authRoutes.js - Login handler
backend/controllers/authController.js - Professor routes
backend/routes/professorRoutes.js - Token validation
backend/middleware/authMiddleware.js - Professor services
backend/controllers/professorController.js
Allocation
- Allocation handler
backend/controllers/alocacaoController.js - Allocation algorithm
backend/utils/alocacaoAlgorithm.js
Persistence
- User records
backend/models/User.js - Professor records
backend/models/Professor.js - Scheduling and resource models
backend/models - MySQL connection
backend/config/database.js - Database schema
database/ekuikui_lab_sql.sql
Other components
- Professor
- Secretariat
Connections 23
- Professor → Professor portal: uses
- Secretariat → Secretariat portal: uses
- Professor portal → Professor workflow: runs
- Secretariat portal → Secretary workflow: runs
- Login interface → Login workflow: runs
- Login workflow → API client: uses
- Professor workflow → API client: uses
- Secretary workflow → API client: uses
- API client → HTTP server: requests
- HTTP server → Authentication routes: mounts
backend/server.js - HTTP server → Professor routes: mounts
backend/server.js - Authentication routes → Login handler: dispatches
backend/routes/authRoutes.js - Login handler → User records: looks up
backend/controllers/authController.js - Professor routes → Token validation: validates with
backend/routes/professorRoutes.js - Professor routes → Professor services: dispatches
backend/routes/professorRoutes.js - Professor services → Scheduling and resource models: reads and writes
backend/controllers/professorController.js - HTTP server → Allocation handler: dispatches
backend/server.js - Allocation handler → Allocation algorithm: generates with
backend/controllers/alocacaoController.js - Allocation handler → MySQL connection: persists and reads
backend/controllers/alocacaoController.js - Allocation algorithm → MySQL connection: reads
backend/utils/alocacaoAlgorithm.js - Professor records → MySQL connection: queries
backend/models/Professor.js - Scheduling and resource models → MySQL connection: queries
backend/models/Professor.js - HTTP server → Professor records: manages
backend/server.js