The scenario
A science fair or expo platform needs to register projects by category, assign judges to projects across rounds, collect rubric-based scores, and track winners.
What is in this drawing
Read the decisions behind it.
01
Separated Student and Judge entities from generic User to allow distinct attributes and relationships.
02
Modeled project-student and judging assignments as associative tables to resolve many-to-many relationships.
03
Introduced ScoreDetail to capture per-criterion points, enabling detailed audit trails and weighted scoring.
Use this schema as a baseline for K-12 science fairs, university expos, hackathons, or any multi-round judged event with rubric scoring.
More like this