Computer Science · 9th Grade · Programming with Purpose · Weeks 19-27

Conditional Statements (If/Else)

Students will use conditional statements to control the execution flow of a program based on specific criteria.

• Common Core State Standards
• CSTA: 3A-AP-15

About This Topic

Conditional statements are the mechanism by which programs make decisions. The if/else structure tells a program to execute different code paths based on whether a condition evaluates to true or false. For 9th graders in US K-12 CS, this is often the moment the abstract concept of an algorithm becomes concrete: here is code that actually changes its behavior based on data. CSTA 3A-AP-15 calls for students to create algorithms that use conditionals, and this topic lays that foundation.

A key challenge at this level is helping students think in boolean logic. Natural language is fuzzy; programming conditions are exact. Students who write conditions like 'if the score is good' must translate that into a precise threshold, and the process of making that precision explicit often reveals assumptions they did not know they were making. Decision trees and flowcharts are effective intermediate representations that bridge natural language thinking and code.

Active learning accelerates understanding here because students can evaluate each other's condition logic before they even touch a keyboard. Peer review of decision flowcharts catches logical gaps, redundant conditions, and unhandled cases more efficiently than individual work, and it builds the habit of testing logic before coding that characterizes professional software development.

Key Questions

1. Design conditional logic to handle complex decision trees in a program.
2. Analyze how different conditions lead to varied program outcomes.
3. Construct a program that uses if/else statements to respond to user choices.

Learning Objectives

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

Before You Start

Variables and Data Types

Why: Students need to understand how to store and manipulate data (like numbers or strings) to use them in conditions.

Basic Operators (Comparison and Logical)

Why: Students must know how to use operators like '>', '<', '==', '!=', 'and', 'or' to form valid conditions.

Introduction to Algorithms

Why: Students should have a foundational understanding of step-by-step instructions before learning how to control the flow of those instructions.

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.

Watch Out for These Misconceptions

Common Misconception

The else clause always has to be included.

What to Teach Instead

An else clause is optional and should only be included when there is meaningful code to run when the condition is false. Adding an empty or unnecessary else adds clutter without function. Peer code review helps students spot unnecessary else blocks and understand when they genuinely add value.

Common Misconception

If two conditions cover all possible cases, no values can fall through unhandled.

What to Teach Instead

Conditions like 'if x > 5' and 'if x < 5' leave out x == 5 entirely. Students often overlook edge values at exact thresholds. Testing with boundary values during peer review activities catches these gaps effectively.

Common Misconception

Nested if statements and chained else-if are equivalent and interchangeable.

What to Teach Instead

Nested ifs check the inner condition only if the outer one is true. Chained else-if checks each condition in order and stops at the first match. These produce different results for inputs that satisfy multiple conditions. Tracing execution with specific values makes this distinction visible.

Active Learning Ideas

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.

40 min·Small Groups

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.

25 min·Pairs

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.

20 min·Whole Class

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.

35 min·Pairs

Real-World Connections

• Video game developers use conditional statements extensively to determine character actions, enemy behaviors, and game state changes based on player input or in-game events. For example, an 'if the player presses the jump button' condition triggers the character's jump animation and movement.
• Automated customer service systems, like those used by airlines or banks, employ if/else logic to route calls or provide information. A system might ask 'if you are calling about a flight,' then present flight-related options, or 'else' route to a general operator.

Assessment Ideas

Quick Check

Present students with a simple scenario, such as a temperature check for outdoor activities. Ask them to write an if/else statement in pseudocode: 'If temperature is greater than 70 degrees, print 'Wear shorts'. Else, print 'Wear pants'.'

Peer Assessment

Students create a flowchart for a simple decision-making process (e.g., deciding what to wear based on weather). They exchange flowcharts and check for logical completeness: Are all paths covered? Are conditions clear and unambiguous? Partners provide one suggestion for improvement.

Exit Ticket

Give students a short Python code snippet with an if/else statement and a specific input value. Ask them to write down the exact output the program will produce and explain why.

Frequently Asked Questions

What is the difference between if/else and a switch statement?

A switch statement is a specialized conditional structure for checking a single variable against multiple exact values. An if/else chain is more flexible and can handle ranges, multiple variables, and complex boolean expressions. Switch statements often produce cleaner code when checking one variable against many fixed options, but if/else is more broadly applicable.

How do programmers handle situations with more than two possible conditions?

Programmers use chained else-if statements or switch statements to handle multiple branches. When conditions become very complex, they may refactor into functions that return values, making the code easier to read and test. The guiding principle is that the branching structure should match the logical structure of the problem.

How does active learning help when learning conditional statements?

Conditionals require students to think precisely about logic before and after writing code. When students review each other's flowcharts or trace through code by hand with their partner, they catch logical errors that they would miss when checking their own work. The collaborative pressure to explain logic aloud also strengthens understanding of boolean reasoning.

Can a condition ever be evaluated out of order in an if/else chain?

No. In a standard if/else if/else chain, conditions are evaluated from top to bottom, and execution stops at the first true condition. This order matters: placing the most specific conditions first, before broader conditions that might also match, ensures the correct branch runs for each input.