Variables, Data Types, and Operators

Active learning works for this topic because students need to experience firsthand how data types and operators behave before they can design reliable tests. Testing code manually helps them see why boundary cases matter, and working in pairs or stations makes abstract concepts like data conversion feel concrete. This builds the critical mindset of anticipating errors rather than just fixing them after they appear.

• Year 11
• Computing
• 3 activities
• 15 min–40 min

Learning Objectives

1. Classify data into integer, float, string, and boolean types, providing examples of appropriate usage for each.
2. Construct arithmetic, relational, and logical expressions to solve programming problems.
3. Analyze the impact of data type mismatches on program execution and output.
4. Demonstrate the declaration and manipulation of variables within a program.
5. Evaluate the effectiveness of different operators in achieving desired computational results.

Inquiry Circle

⏱ 30 min·Small Groups

Inquiry Circle: The Ultimate Test Plan

Groups are given a program specification for a simple calculator. They must work together to create a list of 10 test cases that cover normal, boundary, and erroneous data, then swap with another group to see if their plan catches all the bugs.

Prepare & details

Differentiate between integer, float, string, and boolean data types and their appropriate uses.

Facilitation Tip: During Collaborative Investigation, circulate and ask groups to explain why they chose specific test cases, pushing them to justify their reasoning aloud.

Setup: Groups at tables with access to source materials

Materials: Source material collection, Inquiry cycle worksheet, Question generation protocol, Findings presentation template

• Analyze
• Evaluate
• Create
• Self-Management
• Self-Awareness

Stations Rotation

⏱ 40 min·Small Groups

Stations Rotation: Testing Types

Set up stations for Iterative Testing, Terminal Testing, and Boundary Analysis. At each station, students perform a specific task, such as fixing a bug in a loop or testing a login screen with 'edge case' passwords.

Prepare & details

Construct expressions using arithmetic, relational, and logical operators to achieve specific outcomes.

Facilitation Tip: In Station Rotation, provide a timer at each station to keep students focused on the task and ensure they rotate efficiently between types of testing.

Setup: Tables/desks arranged in 4-6 distinct stations around room

Materials: Station instruction cards, Different materials per station, Rotation timer

• Remember
• Understand
• Apply
• Analyze
• Self-Management
• Relationship Skills

Think-Pair-Share

⏱ 15 min·Pairs

Think-Pair-Share: Prioritising Bugs

Provide a list of five bugs found in a banking app. Students must rank them in order of priority for fixing and justify their choices to a partner, considering factors like security, user experience, and data integrity.

Prepare & details

Analyze how incorrect data type usage can lead to runtime errors or unexpected behavior.

Facilitation Tip: For Think-Pair-Share, assign roles: one student identifies the bug, the other suggests a fix, and they discuss which bug to prioritize first.

Setup: Standard classroom seating; students turn to a neighbor

Materials: Discussion prompt (projected or printed), Optional: recording sheet for pairs

• Understand
• Apply
• Analyze
• Self-Awareness
• Relationship Skills

Teaching This Topic

Teachers should model the process of testing with clear think-alouds, showing how they decide which data to use and why. Emphasize that testing is iterative, not a one-time step at the end. Avoid rushing through the topic; spend time on edge cases and real-world examples. Research shows that students grasp data types better when they see how incorrect types lead to runtime errors or unexpected behavior.

What to Expect

Successful learning looks like students confidently selecting data types for different scenarios, writing test cases that cover normal, boundary, and erroneous data, and explaining why a program’s output might be wrong even when it runs without errors. They should also prioritize bugs based on their impact on functionality and user experience.

Watch Out for These Misconceptions

Common Misconception

During Collaborative Investigation: The Ultimate Test Plan, watch for students who only test the happy path or obvious cases without considering edge scenarios.

What to Teach Instead

Remind groups that their test plan must include inputs like empty strings, negative numbers, or values just outside the expected range. Ask them to plot their test cases on a number line to visualize boundaries.

Common Misconception

During Station Rotation: Testing Types, watch for students who treat boundary data as any random number close to the limit.

What to Teach Instead

Have students mark exact boundary points (e.g., 0 and 11 for a 1-10 range) on a physical or digital number line during the station activity. Ask them to test these specific values and observe the program’s response.

Assessment Ideas

Exit Ticket

After Collaborative Investigation: The Ultimate Test Plan, provide students with a short code snippet containing a variable declaration and an operation. Ask them to identify the data type of the variable and predict the output of the operation, explaining their reasoning in 2-3 sentences.

Quick Check

During Station Rotation: Testing Types, present students with a scenario (e.g., storing a user’s age) at one station and ask them to identify the most appropriate data type and the primary operator needed for a relevant calculation or comparison.

Discussion Prompt

During Think-Pair-Share: Prioritising Bugs, pose the question: 'Imagine you are building a simple calculator application. What are the potential problems if you try to add a text input (string) directly to a number input (integer) without conversion? How would you solve this?' Facilitate a class discussion on data type conversion and error handling.

Extensions & Scaffolding

• Challenge: Ask students to write a short program that intentionally includes a data type mismatch, then challenge peers to find and fix the bug before running it.
• Scaffolding: Provide a partially completed test plan template with prompts like 'What happens if the user enters a word instead of a number?'
• Deeper exploration: Have students research how different programming languages handle type conversion and present findings to the class.

Key Vocabulary

Variable	A named storage location in a program that holds a value which can change during program execution.
Data Type	A classification that specifies which type of value a variable can hold and what operations can be performed on it.
Operator	A symbol that performs an operation on one or more operands, such as arithmetic (+, -), relational (>, <), or logical (AND, OR).
Integer	A whole number, positive or negative, without decimals. Used for counting or precise numerical values.
Float	A number with a decimal point. Used for measurements or values that require fractional precision.
String	A sequence of characters, such as text. Used for names, messages, or textual data.
Boolean	A data type that can only have one of two values: true or false. Used for logical conditions and flags.