Technologies · Year 9

Active learning ideas

Structured Data and Databases

Active learning works for structured data and databases because abstract concepts like keys, joins, and normalization become concrete when students physically design schemas, write real queries, and debug errors. Hands-on activities force students to confront the limits of spreadsheets and experience firsthand how database structure affects speed, accuracy, and scalability.

• ACARA Content Descriptions
• AC9DT10K01
• AC9DT10P01

• 20–45 min
• Pairs → Whole Class
• 4 activities

Activity 01

• Case Study Analysis
• 30 min · Pairs

Pairs: Schema Design Challenge

Pairs sketch a relational schema for a sports club database with tables for players, teams, and matches. They identify primary keys, foreign keys, and relationships, then justify choices against redundancy risks. Share and peer review digitally.

Analyze how the structure of a database affects its ability to scale.

Facilitation Tip

During Schema Design Challenge, circulate and ask each pair to explain their primary key choice to uncover hidden assumptions about uniqueness.

What to look for

Present students with a simple scenario, such as a small music store with artists, albums, and songs. Ask them to sketch out the tables needed, identify the primary key for each table, and draw lines to show the foreign key relationships between tables.

• Analyze
• Evaluate
• Create
• Decision-Making
• Self-Management

Activity 02

• Case Study Analysis
• 45 min · Small Groups

Small Groups: SQL Query Relay

Provide sample relational data on animals in a zoo. Groups take turns writing SQL queries to extract info like 'animals by habitat' or 'count per species.' Rotate roles: writer, tester, explainer. Discuss query efficiency.

Evaluate the risks of data redundancy in a complex system.

Facilitation Tip

In SQL Query Relay, time each team’s query execution and display results publicly to build urgency and immediate feedback.

What to look for

Provide students with a pre-made, slightly redundant database table (e.g., a list of students with their class teacher repeated for each student). Ask them to write two sentences explaining why this repetition is a problem and one way to fix it using a separate table.

• Analyze
• Evaluate
• Create
• Decision-Making
• Self-Management

Activity 03

• Case Study Analysis
• 20 min · Whole Class

Whole Class: Redundancy Hunt

Display a denormalized database on screen. Class votes on redundant data examples, then suggests normalized fixes. Use polls for engagement and reveal scalability impacts with added records.

Design a relational database schema to model real-world relationships using tables and keys.

Facilitation Tip

For Redundancy Hunt, seed one table with deliberate inconsistencies so students experience the pain of updates before they design fixes.

What to look for

Pose the question: 'Imagine a social media platform that stores all user posts, comments, and likes in a single, massive table. What problems might arise as the platform grows to millions of users? How could a relational database design help?' Facilitate a class discussion on scalability and redundancy.

• Analyze
• Evaluate
• Create
• Decision-Making
• Self-Management

Activity 04

• Case Study Analysis
• 25 min · Individual

Individual: Real-World Model

Students design a personal database schema for a chosen scenario, like music playlists. Outline tables, keys, and sample queries, then test with invented data to check relationships.

Analyze how the structure of a database affects its ability to scale.

Facilitation Tip

In Real-World Model, model a sample query yourself first so students see the gap between their draft model and a working query.

What to look for

Present students with a simple scenario, such as a small music store with artists, albums, and songs. Ask them to sketch out the tables needed, identify the primary key for each table, and draw lines to show the foreign key relationships between tables.

• Analyze
• Evaluate
• Create
• Decision-Making
• Self-Management

A few notes on teaching this unit

Teach schema design by having students draw on paper first, then move to digital tools only after they grasp why relationships matter. Avoid starting with SQL syntax; build spatial understanding of tables and keys before syntax. Research shows students grasp joins better when they first experience the visual mismatch of unlinked tables, not when they memorize JOIN clauses.

Successful learning looks like students confidently designing normalized tables with clear primary and foreign keys, writing correct SQL queries with intentional joins, and articulating trade-offs between redundancy and query efficiency. They should explain why a single-table approach fails at scale and how relationships solve real problems.

---

Watch Out for These Misconceptions

• During Schema Design Challenge, watch for students who simply replicate spreadsheet columns without identifying primary keys or planning relationships.

  Ask each pair to circle their proposed primary key and draw connecting lines between tables before writing any SQL; this forces them to articulate relationships before syntax.

• During Redundancy Hunt, watch for students who label all repetition as bad without considering query speed or update costs.

  Have groups present one redundancy they kept and explain why it improves performance, forcing them to justify design choices.

• During SQL Query Relay, watch for teams that guess join conditions without aligning on table keys.

  Require teams to write the join condition on the board before running the query, making their assumptions visible and correctable.

---

Methods used in this brief

• Case Study Analysis