Lesson Plan

Resources → Subject Notes → Computer Science → Notes
Lesson Plan
Grade: Date: 25/02/2026
Subject: Computer Science
Lesson Topic: Produce a normalised database design for a description of a database, a given set of data, or a given set of tables
Learning Objective/s:
  • Describe the key concepts of functional dependencies and the normal forms (1NF, 2NF, 3NF, BCNF).
  • Apply a step‑by‑step procedure to transform an un‑normalized table into a normalized design up to BCNF.
  • Construct primary‑key and foreign‑key definitions for the resulting tables and produce a simple ER diagram.
  • Evaluate common pitfalls and justify design choices in a normalized schema.
Materials Needed:
  • Projector and screen
  • Whiteboard and markers
  • Student worksheets with un‑normalized data examples
  • Laptop with DBMS or spreadsheet software for demonstration
  • Printed handout of normalization steps and functional‑dependency checklist
 Introduction:
Begin with a quick recall of what a database and a table are, then pose the question: how can we organise data to avoid redundancy? Students review key terminology and see a real‑world student‑course registration example. By the end of the lesson they will know how to produce a fully normalised schema and explain their design choices.
Lesson Structure:
  1. Do‑now (5') – Students list examples of data redundancy they have observed.
  2. Mini‑lecture (10') – Review of PK, FK, FD and the four normal forms with slide examples.
  3. Guided walkthrough (15') – Teacher demonstrates the step‑by‑step normalisation of the registration table, checking each normal form.
  4. Pair activity (15') – Students normalise the library‑loans table on a worksheet, identifying functional dependencies and creating tables.
  5. Whole‑class debrief (10') – Groups share designs; teacher highlights common pitfalls and confirms BCNF compliance.
  6. Exit ticket (5') – Students write one sentence describing the most important insight or next step for improving a design.
Conclusion:
Summarise how each normal form eliminates specific redundancy and strengthens data integrity. Students complete an exit ticket stating their key takeaway, and for homework they will normalise a new dataset posted on the class portal.