Computer Science · Grade 10

Active learning ideas

Flowcharts and Pseudocode

Active learning builds students' confidence in planning algorithms by doing, not just listening. Flowcharts and pseudocode become tangible tools when students create them themselves, helping them see how structure clarifies logic before coding begins.

• Ontario Curriculum Expectations
• CS.HS.A.1
• CS.HS.A.2

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

Activity 01

• Stations Rotation
• 30 min · Pairs

Pairs: Morning Routine Flowchart

Students pair up and create a flowchart for their morning routine, including decisions like 'Did I wake up on time?'. Partners review each other's charts for missing loops or decisions, then revise together. Share one example per pair with the class.

Construct a flowchart to represent a given problem's solution.

Facilitation Tip

For Morning Routine Flowchart, provide sticky notes so pairs can rearrange steps before committing to the final flowchart, reinforcing iterative design.

What to look for

Present students with a simple scenario, like 'making a sandwich'. Ask them to write 3-5 lines of pseudocode describing the steps. Then, have them draw the corresponding flowchart, ensuring correct symbol usage for start, end, process, and decision steps.

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

Activity 02

• Stations Rotation
• 45 min · Small Groups

Small Groups: Pseudocode Translator

Provide pseudocode for a number guessing game. Groups translate it into a flowchart, test paths with sample inputs, and identify improvements. Groups present their flowcharts and explain choices to the class.

Translate a simple algorithm from pseudocode into a flowchart and vice versa.

Facilitation Tip

During Pseudocode Translator, ask groups to swap their pseudocode with another table to translate it into a flowchart, creating natural peer-teaching moments.

What to look for

Facilitate a class discussion: 'Imagine you are on a team designing a new app. One programmer prefers only flowcharts, another only pseudocode. What are the strengths and weaknesses of each approach in a collaborative environment? How could you use both effectively?'

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

Activity 03

• Stations Rotation
• 35 min · Whole Class

Whole Class: Flawed Algorithm Hunt

Display a buggy flowchart and pseudocode on the board. Class discusses errors as a group, votes on fixes, and redraws the corrected versions together. Follow with individual practice on similar examples.

Evaluate the benefits of using pseudocode and flowcharts in the design phase of programming.

Facilitation Tip

In Flawed Algorithm Hunt, assign each small group one flowchart to analyze, then have them present their corrections to the class to build collective scrutiny skills.

What to look for

Provide students with a pre-made flowchart for a simple algorithm (e.g., checking if a number is even or odd). Ask them to write the equivalent pseudocode. On the back, have them list one benefit of using flowcharts and one benefit of using pseudocode for this specific algorithm.

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

Activity 04

• Stations Rotation
• 25 min · Individual

Individual: Shopping List Algorithm

Students write pseudocode for sorting a shopping list by category, then convert to a flowchart. Self-assess using a rubric for completeness and logic before submitting.

Construct a flowchart to represent a given problem's solution.

Facilitation Tip

For Shopping List Algorithm, provide a partially filled flowchart template so students focus on decision symbols rather than symbol recall.

What to look for

Present students with a simple scenario, like 'making a sandwich'. Ask them to write 3-5 lines of pseudocode describing the steps. Then, have them draw the corresponding flowchart, ensuring correct symbol usage for start, end, process, and decision steps.

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

A few notes on teaching this unit

Teach flowcharts and pseudocode as complementary tools, not competing ones. Start with concrete examples students recognize, like morning routines, then gradually introduce decisions and variables. Avoid overwhelming students with too many symbols at once. Research shows hands-on construction cements understanding more than lectures alone.

Successful learning looks like students justifying their flowchart choices, translating logic between formats without syntax errors, and recognizing how early planning prevents bigger problems later. They should explain why clear steps matter in real design work.

---

Watch Out for These Misconceptions

• During Flawed Algorithm Hunt, watch for students assuming the flawed flowchart is completely wrong. Correction: Ask groups to identify which parts of the flawed flowchart still work, then modify it together, teaching that flowcharts can be improved rather than discarded.

  During Shopping List Algorithm, watch for students treating decisions as linear steps. Correction: Provide a scenario with multiple possible outcomes, like 'if the store has eggs, buy them,' and have students draw the diamond symbol with two branches to practice branching logic.

---

Methods used in this brief

• Stations Rotation