Computing · Secondary 4

Active learning ideas

Relational Database Design: Tables and Fields

Active learning works for relational database design because students need to experience constraints firsthand. When they design tables themselves, they confront why data types matter, how redundancy harms efficiency, and what happens when rules are broken.

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

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

Activity 01

• Concept Mapping
• 30 min · Pairs

Pair Design Challenge: Library Schema

Pairs read a school library scenario and list entities. They assign fields with data types, justify choices in a shared document. Pairs then swap schemas for peer review on type suitability.

Analyze how tables and fields organize data in a structured manner.

Facilitation Tip

During the Pair Design Challenge, circulate to ask guiding questions like 'What would happen if two books shared the same ISBN?' to push students beyond superficial designs.

What to look for

Provide students with a scenario, e.g., 'Design a table to store information about employees in a company.' Ask them to list at least 4 fields, specify a data type for each, and identify a potential primary key. Collect these to check understanding of table structure and data types.

• Understand
• Analyze
• Create
• Self-Awareness
• Self-Management

Activity 02

• Concept Mapping
• 25 min · Small Groups

Small Group Sort: Data Type Relay

Groups receive sample data items like emails or prices. They race to assign correct fields and types to a template table, then explain selections to the class. Discuss common errors as a wrap-up.

Differentiate between various data types and their appropriate use in database fields.

Facilitation Tip

In the Data Type Relay, assign each group a unique set of sample data to ensure varied practice and discussion across the class.

What to look for

Display a pre-made table with incorrect data types for some fields (e.g., 'Age' stored as TEXT). Ask students to identify the problematic fields and suggest the correct data type, explaining their reasoning. This can be done via a quick poll or show of hands.

• Understand
• Analyze
• Create
• Self-Awareness
• Self-Management

Activity 03

• Concept Mapping
• 35 min · Whole Class

Whole Class Build: Event Database

Project a blank table on the board for school events. Class suggests fields and types via sticky notes or shouts, vote on best options. Teacher inputs into a demo database to show live validation.

Construct a simple table schema for a real-world entity.

Facilitation Tip

For the Whole Class Build, provide a scaffolded starter schema so students focus on relationships and constraints rather than starting from scratch.

What to look for

Pose the question: 'Why is it important to choose the correct data type for a field, rather than just using TEXT for everything?' Facilitate a class discussion where students share examples of how incorrect types could lead to errors or inefficiencies in real-world applications.

• Understand
• Analyze
• Create
• Self-Awareness
• Self-Management

Activity 04

• Concept Mapping
• 20 min · Individual

Individual Validation: Schema Audit

Students get printed flawed schemas with wrong types. They identify issues, correct fields, and note impacts on queries. Share one fix with a partner for confirmation.

Analyze how tables and fields organize data in a structured manner.

Facilitation Tip

In the Schema Audit, model how to critique one another’s work with specific feedback before students exchange papers.

What to look for

Provide students with a scenario, e.g., 'Design a table to store information about employees in a company.' Ask them to list at least 4 fields, specify a data type for each, and identify a potential primary key. Collect these to check understanding of table structure and data types.

• Understand
• Analyze
• Create
• Self-Awareness
• Self-Management

A few notes on teaching this unit

Teach this topic by moving from concrete examples to abstract principles. Start with a flawed spreadsheet to show the chaos of unstructured data, then transition to a simple database to demonstrate how types and keys restore order. Avoid overwhelming students with theory upfront; let them discover the need for rules through their own design failures.

Successful learning looks like students identifying appropriate fields and data types for real-world scenarios, explaining their choices, and recognizing when a design needs refinement. They should also articulate why structure supports function in databases.

---

Watch Out for These Misconceptions

• During the Pair Design Challenge, watch for students treating tables like spreadsheets by replicating data across rows or ignoring constraints on input.

  Redirect groups by asking them to compare inserting invalid data (e.g., a text title into an INTEGER ISBN field) in both a spreadsheet and their database schema. Discuss which system catches the error and why.

• During the Data Type Relay, watch for students assuming any data type can store any value without consequences.

  Have each group attempt to calculate the average price of items stored as TEXT in their relay task. When the calculation fails, prompt them to propose a better type and explain the trade-offs.

• During the Whole Class Build, watch for students adding excessive fields to tables under the belief that more is always better.

  Pause the activity and ask groups to justify each field in their schema. Challenge them to remove one field and explain how the design remains functional without it. Use examples like 'phone_number' for a 'Books' table to highlight relevance.

---

Methods used in this brief

• Concept Mapping