Computing · Year 10

Active learning ideas

Selection: Case Statements

Active learning helps Year 10 students grasp case statements because they move beyond abstract definitions to solve real problems. By refactoring messy if-else chains or designing menu systems, students see how structure improves clarity and reduces errors in their own code.

• National Curriculum Attainment Targets
• GCSE: Computing - Programming Fundamentals

• 20–45 min
• Pairs → Whole Class
• 4 activities

Activity 01

• Collaborative Problem-Solving
• 30 min · Pairs

Pair Refactor: If-Else to Case

Provide students with a nested if-else menu handler for a simple game. In pairs, they rewrite it using a case statement, test inputs, and note changes in line count and clarity. Pairs then swap code for peer review.

Compare the readability and efficiency of case statements versus nested if-else structures.

Facilitation Tip

During Pair Refactor, pair students with different prior knowledge to encourage peer teaching and immediate feedback on their refactoring choices.

What to look for

Present students with a short code snippet containing a series of nested if-else statements that could be replaced by a case statement. Ask them to rewrite the snippet using a case statement and explain one advantage of their new version.

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

Activity 02

• Collaborative Problem-Solving
• 45 min · Small Groups

Small Group Menu Design

Groups design a case-based menu for a library system handling options like borrow, return, or search. They code the structure, add sample outputs, and present one unique feature. Discuss efficiency as a class.

Design a program segment that uses a case statement to handle menu selections.

Facilitation Tip

In Small Group Menu Design, circulate to ensure groups test edge cases like invalid inputs and discuss how case statements handle them.

What to look for

Pose the question: 'When would using a case statement make your code significantly harder to read than using if-else statements?' Facilitate a class discussion where students provide examples and justify their reasoning.

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

Activity 03

• Collaborative Problem-Solving
• 20 min · Whole Class

Whole Class Debug Challenge

Display a buggy case statement on the board with missing breaks or fallthrough errors. Students suggest fixes in a think-pair-share, then vote on the best version before coding a corrected full program.

Justify when a case statement is a more appropriate choice than a series of if-else statements.

Facilitation Tip

For the Whole Class Debug Challenge, assign each group a different buggy case statement to analyze, then have them present their findings to the class.

What to look for

Ask students to write down one scenario where a case statement is the most appropriate control structure and one scenario where a series of if-else statements would be better. They should briefly explain their choices.

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

Activity 04

• Collaborative Problem-Solving
• 25 min · Individual

Individual Justification Task

Students receive code snippets and write a short justification for using case over if-else, citing readability or branch count. They test both versions with varied inputs to verify claims.

Compare the readability and efficiency of case statements versus nested if-else structures.

Facilitation Tip

In the Individual Justification Task, provide a checklist of criteria for effective case statements so students self-assess before submitting.

What to look for

Present students with a short code snippet containing a series of nested if-else statements that could be replaced by a case statement. Ask them to rewrite the snippet using a case statement and explain one advantage of their new version.

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

A few notes on teaching this unit

Teach case statements by starting with familiar tools students already use, like menu-driven programs or grade calculators. Avoid presenting case syntax as a standalone concept; instead, frame it as a solution to problems they’ve already encountered. Research shows that students grasp control structures better when they see the inefficiencies in their own code first, so prioritize refactoring over lectures.

Successful learning looks like students confidently replacing if-else chains with case statements, explaining when each structure is appropriate. They should justify their choices based on readability and maintenance, not just syntax.

---

Watch Out for These Misconceptions

• During Pair Refactor, watch for students assuming case statements are always faster than if-else chains.

  Provide a simple timer and line counter with the refactoring task. Ask pairs to measure execution time and count lines before and after refactoring, then discuss whether speed differences are meaningful compared to code clarity.

• During Small Group Menu Design, watch for students trying to use case statements with unsupported data types like strings in all languages.

  Provide a language-specific reference sheet with each group’s chosen language. Ask them to test their case statement with a string input and observe the error, then revise their design using if-else or an enum where necessary.

• During Whole Class Debug Challenge, watch for students ignoring break statements and assuming fallthrough is always desired.

  Give each group a code snippet with a missing break and an expected output. Ask them to run the code, observe the unexpected behavior, and explain why fallthrough caused the error. Have them add the missing break and compare outputs.

---

Methods used in this brief

• Collaborative Problem-Solving