Lesson Plan

• Describe 1NF, 2NF and 3NF and explain why each reduces redundancy.
• Identify functional, partial and transitive dependencies in a relation.
• Apply a step‑by‑step process to transform an unnormalised table into 3NF.
• Evaluate a set of tables against the 3NF checklist.
• Produce a short ER diagram showing the final 3NF tables and relationships.

• Projector and screen
• Laptop with a relational DBMS (e.g., MySQL Workbench)
• Printed handouts of the sample Student‑Course table
• Worksheet containing the Order table normalisation exercise
• Whiteboard and markers
• Sticky notes for exit tickets

Begin with a quick poll: “What problems arise when the same data is stored in many places?” Connect this to the previous lesson on relational databases and remind students of primary keys. Explain that today they will learn how to systematically eliminate those problems and will be able to check their work against a clear 3NF checklist.

1. Do‑now (5'): Quick quiz on definitions of 1NF, 2NF and functional dependencies (paper).
2. Mini‑lecture (10'): Review of keys, functional, partial and transitive dependencies with short examples.
3. Guided practice (15'): Walk through normalising the Student‑Course registration table to 3NF, projecting each step on the screen.
4. Pair activity (15'): Students normalise the provided Order table, complete the worksheet, and identify all dependencies.
5. Whole‑class debrief (10'): Groups share their decompositions; teacher highlights the 3NF checklist.
6. Exit ticket (5'): Each student writes one condition that must be met for a table to be in 3NF.

Summarise how moving from 1NF to 3NF removes redundancy and improves data integrity. Collect exit tickets to gauge understanding, and assign homework: normalise a new unnormalised sales table and produce a brief ER diagram of the final 3NF design.