Lesson Plan

• Interpret user requirements to identify the entity and its attributes.
• Select appropriate data types and define a primary key for a single‑table schema.
• Construct and validate a single‑table relational database design that satisfies the given requirements.

• Projector or interactive whiteboard
• Printed worksheet with user requirements
• Laptop computers with a DBMS or spreadsheet software
• Sample data set (e.g., library book list)
• Whiteboard and markers
• Field‑type reference handout

Begin with a quick discussion about how schools track information such as library books, highlighting the need for organized data. Ask students what they already know about tables and records in a database. Explain that by the end of the lesson they will be able to design a complete single‑table database that meets a set of requirements.

1. Do‑now (5 minutes): Students list possible attributes for a library book register on a sticky note.
2. Mini‑lecture (10 minutes): Define a single‑table database, discuss when it is appropriate, and outline the design steps.
3. Guided practice (15 minutes): Walk through the six‑step process using the provided library example, filling a design worksheet together.
4. Independent activity (15 minutes): In pairs, students create a single‑table schema for a new scenario (e.g., cafeteria menu), selecting fields, data types, and a primary key.
5. Peer review (10 minutes): Pairs exchange designs and use a checklist to verify completeness and correctness.
6. Whole‑class debrief (5 minutes): Highlight common errors, answer questions, and reinforce the design checklist.

Summarise the six‑step procedure for translating requirements into a single‑table design and remind students of the importance of a clear primary key. For the exit ticket, each student writes one requirement and its corresponding field name and data type. Homework: design a single‑table database for their personal book collection, including at least five fields.