Skip to content
Digital Solutions · Year 12

Active learning ideas

Relational Database Modelling

Relational Database Modelling is a cornerstone of data-driven solutions. Students learn to organise complex information into logical structures using Entity-Relationship Diagrams (ERDs) and normalisation techniques (1NF, 2NF, 3NF). This topic is essential for managing data integrity and ensuring that digital solutions are scalable and efficient, reflecting the ACARA focus on managing and manipulating data.

ACARA Content DescriptionsQCAA DS 2019: Unit 4.1.1ACARA: ACTDIP042
25–50 minPairs → Whole Class3 activities

Activity 01

Inquiry Circle50 min · Small Groups

Inquiry Circle: The Data Normalisation Puzzle

Provide groups with a large, messy spreadsheet of 'un-normalised' data (e.g., a school sports day record). Students must work together to break the data into separate tables and define the primary and foreign keys to reach 3NF.

How does normalisation improve data integrity?
AnalyzeEvaluateCreateSelf-ManagementSelf-Awareness
Generate Complete Lesson

Activity 02

Think-Pair-Share25 min · Pairs

Think-Pair-Share: SQL Query Challenge

Present a complex data request (e.g., 'Find all students who take IT and have an overdue library book'). Students draft the SQL query individually, then pair up to debug and refine their logic before sharing with the class.

What are the key components of an ER diagram?
UnderstandApplyAnalyzeSelf-AwarenessRelationship Skills
Generate Complete Lesson

Activity 03

Simulation Game30 min · Whole Class

Simulation Game: Human ERD

Students act as 'Entities' (e.g., Student, Course, Teacher) and use lengths of string to represent 'Relationships'. They must physically demonstrate one-to-many and many-to-many connections to understand how linking tables are formed.

How do complex SQL queries join multiple tables?
ApplyAnalyzeEvaluateCreateSocial AwarenessDecision-Making
Generate Complete Lesson

A few notes on teaching this unit


Watch Out for These Misconceptions

  • A many-to-many relationship can be directly implemented in a database.

    Many-to-many relationships require a junction (linking) table. Physical modelling with strings and cards helps students see why a direct link fails to store unique data for the relationship itself.

  • Normalisation just makes the database more complicated.

    Normalisation reduces data redundancy and prevents update anomalies. Using a 'broken' database simulation helps students experience the frustration of inconsistent data, making the value of 3NF clear.


Methods used in this brief