Computing · Secondary 4

Active learning ideas

Database Design Principles: Avoiding Redundancy

Active learning builds students' intuition for database problems that spreadsheets cannot show. When students physically mark redundancies or role-play updates, they see why flat files break before they learn formal rules. Hands-on work makes the cost of redundancy concrete and memorable for teenage learners.

• MOE Syllabus Outcomes
• MOE: Data Management - S4
• MOE: Database Systems - S4

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

Activity 01

• Case Study Analysis
• 30 min · Pairs

Pair Work: Redundancy Hunt

Give pairs a printed flat table of school event registrations with duplicate participant details. They circle redundancies and list potential anomalies like update errors. Pairs then draw a two-table normalized schema with keys.

Why is data redundancy a problem in databases?

Facilitation Tip

During the Redundancy Hunt, provide colored markers so pairs can highlight repeating groups and discuss each mark aloud before moving to the next row.

What to look for

Present students with a table containing redundant data (e.g., student names and class details repeated for each subject they take). Ask them to identify at least two instances of redundancy and explain why they are problematic.

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

Activity 02

• Case Study Analysis
• 45 min · Small Groups

Small Groups: Normalize a Sales Database

Provide groups with a redundant sales table mixing products, customers, and orders. Groups discuss issues, apply 1NF and 2NF, and create three linked tables. They share schemas via whiteboard sketches.

Explain strategies to reduce duplicate data when designing tables.

Facilitation Tip

When groups normalize the sales database, insist they write each new table name on a sticky note and place it on the whiteboard before finalizing the schema.

What to look for

In pairs, students are given a simple database design (e.g., a single table for library books including author details). They critique each other's design, identifying redundancies and suggesting how to split the table to create separate tables for books and authors, using primary and foreign keys.

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

Activity 03

• Case Study Analysis
• 25 min · Whole Class

Whole Class: Anomaly Role-Play

Project a sample database. Assign class roles for update scenarios, such as changing a customer's address. Vote and discuss inconsistencies, then normalize live on screen.

Critique a simple database design and suggest ways to make it more efficient by reducing redundancy.

Facilitation Tip

In the Anomaly Role-Play, assign each student a role (data entry clerk, student, registrar) so the class experiences how one change ripples through an unnormalized file.

What to look for

Ask students to write down one strategy they learned to reduce data redundancy and provide a brief example of when this strategy would be useful in a real-world database scenario.

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

Activity 04

• Case Study Analysis
• 20 min · Individual

Individual: Step-by-Step Normalization

Students receive worksheets with progressively redundant tables. They normalize each to 2NF, labeling dependencies and keys, then check against a rubric.

Why is data redundancy a problem in databases?

Facilitation Tip

For the Step-by-Step Normalization worksheet, circulate and ask students to verbalize why each step reduces redundancy before they write the next one.

What to look for

Present students with a table containing redundant data (e.g., student names and class details repeated for each subject they take). Ask them to identify at least two instances of redundancy and explain why they are problematic.

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

A few notes on teaching this unit

Teachers should start with real examples students recognize, like class rosters or library checkouts, so the abstractions feel attached to lived experience. Avoid rushing to 1NF, 2NF, 3NF labels; instead, let students name the problems they see and invent rules that solve them. Research shows concrete examples followed by gradual abstraction lead to deeper understanding than starting with definitions.

Success looks like students confidently pointing to repeating data, naming anomalies, and proposing normalized designs that use primary and foreign keys. They should explain how their changes prevent update, insertion, and deletion issues without creating extra work for users.

---

Watch Out for These Misconceptions

• During the Redundancy Hunt, watch for students who assume one large table is simpler because it shows all data in one place.

  Have pairs circle the first instance where a change to student address would leave other rows outdated, then ask them to imagine updating 300 rows by hand in a real enrollment system.

• During the Normalize a Sales Database activity, watch for students who believe identical duplicates across rows cause no harm.

  Ask groups to simulate adding a new product by duplicating the entire row and changing only the product name, then watch the data diverge when they try to update the price.

• During the Anomaly Role-Play, watch for students who think normalization slows down queries because they see extra steps in the role-play script.

  Use the class’s role-play script to time a query on the unnormalized file versus a normalized version on the board, showing the real-world trade-off.

---

Methods used in this brief

• Case Study Analysis