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.

• Year 11
• Computing
• 4 activities
• 35 min–50 min

Learning Objectives

1. Design a program segment that uses nested if/else statements to manage multiple user inputs for a login system.
2. Compare the efficiency of 'for' loops versus 'while' loops when processing a list of student scores.
3. Create a Python script that iterates through a range of numbers, applying conditional logic to print specific outputs.
4. Analyze the flow of control in a given pseudocode snippet involving both selection and iteration.
5. Evaluate the suitability of different loop structures for tasks with predetermined versus indeterminate completion criteria.

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.

Prepare & details

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.

Setup: Groups at tables with access to research materials

Materials: Problem scenario document, KWL chart or inquiry framework, Resource library, Solution presentation template

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

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.

Prepare & details

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.

Setup: Groups at tables with access to research materials

Materials: Problem scenario document, KWL chart or inquiry framework, Resource library, Solution presentation template

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

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.

Prepare & details

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.

Setup: Groups at tables with access to research materials

Materials: Problem scenario document, KWL chart or inquiry framework, Resource library, Solution presentation template

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

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.

Prepare & details

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.

Setup: Groups at tables with access to research materials

Materials: Problem scenario document, KWL chart or inquiry framework, Resource library, Solution presentation template

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

Teaching This Topic

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.

What to Expect

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

Common Misconception

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

What to Teach Instead

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.

Common Misconception

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

What to Teach Instead

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.

Assessment Ideas

Exit Ticket

After Pair Programming: Nested Decision Tree, collect pseudocode from each pair and check that it correctly uses a single if statement without an unnecessary else for scenarios where alternatives aren’t needed.

Quick Check

During Loop Comparison Relay, circulate and ask each relay team to explain why they chose their loop type for the given task. Listen for references to known versus unknown repetition counts.

Discussion Prompt

After Flowchart to Code Challenge, facilitate a whole-class discussion where students compare their flowcharts and code for the same scenario. Ask them to identify where nesting added clarity or where a simpler structure would suffice.

Extensions & Scaffolding

• Challenge: Provide a scenario where multiple loops and nested ifs are needed, such as a traffic light simulation with pedestrian crossings and vehicle sensors.
• Scaffolding: Offer a partially completed flowchart with missing branches or loop conditions for students to fill in during Custom Program Builder.
• Deeper exploration: Ask students to refactor a monolithic while loop into a for loop with an accumulator and explain the change in efficiency.

Key Vocabulary

Conditional Statement	A programming construct that executes different code blocks based on whether a specified condition is true or false. Commonly implemented using if, else if, and else.
Loop (Iteration)	A programming construct that repeats a sequence of instructions until a specific condition is met. Includes 'for' and 'while' loops.
Nested Conditional	Placing one conditional statement inside another. This allows for more complex decision-making by evaluating multiple conditions sequentially.
For Loop	A loop that executes a block of code a fixed number of times, typically used when the number of iterations is known in advance.
While Loop	A loop that executes a block of code as long as a specified condition remains true. Used when the number of iterations is not known beforehand.