Computer Science · Grade 9

Active learning ideas

Flowcharts and Pseudocode

Flowcharts and pseudocode come alive when students move from listening to doing. Active learning lets them test their thinking by drawing, writing, and explaining step-by-step. These hands-on tasks reveal gaps in logic that silent worksheets miss, making abstract concepts concrete for ninth graders new to algorithm design.

• Ontario Curriculum Expectations
• CS.HS.AP.2
• CS.HS.CT.3

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

Activity 01

• Stations Rotation
• 30 min · Pairs

Pair Challenge: Flowchart a Recipe

Pairs receive a simple recipe, like making sandwiches. They sketch a flowchart showing steps, decisions (e.g., 'Bread available?'), and loops (e.g., repeat for each sandwich). Pairs swap with another duo to test by following the chart and suggest improvements.

Explain how flowcharts visually represent the flow of an algorithm.

Facilitation Tip

During the Pair Challenge, circulate and ask one student to explain their flowchart aloud while their partner traces the arrows with a finger, forcing them to justify every step.

What to look for

Provide students with a simple scenario, such as 'making a sandwich'. Ask them to draw a basic flowchart OR write pseudocode for the process. Collect these to check for understanding of basic sequencing and symbol usage.

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

Activity 02

• Stations Rotation
• 45 min · Small Groups

Small Group Pseudocode Relay

Divide class into small groups. Each group writes pseudocode for a problem like 'Find the largest number in a list.' Pass the draft to the next group for additions like error checks, then back for final critique and flowchart conversion.

Design pseudocode for a given problem, ensuring clarity and logical sequence.

Facilitation Tip

For the Small Group Pseudocode Relay, set a timer so teams feel pressure to move forward quickly, which prevents over-editing and keeps the focus on logical flow.

What to look for

Present students with a short, flawed pseudocode example (e.g., missing a decision condition or an infinite loop). Ask them to identify the error and suggest a correction in one sentence. This checks their ability to critique.

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

Activity 03

• Gallery Walk
• 50 min · Whole Class

Whole Class Algorithm Gallery Walk

Students create flowcharts or pseudocode for personal problems, like organizing homework. Post on walls. Class walks around, adds sticky notes with questions or fixes, then discusses in full group to refine top examples.

Critique the readability and completeness of a provided pseudocode example.

Facilitation Tip

Set clear time limits for the Whole Class Algorithm Gallery Walk to ensure students move purposefully and do not get stuck on any single example.

What to look for

In pairs, have students exchange their pseudocode for a given problem. Each student reviews their partner's pseudocode for clarity, logical flow, and completeness, providing one specific suggestion for improvement. This encourages active evaluation.

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

Activity 04

• Stations Rotation
• 25 min · Individual

Individual Debug Station

Provide flawed flowchart or pseudocode examples at stations. Students identify issues solo, redraw correctly, and explain changes in a quick journal entry before sharing one with the class.

Explain how flowcharts visually represent the flow of an algorithm.

Facilitation Tip

At the Individual Debug Station, place a timer for five minutes per station to maintain urgency and prevent students from over-analyzing minor errors.

What to look for

Provide students with a simple scenario, such as 'making a sandwich'. Ask them to draw a basic flowchart OR write pseudocode for the process. Collect these to check for understanding of basic sequencing and symbol usage.

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

A few notes on teaching this unit

Teach flowcharts and pseudocode as twin languages for the same ideas: flowcharts speak visually, pseudocode speaks plainly. Avoid starting with formal syntax rules, since rigid structures stifle creativity in early algorithm design. Instead, let students experiment with loose drafts, then refine as patterns emerge. Research shows that students grasp iteration and selection better when they first experience them through physical tracing and verbal explanation before moving to written forms.

By the end of these activities, students will turn written problems into clear visual or written steps without confusion. They will use the right symbols for flowcharts and keep pseudocode logical and readable. Missteps become visible early, so corrections happen while learning is still forming.

---

Watch Out for These Misconceptions

• During the Pair Challenge: Flowcharts only need boxes, no arrows.

  Ask pairs to swap flowcharts and trace the steps using only the arrows. When they realize arrows are missing, have them physically draw the missing connections in a different color before continuing.

• During the Small Group Pseudocode Relay: Pseudocode must use real programming syntax.

  Remind teams that pseudocode is informal language. If a group uses code-like syntax, ask them to read their draft aloud and replace any symbols or keywords with plain English phrases that maintain the same logic.

• During the Whole Class Algorithm Gallery Walk: All algorithms follow a straight line with no repeats.

  After viewing several examples, ask students to identify flowcharts or pseudocode that include loops or decisions. Have them circle the symbols or lines that create branches and explain their function to the class.

---

Methods used in this brief

• Stations Rotation
• Gallery Walk