Computer Science · 9th Grade

Active learning ideas

Flowcharts and Pseudocode for Logic

Planning logic with flowcharts and pseudocode feels abstract until students see how it connects to real decisions. Active learning makes these tools concrete by letting students move, discuss, and test their ideas before coding. This hands-on practice builds confidence and reduces frustration when they start programming.

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

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

Activity 01

• Think-Pair-Share
• 20 min · Pairs

Think-Pair-Share: Pseudocode the Morning

Students individually write pseudocode for their morning routine, including decision points like checking the alarm and choosing breakfast. Partners compare structures and identify how their decision logic differs, then discuss how computers handle the same types of conditional choices.

Design a flowchart to represent a multi-step decision-making process.

Facilitation Tip

During Think-Pair-Share: Pseudocode the Morning, set a timer so students have equal turns explaining and listening.

What to look for

Present students with a simple real-world problem, such as 'making a peanut butter and jelly sandwich'. Ask them to create a flowchart representing the steps. Check if they use appropriate symbols and if the sequence is logical.

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

Activity 02

• Gallery Walk
• 35 min · Small Groups

Gallery Walk: Flowchart Audit

Groups create flowcharts for a decision scenario on large paper (e.g., deciding whether to bring an umbrella). Post them around the room. Students use color-coded sticky notes to mark each diagram: green for clear logic, yellow for ambiguous steps, and red for logic gaps they can identify.

Explain how pseudocode translates human language into computational steps.

Facilitation Tip

During Gallery Walk: Flowchart Audit, ask students to leave sticky notes with one question or suggestion per poster they review.

What to look for

Students write a short pseudocode algorithm for a task (e.g., 'checking if a number is even'). They then exchange their pseudocode with a partner. Partners should identify one unclear step and suggest a clearer way to phrase it.

• Understand
• Apply
• Analyze
• Create
• Relationship Skills
• Social Awareness

Activity 03

• Peer Teaching
• 25 min · Pairs

Peer Teaching: Human CPU

One student acts as the CPU and can only follow written pseudocode literally, without inferring intent. Their partner writes pseudocode to guide them through a physical task like making a sandwich. The CPU follows instructions exactly as written, exposing every gap in the logic through its literal execution.

Critique the clarity and completeness of a given pseudocode algorithm.

Facilitation Tip

During Peer Teaching: Human CPU, rotate roles every 2 minutes so every student experiences being the CPU and the programmer.

What to look for

Provide students with a pre-made flowchart for a simple process. Ask them to write 2-3 sentences explaining what the flowchart represents and identify one potential ambiguity or missing step.

• Understand
• Apply
• Analyze
• Create
• Self-Management
• Relationship Skills

Activity 04

• Inquiry Circle
• 30 min · Small Groups

Inquiry Circle: Pseudocode Reverse-Engineering

Small groups receive a short working program and must reverse-engineer the pseudocode that could have produced it. Groups then share their versions and discuss which is clearest, revealing that multiple valid pseudocode representations can describe the same algorithm.

Design a flowchart to represent a multi-step decision-making process.

Facilitation Tip

During Collaborative Investigation: Pseudocode Reverse-Engineering, provide a mix of correct and flawed examples so students practice identifying both clarity and ambiguity.

What to look for

Present students with a simple real-world problem, such as 'making a peanut butter and jelly sandwich'. Ask them to create a flowchart representing the steps. Check if they use appropriate symbols and if the sequence is logical.

• Analyze
• Evaluate
• Create
• Self-Management
• Self-Awareness

A few notes on teaching this unit

Teach this topic by modeling your own thinking out loud. Show students how you draft, revise, and test your flowchart or pseudocode before declaring it finished. Avoid rushing to the next step—spend time on the messiness of planning. Research shows that novices benefit from seeing experts struggle and refine their work, not just the final polished product.

By the end of these activities, students will explain their logic clearly, identify gaps in their planning, and revise their work based on feedback. They will use standard symbols and pseudocode conventions correctly in every task.

---

Watch Out for These Misconceptions

• During Think-Pair-Share: Pseudocode the Morning, watch for students who try to write pseudocode that looks exactly like Python or Java.

  During Think-Pair-Share: Pseudocode the Morning, remind students that pseudocode is for humans. Have them highlight parts of their pseudocode that use plain English or loose structure, and ask peers to explain what those steps mean.

• During Gallery Walk: Flowchart Audit, watch for students who assume a flowchart is correct if it looks complete.

  During Gallery Walk: Flowchart Audit, ask students to trace each flowchart with their finger and note any steps that feel vague or missing. Use these observations to guide a class discussion about testing and refinement.

---

Methods used in this brief

• Think-Pair-Share
• Gallery Walk
• Peer Teaching
• Inquiry Circle