Computing · Year 5 · Variables in Games · Spring Term

Decisions in Daily Life

Mapping everyday decisions to the logical structures used by computers.

• National Curriculum Attainment Targets
• KS2: Computing - Programming and Algorithms

About This Topic

Decisions in Daily Life helps Year 5 students connect everyday choices to the branching structures in computer programs. They map routines like getting to school onto 'if-then' logic, spotting sequences of conditions such as 'if raining, then wear coat'. This builds understanding of algorithms as step-by-step instructions with decision points, aligning with KS2 Computing standards for programming.

In the Variables in Games unit, this topic lays groundwork for coding conditional statements that respond to game states. Students construct flowcharts for complex decisions, like choosing breakfast based on time and weather, and explore what happens when conditions are unclear, such as neither true nor false. These activities foster decomposition of problems and prediction skills essential for debugging code later.

Active learning shines here because students act out decisions in role-play or collaboratively build oversized flowcharts on the floor. These methods make logical structures visible and testable, turning abstract computing concepts into relatable, hands-on experiences that stick.

Key Questions

1. Analyze how many 'if-then' decisions you make before you arrive at school.
2. Construct a simple flowchart to represent a complex everyday decision.
3. Predict what happens if a condition is neither true nor false in a decision.

Learning Objectives

• Analyze the sequence of 'if-then' decisions in a familiar daily routine, such as getting ready for school.
• Construct a flowchart representing a complex everyday decision, including multiple conditions and outcomes.
• Explain the concept of a boolean condition (true/false) and predict the program's behavior when a condition is ambiguous.
• Compare the logic of two different everyday decisions by creating flowcharts for each.

Before You Start

Sequencing Instructions

Why: Students need to understand how to follow and create ordered steps before they can introduce decision points.

Identifying Patterns

Why: Recognizing patterns helps students identify the conditions and outcomes within everyday decisions.

Key Vocabulary

Algorithm	A set of step-by-step instructions or rules designed to solve a problem or perform a task.
Flowchart	A visual diagram that represents the steps and decisions in a process using standard symbols.
Condition	A statement that can be either true or false, used to make decisions in a program or process.
If-Then Statement	A programming structure where a specific action is performed only if a certain condition is met.
Boolean	A type of data that can only have one of two values: true or false.

Watch Out for These Misconceptions

Common Misconception

Computers understand decisions like humans do, without clear rules.

What to Teach Instead

Computers require explicit conditions in binary terms (true or false). Role-playing ambiguous scenarios shows why programs need defined 'else' branches. Group discussions help students articulate precise conditions from their experiences.

Common Misconception

All decisions are simple yes/no choices.

What to Teach Instead

Real decisions nest multiple conditions. Building layered flowcharts reveals this structure. Collaborative construction lets students test and iterate, correcting oversimplifications through peer challenges.

Common Misconception

Unclear conditions (neither true nor false) make programs stop.

What to Teach Instead

Programs handle this with default paths or error checks. Prediction activities with card sorts demonstrate outcomes. Acting out paths clarifies how coders anticipate edge cases.

Active Learning Ideas

Flowchart Walkthrough: School Journey

Students list decisions made on the way to school, such as crossing roads or choosing routes. In pairs, they draw a flowchart with ovals for start/end, rectangles for actions, and diamonds for conditions. Pairs present one path to the class for feedback.

35 min·Pairs

Decision Role-Play: Breakfast Choices

Assign roles like 'hungry child' facing conditions (time, weather, ingredients). Small groups act out 'if-then' branches, recording outcomes on sticky notes. Groups combine paths into a shared flowchart on the board.

45 min·Small Groups

Chain Reaction: Class If-Then Build

Start with a whole-class decision like 'plan a trip'. Teacher poses a condition; students suggest actions or new conditions, adding to a large floor flowchart with string and cards. Discuss predictions for ambiguous cases.

30 min·Whole Class

Prediction Cards: Boolean Challenges

Provide cards with everyday scenarios and conditions that are true, false, or unclear. Individually, students predict program outcomes and sketch flowcharts. Share in pairs to refine ideas.

25 min·Individual

Real-World Connections

• Traffic light systems use 'if-then' logic: if the sensor detects a car, then the light changes. This ensures smooth traffic flow in cities like London.
• Smart home devices, such as thermostats, use conditional logic. If the room temperature is below a set point, then the heating turns on, optimizing comfort and energy use in homes across the UK.
• Video game developers use decision structures extensively. For example, in a game like 'Minecraft', if the player has enough resources, then they can craft an item.

Assessment Ideas

Exit Ticket

Give students a scenario: 'You want to play outside. If it is sunny, you will play. If it is raining, you will read a book.' Ask them to write down the 'if' part and the 'then' part of this decision.

Discussion Prompt

Ask students: 'Imagine you are designing a robot to make breakfast. What are some decisions the robot needs to make? What information (conditions) does it need to make those decisions?' Record their ideas on the board.

Quick Check

Present students with a simple flowchart for choosing an outfit based on weather. Ask them to trace the path for a specific weather condition (e.g., 'It is cold and windy') and state the final outcome.

Frequently Asked Questions

How do I introduce flowcharts for everyday decisions in Year 5?

Start with a familiar routine like morning prep. Model a simple flowchart on the board, using shapes for actions and decisions. Have students add branches in pairs, then merge into class examples. This scaffolds from concrete to abstract, linking life to code in 20 minutes.

How does this topic connect to programming variables in games?

Decisions mirror 'if' statements that check variable values, like player score or health. Flowchart practice predicts game behaviors, preparing students to code conditions. It builds decomposition skills for breaking game logic into testable parts.

What are common errors when students map decisions to logic?

Students often skip 'else' paths or assume intuitive understanding. Use prediction tasks with ambiguous conditions to expose gaps. Peer review of flowcharts encourages precise language, reducing vague terms like 'maybe'.

Why use active learning for teaching decisions in computing?

Active methods like role-play and physical flowcharts make invisible logic tangible. Students walk paths, test conditions, and debate outcomes, deepening understanding over passive diagrams. This boosts engagement and retention, especially for visual-spatial learners, while building collaboration for real programming teamwork.