Constraint system / data engineering

Smart Classroom & Timetable Scheduler

A scheduling system that models rooms, faculty, courses, time windows, and conflicts as explicit constraints rather than spreadsheet exceptions.

TypeScriptConstraint modelingData validationFull-stack development
Intent

Why this system exists

Timetables look simple until limited rooms, faculty availability, course requirements, and change requests collide.

Critical decision

What shaped the architecture

Represent hard constraints separately from soft preferences so an impossible schedule can be explained instead of silently degraded.

Architecture / simplified
  1. 01Source data
  2. 02Constraint normalization
  3. 03Candidate slots
  4. 04Conflict checks
  5. 05Published schedule
Reliability work

Designed for imperfect conditions

  • Input validation
  • Conflict trace
  • Deterministic reruns
  • Manual override audit
Constraint set size
Add measured value
Working result

What exists now

  • Structured scheduling rules into inspectable constraints and conflict explanations.
Next pass

What I would improve

Add scenario comparison and measure solve time against larger real-world timetable inputs.