Computing · Secondary 3

Active learning ideas

Conditional Statements: If, Elif, Else

Active learning works for conditional statements because Python’s decision-making relies on precise sequencing. Students must physically trace code paths to grasp how conditions interact, making hands-on activities more effective than abstract explanations alone.

• MOE Syllabus Outcomes
• MOE: Programming - S3

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

Activity 01

• Plan-Do-Review
• 30 min · Pairs

Pair Programming: Grade Classifier

Pairs input a student's mark and use if-elif-else to output grades A to F, including boundaries like 75-79 for B. Test with 10 varied scores, then add input validation for invalid entries. Share one edge case discussion with the class.

Design a program that makes decisions based on multiple conditions.

Facilitation Tip

During Pair Programming: Grade Classifier, ask pairs to swap roles every 5 minutes to ensure both students engage with the logic and syntax equally.

What to look for

Provide students with a scenario, such as grading a student's score (A, B, C, D, F). Ask them to write down the Python code using if, elif, and else to determine the grade. Collect these to check their understanding of conditional structure.

• Remember
• Apply
• Analyze
• Self-Management
• Decision-Making
• Self-Awareness

Activity 02

• Plan-Do-Review
• 45 min · Small Groups

Small Groups: Traffic Light Simulator

Groups code a traffic light system where color changes based on time and vehicle sensors using multiple elifs. Run simulations with different inputs and predict outcomes before execution. Refactor to nested ifs and compare behaviors.

Analyze how the order of 'elif' conditions can affect program behavior.

Facilitation Tip

For Traffic Light Simulator, provide printed flowcharts so students can annotate expected paths before coding.

What to look for

Present students with a simple Python code snippet containing an if-elif-else structure and a specific input value. Ask them to predict the output of the code and explain their reasoning, focusing on how the conditions are evaluated sequentially.

• Remember
• Apply
• Analyze
• Self-Management
• Decision-Making
• Self-Awareness

Activity 03

• Plan-Do-Review
• 25 min · Whole Class

Whole Class: Condition Order Prediction

Project buggy code with jumbled elifs for discount calculations. Students predict outputs for sample inputs on mini-whiteboards, then run the code to verify. Vote on reorderings and test class suggestions live.

Justify the use of nested 'if' statements versus a series of 'elif' statements.

Facilitation Tip

In Condition Order Prediction, have students write their predictions on sticky notes before sharing, forcing them to commit to an answer before discussion.

What to look for

Pose the question: 'When might you choose to use nested if statements instead of a long chain of elif statements?' Facilitate a class discussion where students justify their choices based on logic, readability, and the nature of the conditions being checked.

• Remember
• Apply
• Analyze
• Self-Management
• Decision-Making
• Self-Awareness

Activity 04

• Plan-Do-Review
• 35 min · Individual

Individual: Nested Decision Tree

Each student builds a quiz scorer with nested ifs for subjects and overall grade using elif chains inside. Test personally, then swap with a partner for debugging feedback on logic flow.

Design a program that makes decisions based on multiple conditions.

Facilitation Tip

For Nested Decision Tree, limit the tree depth to 3 levels to prevent overwhelming beginners while still illustrating complexity.

What to look for

Provide students with a scenario, such as grading a student's score (A, B, C, D, F). Ask them to write down the Python code using if, elif, and else to determine the grade. Collect these to check their understanding of conditional structure.

• Remember
• Apply
• Analyze
• Self-Management
• Decision-Making
• Self-Awareness

A few notes on teaching this unit

Start with real-world analogies, like traffic lights or grade thresholds, to ground abstract logic. Model tracing code step-by-step using a color-coded whiteboard, highlighting which condition triggers. Avoid teaching elif without contrasting it with nested ifs early, as students often default to nesting even when chains suit the task better.

Successful learning shows when students can write clear if-elif-else chains, predict execution paths without running code, and explain why reordering conditions changes outcomes. They should also justify choices between nesting and chaining based on problem structure.

---

Watch Out for These Misconceptions

• During Condition Order Prediction, watch for students who believe elifs execute independently rather than sequentially.

  Have students physically reorder elif statements in their printed code snippets and trace execution with highlighters, then compare results in pairs to observe how order changes outcomes.

• During Pair Programming: Grade Classifier, watch for students who default to nesting if-else statements even for mutually exclusive conditions.

  Provide a starter code template with elif chains and ask pairs to refactor their nested solutions into chains, discussing why chains reduce redundancy and improve readability.

• During Traffic Light Simulator, watch for students who assume else runs if any prior condition fails, ignoring elifs.

  Use a live coding session where you intentionally misplace an elif and run the code, then ask students to predict and explain the incorrect output before fixing it together.

---

Methods used in this brief

• Plan-Do-Review