NEW HALL INTERNATIONAL SCHOOL LEKKI LAGOS

LESSON PLAN

WEEK: 2 TERM: THIRD Second SESSION: 2025/2026

SUBJECT: DIGITAL TECHNOLOGIES CLASS: YEAR 10

________________________ LESSON 1 Hour

DATE:
PERIOD:

TOPIC: Database Introduction

SUB-TOPICS: 1. Concept of a Database | 2. DBMS | 3. Tables | 4. Records | 5. Fields

Students are asked: "Think of your school's student registration system — how do
you think your name, class, and date of birth are stored and retrieved so
quickly?"
INTRODUCTION:
Students respond in pairs (think-pair-share). This grounds the lesson in a familiar
school context and reveals existing mental models about organised data storage before
formal concepts are introduced.

Learning Objectives Vocabulary

At the end of the lesson, students should be able to: • Database
• Define a database and explain why structured data • DBMS (Database Management System)
storage is essential in real-world systems. • Table
• Describe the role and importance of a Database • Record (Row)
Management System (DBMS) with real examples. • Field (Column)
• Distinguish between tables, records, and fields, and • Primary Key
explain how they relate to each other. • Data Type
• Design a simple database table with appropriate • Query
fields for a given real-life scenario.
• Flat File
• Analyse the advantages of using a database over
• Relational Database
flat-file storage such as spreadsheets.
• Entity
• Attribute
Study Questions:
1. What is a database and why do organisations use
them?
2. What does a DBMS do, and name two real-world
examples.
3. What is the difference between a field, a record,
and a table?
4. Design a table with appropriate fields for a school
library system.
5. Why is a database more efficient than keeping
records in a notebook or spreadsheet?
Teaching Materials: Previous Learning:
• Projector / Smart Board Students have previously covered digital storage
• Printed 'Student Record Card' activity sheet types, spreadsheets as flat-file data tools, and the
(paper-based database simulation) concept of data vs. information. They understand that
• Whiteboard for live table-building exercise computers store and retrieve data, but have not yet
• Sample database screenshots (Google explored structured, relational data organisation.
Sheets vs. MS Access comparison)
• Scenario cards for design activity
• Short video: 'What is a Database?' (3 min, CS
simplified)

Learning Activities (Step-by-Step) Timing

STEP 1: Hook & Prior Knowledge — The Paper Register Problem

Teacher presents a scenario: "Your school has 1,500 students. Every
morning, the secretary writes attendance in a paper register. A student
transfers classes — three registers must be updated by hand. A student's
10 mins
name is misspelled in one register but correct in another. Who is right?"
Students discuss the chaos this creates.
Teacher then reveals: 'This is exactly the problem databases solve.' Students
record their initial definition of a database.

STEP 2: Direct Instruction — Concept of a Database & DBMS

Teacher defines a database and introduces the DBMS using the school
registration system as a running analogy throughout.
• Database: An organised, structured collection of related data stored
and accessed electronically — like a digital filing cabinet with rules.
• DBMS: The software that creates, manages, and controls access to
the database. Examples: Microsoft Access (school use), MySQL (web 12 mins
apps), Oracle (banking), SQLite (mobile apps).
• Real examples: ATM transactions (banking DB), hospital patient
records, supermarket stock systems, social media user profiles.
Teacher plays the 3-minute video, then checks understanding with whole-
class Q&A: 'What is the DBMS doing in the video? Could you do the same in
a spreadsheet? Why not?'

STEP 3: Interactive Instruction — Tables, Records & Fields (Live Build)

Teacher builds a database table LIVE on the whiteboard using student
volunteers as data. The class becomes the database.
Live Example — Student Table:
• Fields (Columns): StudentID | FirstName | Surname | Class |
DateOfBirth | PhoneNumber
• Record (Row): Each student volunteer calls out their details — one
full row = one record about one entity (one student).
15 mins
• Table: The entire grid of all students = the table.
• Primary Key: StudentID — uniquely identifies each record. No two
students share it.
Teacher asks analytical questions: 'What happens if we don't have a
StudentID and two students are named Emeka Okafor? How does the system
know which record to update?' This demonstrates WHY primary keys are
logically necessary.
Students copy the table structure into their notes, labelling each component.

STEP 4: Practical Activity — Design a Database Table 15 mins

Students work in pairs. Each pair receives a scenario card and must design
an appropriate database table on their worksheet — naming the table,
identifying all necessary fields, choosing data types, and selecting a primary
key.
Scenario cards:
◦ A Lagos pharmacy tracking medicine stock (name, quantity, expiry
date, supplier, price).
◦ A school library tracking borrowed books (book title, ISBN, borrower
name, borrow date, return date).
◦ A food delivery company tracking orders (order ID, customer name,
meal, delivery address, status).
◦ A football club tracking player statistics (player ID, name, position,
goals scored, matches played).
Pairs share their field choices. Class votes on whether each chosen field is
'necessary', 'useful', or 'redundant' — sparking analytical debate about what
data is actually worth storing.

STEP 5: Consolidation — Summary, Comparison & Evaluation

Teacher draws a comparison on the board: Paper Register vs. Spreadsheet
vs. Database. Students contribute the advantages of each. Teacher
highlights: databases enforce data integrity, allow simultaneous multi-user 8 mins
access, support queries (search/filter), and scale to millions of records.
Students then answer three written evaluation questions independently before
dismissal.

LESSON CONTENT

1. Concept of a Database
A database is an organised collection of structured, related data that can be easily accessed, managed, and
updated. Unlike a random collection of files or a notebook, a database stores data in a controlled format that
allows fast, reliable retrieval and prevents unnecessary repetition.
Consider a bank: thousands of customers, millions of transactions per day. A database allows the bank's system
to retrieve the exact balance of one specific customer in milliseconds — something impossible with paper-based
filing or simple spreadsheets at that scale.
Why databases matter in real life:
• JAMB/WAEC results systems — storing and retrieving millions of candidate results accurately.
• Hospital patient management — one patient record accessible to doctors, nurses, and pharmacists
simultaneously.
• E-commerce platforms — tracking products, customers, and orders in real time.
• Social media — storing billions of posts, likes, and user profiles with instant search.
2. Database Management System (DBMS)
A DBMS is software that acts as an interface between the user and the database. It controls how data is stored,
organised, retrieved, updated, and secured. Without a DBMS, raw data stored on disk would be inaccessible to
most users.
Key functions of a DBMS:
• Data storage management: Organises data efficiently on physical storage media.
• Data retrieval: Allows users to query (search/filter) data using structured commands.
• Access control: Determines who can view, edit, or delete specific data (e.g., students cannot edit their
own exam results).
• Data integrity: Enforces rules to prevent invalid or inconsistent data entry (e.g., a date field cannot hold a
name).
• Backup and recovery: Protects data against loss through automated backup systems.
Real-world DBMS examples:
• Microsoft Access — common in schools and small businesses.
 • MySQL — powers most websites (e.g., WordPress blogs, online stores).
• Oracle Database — used by banks, airlines, and large enterprises.
• SQLite — lightweight database built into smartphones and apps.
3. Tables
A table is the fundamental structure of a relational database. It organises data into rows and columns — similar
in appearance to a spreadsheet, but with strict rules about what each column represents and what type of data it
can hold.
A database is typically made up of multiple related tables. For example, a school database might have a
Students table, a Classes table, and a Teachers table — all linked together.
Example — Students Table:
StudentID FirstName Surname Class DateOfBirth

S001 Chioma Adeyemi 11A 12/03/2008

S002 Emeka Okafor 11B 07/09/2007

S003 Fatima Bello 11A 22/11/2008

4. Records
A record is a single horizontal row in a table. It contains all the data about one specific entity (person, object,
transaction, etc.). Every field in a record relates to the same subject.
In the Students table above, the row for Chioma Adeyemi is one record. It holds every piece of information the
database stores about that one student. If you were to print out just that one row, you would have a complete
digital profile for Chioma.
Key properties of a record:
• Each record is uniquely identified by a Primary Key (e.g., StudentID = S001).
• All fields in a record belong to the same entity — you would not mix Chioma's name with Emeka's date
of birth.
• Records can be added, deleted, or updated without affecting other records.
Real-life analogy: A record is like one patient's medical file in a hospital — it holds everything about that one
patient. The filing cabinet holding all patients' files is the table.
5. Fields
A field is a single vertical column in a table. It represents one specific attribute (characteristic) that is stored for
every record. Every field has a name and a data type that constrains what values can be entered.
Common data types for fields:
• Text / VARCHAR: Stores letters and characters — e.g., FirstName, Surname.
• Integer / Number: Stores whole numbers — e.g., Age, GoalsScored.
• Date/Time: Stores date and time values — e.g., DateOfBirth, OrderDate.
• Boolean / Yes/No: Stores true or false — e.g., IsEnrolled, HasPaid.
• Currency / Decimal: Stores monetary values — e.g., Price, Salary.
Why field design matters:
Poor field design causes problems. If a developer stores a phone number as an Integer (number), the leading
zero is dropped — '08012345678' becomes '8012345678'. Storing it as Text preserves the full number. Every
field decision has logical consequences that affect data quality.
Primary Key:
One field (or a combination) in each table is designated as the Primary Key — a unique identifier for every
record. No two records can share the same primary key value, and it cannot be left blank (null). This is what
allows the DBMS to locate, update, or delete the exact correct record every time.

EXTEND (High Challenge Task:

Flyers): A Lagos general hospital currently stores all patient data in paper files. Critically evaluate
 the move to a DBMS-managed relational database. In your response: (1) design TWO
related tables (Patient and Appointment) with appropriate fields, data types, and primary
keys; (2) identify a field that could link both tables together; (3) explain TWO risks of the
transition and how they could be mitigated. Use correct database terminology throughout.

Differentiation: Resources:
• Level 1 (80–100%): Students design multi- • Cambridge IGCSE Computer Science
table structures, justify field choices including Textbook — Chapter: Databases
data types, and identify primary keys with full • BBC Bitesize — Databases & Data Structures
reasoning. • Microsoft Access Tutorial (YouTube —
• Level 2 (60–79%): Students correctly identify Beginner)
fields, records, and tables in given examples • W3Schools — SQL Introduction (extension
and can design a simple single-table database reading)
with guidance. • Teacher-prepared scenario cards and design
• Level 3 (50–59%): Students match definitions worksheets
to terms and label the components of a pre-
built table using the worksheet with teacher
support.

Evaluation Questions: Key Skills Developed:

6. Define a database and explain ONE way it is • Analytical thinking — evaluating appropriate
superior to storing data in a paper register. field choices and data types
7. Look at this record: [S002 | Emeka | Okafor | • Logical reasoning — understanding why
11B | 07/09/2007]. Identify the Primary Key primary keys are structurally essential
and explain why it is necessary. • Design skills — structuring a database table
8. A supermarket wants to build a database to for a real-world need
track its products. List FOUR fields that the • Collaborative learning — pair design activity
Products table should contain, and for each and peer critique
field, state the appropriate data type. • Digital literacy — understanding how everyday
systems (banking, hospitals, schools) use
databases

FEEDBACK ON CLASS PERFORMANCE

(To what extent did we achieve our purpose?)

1. Class displayed understanding of the topic taught:
(a) Yes (b) No Exceptions: ___________________________________
2. Comments on completion of previous week's assignment by students:
(a) Well (b) Average (c) Poor
3. Exceptions: _____________________________________________________________________________
4. Any follow-up action: ____________________________________________________________________

Choose ONE of the following organisations: (a) a school canteen, (b) a petrol station, or (c)
a hotel in Abuja. Design a database for your chosen organisation. Your answer must
include: (1) the name of the database table, (2) at least six appropriate fields with field
ASSIGNMENT:
names and data types, (3) identification of the Primary Key and justification for your choice,
and (4) two sample records completed in full. Present your table neatly in a drawn grid
format.

FEEDBACK AND HOD APPROVAL

1. ___________________________________________________________________________
2. ___________________________________________________________________________
3. ___________________________________________________________________________
4. ___________________________________________________________________________

Name of Subject Teacher: H.O.D:

_____________________________ _____________________________________________
Signature: _
__________________________________________ Signature:
_ ___________________________________________