Computing · Year 6

Active learning ideas

Nested Selection and Multiple Conditions

Active learning works because nested logic is best understood through tactile and visual engagement. Students solidify abstract concepts like AND and OR when they physically arrange truth tables or trace code paths with their fingers. This topic demands repetition to override intuitive but incorrect assumptions about how conditions interact.

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

• 30–50 min
• Pairs → Whole Class
• 4 activities

Activity 01

• Concept Mapping
• 30 min · Pairs

Truth Table Challenge: AND vs OR

Pairs create truth tables on paper or digital sheets for two conditions using AND and OR. They predict outcomes for all input combinations, then code simple Scratch programs to verify. Discuss matches between tables and program runs.

Analyze how combining conditions with 'AND' and 'OR' changes program logic.

Facilitation Tip

During Truth Table Challenge, circulate and ask pairs to explain why a false condition in an AND row blocks the entire outcome.

What to look for

Provide students with two simple code snippets, one using 'AND' and one using 'OR' with identical conditions. Ask them to write one sentence explaining the difference in output if one of the conditions is false for each snippet.

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

Activity 02

• Concept Mapping
• 45 min · Small Groups

Flowchart to Nested Code: Puzzle Path

Small groups draw flowcharts for a character puzzle with nested decisions, like 'if health > 50 AND energy > 20, then jump'. Convert to Scratch code, test with sample inputs, and swap with another group to evaluate logic.

Differentiate between the outcomes of using 'AND' versus 'OR' in a conditional statement.

Facilitation Tip

For Flowchart to Nested Code, require students to label each branch with the condition it represents before translating to code.

What to look for

Present students with a scenario: 'A character can open a door if they have the key AND are at the door.' Ask them to write the pseudocode for this condition. Then, present: 'A character can eat an apple OR a banana.' Ask for the pseudocode for this.

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

Activity 03

• Concept Mapping
• 35 min · Whole Class

Debug Relay: Fix the Logic

Whole class starts with a shared buggy Scratch project using nested ifs and wrong operators. Teams take turns fixing one error, running tests, and passing to the next. Class votes on the final working version.

Construct a program that uses nested conditions to guide a character through a multi-stage puzzle.

Facilitation Tip

In Debug Relay, have students swap code sheets after each fix so they see how one correction affects the next step.

What to look for

Pose the question: 'Imagine a treasure chest that requires two keys to open, but you can use either a magic spell OR a special tool to break the lock if you don't have both keys.' Ask students to explain how they would use nested 'if' statements and 'AND'/'OR' to represent this logic in a program.

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

Activity 04

• Concept Mapping
• 50 min · Individual

Multi-Stage Game Builder: Individual

Individuals extend a basic game sprite with nested conditions for obstacles, such as 'if key pressed OR timer low AND position correct'. Playtest against self-set goals and refine based on edge cases.

Analyze how combining conditions with 'AND' and 'OR' changes program logic.

Facilitation Tip

During Multi-Stage Game Builder, insist students write pseudocode first to plan nested logic before coding.

What to look for

Provide students with two simple code snippets, one using 'AND' and one using 'OR' with identical conditions. Ask them to write one sentence explaining the difference in output if one of the conditions is false for each snippet.

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

A few notes on teaching this unit

Teach this by layering activities from concrete to abstract. Start with truth tables to build boolean intuition, move to flowcharts for visual logic, then use debugging to confront misconceptions directly. Avoid rushing to code—students need time to internalize how conditions chain together. Research shows that step-through debugging in block editors reduces confusion about nested structures more effectively than lectures.

Students will confidently write and modify nested if statements and use AND/OR correctly in real programs. They will explain their logic aloud, justify their code choices, and debug errors without skipping steps. Mastery shows when students can predict program flow before running it.

---

Watch Out for These Misconceptions

• During Truth Table Challenge, watch for students who mark AND rows as true when one condition is true.

  Have them add a physical counter to each row: place a token on the table only if every condition is true. If one is false, remove the token and ask why the whole row fails.

• During Flowchart to Nested Code, watch for students who place inner if statements outside the outer condition's path.

  Use colored pencils to trace the flowchart path and circle where the inner if should sit inside the outer block. Then, have them rewrite the pseudocode with indentation to match.

• During Debug Relay, watch for students who assume OR makes the entire condition true regardless of inputs.

  Freeze the code and ask them to test each input one at a time. Have them write down which inputs make the OR block run and which do not, then compare with the group.

---

Methods used in this brief

• Concept Mapping