Lesson Plan

Resources → Subject Notes → Information Technology IT → Notes
Lesson Plan
Grade: Date: 17/01/2026
Subject: Information Technology IT
Lesson Topic: Understand database relationships (one-to-one, one-to-many)
Learning Objective/s:
  • Describe the purpose of database relationships and differentiate one-to-one and one-to-many types.
  • Explain how primary and foreign keys enforce one-to-one and one-to-many relationships.
  • Apply crow’s‑foot notation to model these relationships in an ER diagram.
  • Write basic SQL statements to create tables that implement one-to-one and one-to-many relationships.
  • Evaluate design choices when deciding between one-to-one and one-to-many structures.
Materials Needed:
  • Projector or interactive whiteboard
  • Laptop with database software (e.g., MySQL Workbench)
  • Printed handout of ER diagram examples
  • Sample SQL script worksheets
  • Whiteboard and markers
  • Student laptops (optional)
 Introduction:
Begin with a quick question: “Where have you seen data linked together in everyday life?” Connect this to prior knowledge of tables and keys, and state that by the end of the lesson students will be able to identify and create one-to-one and one-to-many relationships.
Lesson Structure:
  1. Do‑now (5’) – Students list everyday examples of linked data and share with the class.
  2. Mini‑lecture (10’) – Define database relationships, cardinality, and why they matter.
  3. Guided demo (12’) – Show ER‑diagram crow’s‑foot notation and build a one-to-one relationship in SQL.
  4. Pair activity (15’) – Using a worksheet, students create a one-to-many relationship (Department ↔ Employee) and write the corresponding SQL.
  5. Check for understanding (8’) – Quick quiz or Kahoot with scenario questions; teacher reviews answers.
  6. Recap & reflection (5’) – Teacher summarises key differences; students note one remaining question.
Conclusion:
Review the main distinctions between one-to-one and one-to-many relationships and how they are implemented with keys. Students complete an exit ticket describing which relationship fits a given scenario. For homework, they design an ER diagram for a simple library database that incorporates both relationship types.