Computer Science · Grade 10

Active learning ideas

Introduction to Databases

Active learning helps students grasp abstract database concepts by making them concrete. When Grade 10 students physically arrange fields, records, and tables, they move from passive listeners to active designers who see how structure impacts data management.

• Ontario Curriculum Expectations
• CS.HS.D.4
• CS.HS.D.5

• 25–40 min
• Pairs → Whole Class
• 4 activities

Activity 01

• Concept Mapping
• 35 min · Pairs

Pairs: Schema Design Challenge

Present a scenario like a school club membership list. Pairs brainstorm and sketch tables, fields, and records on chart paper, including primary keys. They present one design to the class for feedback.

Explain the purpose of a database in managing large amounts of information.

Facilitation Tip

For the Schema Design Challenge, provide blank grid paper and colored markers so pairs can visualize table relationships before writing SQL-like labels.

What to look for

Present students with a list of data types (e.g., a student's name, a social media post, a product price, an image file). Ask them to classify each as either structured or unstructured data and briefly explain their reasoning.

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

Activity 02

• Concept Mapping
• 25 min · Small Groups

Small Groups: Component Card Sort

Distribute cards labeled with data examples, such as 'email address' or 'John Doe record'. Groups sort them into tables, fields, and records, then justify choices in a class share-out.

Differentiate between structured and unstructured data.

Facilitation Tip

During the Component Card Sort, circulate with a stopwatch to time groups and add urgency, mimicking real database processing speed.

What to look for

Provide students with a scenario, such as 'managing a small music collection'. Ask them to list at least three fields (e.g., Song Title, Artist, Album, Genre) that would be needed in a database table for this scenario and identify what a single record would represent.

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

Activity 03

• Concept Mapping
• 30 min · Whole Class

Whole Class: Structured vs Unstructured Hunt

Project mixed data samples. Class votes and discusses categorizing as structured or unstructured, then simulates database queries on structured items using volunteer 'records'.

Design a simple database schema for a given scenario.

Facilitation Tip

In the Structured vs Unstructured Hunt, assign each small group a different data type so they collectively cover all samples and debate classifications together.

What to look for

Pose the question: 'Imagine you are designing a database for your school's sports teams. What would be the main tables you would need, and what information (fields) would go into each table? Discuss potential relationships between these tables.'

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

Activity 04

• Concept Mapping
• 40 min · Individual

Individual: Personal Data Schema

Students design a database schema for their own contacts list, listing tables, fields, and one sample record. They self-assess against a rubric and revise.

Explain the purpose of a database in managing large amounts of information.

Facilitation Tip

For the Personal Data Schema, remind students to include at least one field that requires a relationship to another table, like a student ID linked to a courses table.

What to look for

Present students with a list of data types (e.g., a student's name, a social media post, a product price, an image file). Ask them to classify each as either structured or unstructured data and briefly explain their reasoning.

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

A few notes on teaching this unit

Start with familiar examples, like student rosters, to introduce tables and fields, then contrast these with unstructured data like scanned report cards. Avoid overwhelming students with jargon; instead, let them experience schema design through paper prototypes first. Research shows that tactile modeling builds mental schemas faster than lectures on normalization.

By the end of these activities, students will explain the difference between fields, records, and tables, design a basic schema for a given scenario, and justify why a relational database outperforms a spreadsheet for complex queries.

---

Watch Out for These Misconceptions

• During the Schema Design Challenge, watch for students who create a single flat table for complex data, like storing all student information in one sheet without splitting into related tables.

  Prompt pairs to consider how querying for a student's grade level would require scanning every row. Guide them to split their design into tables like Students and Grades, with a shared ID field to connect records.

• During the Component Card Sort, watch for students who categorize all data as structured because it fits into neat columns.

  Have groups debate whether a video file or an audio clip belongs in a structured field. Provide a blob icon for unstructured data and ask them to justify placement using real-world examples like streaming platforms storing media as blobs.

• During the Personal Data Schema activity, watch for students who confuse fields with records by labeling an entire row as a field.

  Ask them to count the fields in one row, then compare it to the number of fields across all rows. Use a grid on the board to highlight how fields are column headers, while records are individual rows of data.

---

Methods used in this brief

• Concept Mapping