Computing · Year 11

Active learning ideas

Control Structures: Selection and Iteration

Active learning works for control structures because students need to physically trace logic paths and debug live code to grasp how selection and iteration direct program flow. Moving from passive reading to pair debugging and flowchart mapping makes abstract concepts visible and concrete.

• National Curriculum Attainment Targets
• GCSE: Computing - Programming

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

Activity 01

• Problem-Based Learning
• 45 min · Pairs

Pair Programming: Nested Decision Tree

Pairs design a program that uses nested if/else to categorise student scores into grades with sub-branches for feedback. They test with sample data, swap roles to debug partner's code, and discuss improvements. Extend by adding loop for multiple entries.

Explain how nested conditional statements can handle complex decision-making processes.

Facilitation Tip

During Pair Programming: Nested Decision Tree, have students switch roles between driver and navigator every three minutes to keep both engaged with logic tracing.

What to look for

Provide students with a scenario: 'A vending machine dispenses a snack if the correct change is inserted and the item is in stock. If not enough change is inserted, it asks for more. If the item is out of stock, it offers a refund.' Ask students to write pseudocode for this scenario, using at least one 'if/else' and one 'while' loop.

• Analyze
• Evaluate
• Create
• Decision-Making
• Self-Management
• Relationship Skills

Activity 02

• Problem-Based Learning
• 50 min · Small Groups

Small Groups: Loop Comparison Relay

Groups race to implement the same task three ways: for loop with known iterations, while loop with condition check, and a flawed version to debug. Rotate who codes each round, then present efficiency differences to class.

Compare the use cases for 'for' loops versus 'while' loops in iterative tasks.

Facilitation Tip

In Loop Comparison Relay, assign each student one loop type and require them to justify their choice using a real-world example before writing code.

What to look for

Display a short Python code snippet containing a 'for' loop with an 'if' statement inside. Ask students to predict the output of the code and explain why. Then, ask them to modify the code to use a 'while' loop instead and explain the difference in its execution.

• Analyze
• Evaluate
• Create
• Decision-Making
• Self-Management
• Relationship Skills

Activity 03

• Problem-Based Learning
• 35 min · Whole Class

Whole Class: Flowchart to Code Challenge

Project a problem flowchart using selection and iteration. Class votes on pseudocode steps, then codes in shared editor. Run tests live, vote on fixes for errors, reinforcing structure translation.

Design a program segment that uses both selection and iteration to solve a given problem.

Facilitation Tip

For Flowchart to Code Challenge, provide a blank template and colored pens so students can revise and redraw paths when logic errors arise.

What to look for

Pose the question: 'When would you choose a 'for' loop over a 'while' loop, and vice versa?' Facilitate a class discussion where students provide specific examples of programming tasks and justify their choice of loop structure.

• Analyze
• Evaluate
• Create
• Decision-Making
• Self-Management
• Relationship Skills

Activity 04

• Problem-Based Learning
• 40 min · Individual

Individual: Custom Program Builder

Students independently create a guessing game combining while loop for retries and if/else for hints based on closeness. Peer review follows, with revisions for edge cases like invalid inputs.

Explain how nested conditional statements can handle complex decision-making processes.

Facilitation Tip

In Custom Program Builder, insist students include test cases in comments to force them to think through edge conditions before coding.

What to look for

Provide students with a scenario: 'A vending machine dispenses a snack if the correct change is inserted and the item is in stock. If not enough change is inserted, it asks for more. If the item is out of stock, it offers a refund.' Ask students to write pseudocode for this scenario, using at least one 'if/else' and one 'while' loop.

• Analyze
• Evaluate
• Create
• Decision-Making
• Self-Management
• Relationship Skills

A few notes on teaching this unit

Teach selection and iteration by making students confront their own misconceptions through live tracing and deliberate mistakes. Research shows that asking students to predict outputs before running code reduces overconfidence and improves debugging. Avoid rushing through syntax; instead, emphasize reading code aloud and drawing flow arrows to reveal hidden assumptions. Use the concrete-to-abstract approach: start with a flowchart, then pseudocode, then real syntax, so students see each layer as a translation rather than a new skill.

Successful learning looks like students confidently tracing nested conditions, choosing the right loop for a task, and explaining their reasoning using flowcharts or pseudocode. They should also identify redundant branches and unnecessary iterations when reviewing peers’ work.

---

Watch Out for These Misconceptions

• During Pair Programming: Nested Decision Tree, watch for students who automatically add else clauses even when the logic only needs a single if.

  Prompt pairs to trace the code without the else and ask whether the program still produces the correct result. If it does, have them remove the redundant else and discuss why it was unnecessary.

• During Loop Comparison Relay, watch for students who assume for loops are always better than while loops because they see them more often.

  Have relay teams run both loop types with a sentinel value and print each iteration count. Ask them to compare outputs and discuss which structure better matches the problem’s unknown repetition count.

---

Methods used in this brief

• Problem-Based Learning