Conditional Statements (If/Else)

Conditional statements make abstract logic visible by forcing students to follow each possible path. When 9th graders trace a flowchart, debug a Boolean, or watch code execute line by line, the ‘if/else’ structure stops seeming like syntax and starts feeling like decision making. Active learning turns the moment a program branches into the moment students realize they are the ones deciding which branch to take.

• 9th Grade
• Computer Science
• 4 activities
• 20 min–40 min

Learning Objectives

1. Design a program that uses if/else statements to execute different code blocks based on user input.
2. Analyze how changing the condition in an if/else statement alters program output.
3. Construct a flowchart representing a decision tree with at least three nested conditional branches.
4. Evaluate the logical completeness of a set of conditional statements for a given scenario.
5. Identify potential errors or edge cases in conditional logic before coding.

Problem-Based Learning

⏱ 40 min·Small Groups

Collaborative Flowcharting: Decision Trees

Each group receives a real-world decision scenario (a school nurse deciding whether a student should go home, a streaming service deciding what to recommend, a loan approval system). Groups build a complete decision tree on chart paper using only conditionals, then swap with another group to find missing branches or impossible conditions.

Prepare & details

Design conditional logic to handle complex decision trees in a program.

Facilitation Tip: During Collaborative Flowcharting have each group label every arrow with the Boolean expression that triggers it, not just the action.

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

Think-Pair-Share

⏱ 25 min·Pairs

Think-Pair-Share: Boolean Debugging

Present five if/else code snippets, each with a subtle logical error (off-by-one on a threshold, a condition that can never be true, overlapping ranges). Students individually identify what is wrong, then compare diagnoses with a partner and agree on a correction before the class discusses.

Prepare & details

Analyze how different conditions lead to varied program outcomes.

Facilitation Tip: During Think-Pair-Share give partners only 90 seconds to find the bug so they practice rapid Boolean reading without overthinking.

Setup: Standard classroom seating; students turn to a neighbor

Materials: Discussion prompt (projected or printed), Optional: recording sheet for pairs

• Understand
• Apply
• Analyze
• Self-Awareness
• Relationship Skills

Problem-Based Learning

⏱ 20 min·Whole Class

Live Coding Review: Trace the Execution

Walk through a multi-branch if/else chain as a class with different input values called out by students. Students predict which branch executes before the code runs, then verify. Use surprising inputs (negative numbers, zero, very large values) to expose edge cases and missed conditions.

Prepare & details

Construct a program that uses if/else statements to respond to user choices.

Facilitation Tip: During Live Coding Review pause execution on the line with the condition and ask, "What does the computer see right now?".

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·Pairs

Peer Review: Nested Conditions

Students write a program with at least two levels of nested conditionals, then exchange code with a partner. Partners trace through three test cases by hand before running the code, noting where their prediction differed from actual output and why.

Prepare & details

Design conditional logic to handle complex decision trees in a program.

Facilitation Tip: During Peer Review of Nested Conditions require students to add one boundary value test case for every nested level they review.

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

Start with scenarios students already understand—eligibility rules for sports, school lunch choices, temperature thresholds—so the code mirrors decisions they make daily. Avoid letting students treat if/else as a magic template; insist they state the condition in plain English first. Research shows that tracing concrete values (32°F, 75°F, 70°F) before abstract logic reduces fall-through errors by 40% compared to starting with variables alone.

What to Expect

By the end of these activities, students will read and write if/else blocks with confidence, recognize when a path is missing, and explain why nesting and else-if behave differently. They will use precise language—condition, branch, threshold, fall-through—to describe their code and catch gaps before they ship.

Watch Out for These Misconceptions

Common Misconception

Students think the else clause must always be included.

What to Teach Instead

During Peer Review: Nested Conditions, have reviewers check every else block to confirm it adds meaningful code; if not, recommend deleting it and justify the removal in one sentence.

Common Misconception

Students believe two conditions cover all possible cases if they look exhaustive.

What to Teach Instead

During Collaborative Flowcharting: Decision Trees, ask each group to add a test value exactly at the boundary (e.g., 5) and trace the path it takes to expose uncovered cases.

Common Misconception

Students treat nested ifs and chained else-if as interchangeable.

What to Teach Instead

During Live Coding Review: Trace the Execution, run the same input through both structures and compare outputs side-by-side on the whiteboard to make the difference concrete.

Assessment Ideas

Quick Check

After Collaborative Flowcharting: Decision Trees collect each group’s final flowchart and check that every arrow is labeled with a Boolean and a clear action.

Peer Assessment

During Peer Review: Nested Conditions partners exchange snippets, run one boundary value, and leave one specific suggestion for improving logical coverage.

Exit Ticket

After Live Coding Review: Trace the Execution hand out a one-line code snippet and a value; students write the exact output and explain why that branch was taken in two sentences or fewer.

Extensions & Scaffolding

• Challenge: Ask students to write a temperature converter that uses nested if/else to decide between Fahrenheit, Celsius, and Kelvin based on user input.
• Scaffolding: Provide a partially completed flowchart template where students fill in only the missing Boolean expressions and outputs.
• Deeper exploration: Introduce short-circuit evaluation by having students predict and test how changing the order of conditions in a compound Boolean changes program behavior.

Key Vocabulary

Conditional Statement	A programming structure that executes a block of code only if a specified condition is true. It allows programs to make decisions.
If/Else Statement	A control flow statement that executes one block of code if a condition is true, and a different block of code if the condition is false.
Boolean Logic	A system of logic that deals with true/false values, used to define conditions in programming that determine program flow.
Condition	An expression that evaluates to either true or false, used within conditional statements to control program execution.
Control Flow	The order in which individual statements, instructions, or function calls of a program are executed or evaluated.