Lesson Plan

• Describe key components of ER diagrams (entities, attributes, relationships, cardinality, keys).
• Distinguish between conceptual and logical ER diagrams and their purposes.
• Apply a systematic process to create a conceptual ER diagram from requirements.
• Refine the conceptual diagram into a logical ER diagram, adding attributes, foreign keys and normalization.
• Evaluate the completed logical ER diagram for completeness and readiness for database implementation.

• Projector or interactive whiteboard
• Whiteboard and markers
• Student worksheets with sample requirements
• Laptop with ER‑diagram software (e.g., draw.io or Lucidchart)
• Printed handout of ER notation symbols
• Sticky notes for group brainstorming

Begin with a quick poll: Who has seen a database diagram before? Review the purpose of visualising data structures and link to previous lessons on relational databases. Explain that by the end of the lesson students will be able to produce both a conceptual and a logical ER diagram that meets a given brief.

1. Do‑Now (5’) – Students sketch any diagram they recall from earlier lessons; share briefly (checking prior knowledge).
2. Mini‑lecture (10’) – Introduce ER diagram components and differentiate conceptual vs logical models using slides.
3. Guided practice (15’) – Whole class works through steps 1‑5 of the ER creation process using the university example; teacher models on board.
4. Pair activity (15’) – Students create a conceptual ER diagram for a new scenario on sticky notes, then exchange for peer feedback.
5. Logical refinement (15’) – In pairs, add missing attributes, define foreign keys, and discuss normalization; use laptop software to update the diagram.
6. Whole‑class review (5’) – Selected groups present their logical diagrams; teacher highlights common errors and success criteria.
7. Exit ticket (5’) – Students write one key difference between conceptual and logical ERDs and one tip for checking normalization.

Summarise how the step‑by‑step process transforms business requirements into a ready‑to‑implement logical ER diagram. Collect exit tickets to gauge understanding and assign homework: each student must produce a complete logical ER diagram for a simple library system. Remind them to reference the notation guide provided.