Computing · Secondary 3

Active learning ideas

Converting Flowcharts to Pseudocode

Active learning works because translating flowcharts to pseudocode demands students move between visual and textual logic. By handling symbols and writing steps, they internalize how structure serves meaning, which reduces errors in later programming tasks.

• MOE Syllabus Outcomes
• MOE: Algorithms - S3

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

Activity 01

• Numbered Heads Together
• 30 min · Pairs

Pair Mapping Relay: Symbol Translation

Provide pairs with flowcharts using 4-5 symbols. Student A traces one path and writes pseudocode snippet; Student B verifies and extends to next path. Switch roles after two paths, then compare full versions for equivalence. Debrief as a class on tricky symbols.

Analyze how a specific flowchart symbol translates into pseudocode syntax.

Facilitation Tip

During Pair Mapping Relay, circulate to listen for students debating why a rectangle becomes an assignment statement, not an output.

What to look for

Provide students with a simple flowchart containing 3-4 symbols. Ask them to write the corresponding pseudocode on their exit ticket. Check for accurate translation of each symbol's function and correct syntax.

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

Activity 02

• Numbered Heads Together
• 45 min · Small Groups

Small Group Flowchart Scramble: Rebuild and Code

Give groups jumbled flowchart pieces for a simple algorithm like finding maximum number. First, reassemble into correct flow, then convert to pseudocode collaboratively. Groups present their version; class votes on most accurate.

Construct pseudocode that accurately reflects the logic of a given flowchart.

Facilitation Tip

For Small Group Flowchart Scramble, provide sticky notes so groups can rearrange symbols before writing pseudocode.

What to look for

Display a flowchart on the projector. Ask students to individually write down the pseudocode for a specific section or decision point. Review answers as a class, discussing any common errors in translation.

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

Activity 03

• Numbered Heads Together
• 25 min · Whole Class

Whole Class Equivalence Hunt: Spot the Mismatch

Project a flowchart beside three pseudocode options. Students hold up fingers (1,2,3) to vote on match. Discuss mismatches in branches or loops, then revise as a group on whiteboard.

Evaluate the equivalence of a flowchart and its corresponding pseudocode representation.

Facilitation Tip

In Whole Class Equivalence Hunt, ask volunteers to trace arrows aloud while others confirm if pseudocode matches the flowchart’s branches.

What to look for

Students work in pairs, each creating a flowchart for a simple task (e.g., making toast). They then exchange flowcharts and write the pseudocode for their partner's flowchart. Partners review each other's pseudocode for accuracy against the original flowchart.

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

Activity 04

• Numbered Heads Together
• 35 min · Individual

Individual Practice to Peer Review: Loop Challenges

Students convert solo a flowchart with nested loops to pseudocode. Pair up to swap and critique using a checklist for syntax and logic paths. Revise based on feedback.

Analyze how a specific flowchart symbol translates into pseudocode syntax.

Facilitation Tip

During Individual Practice to Peer Review, distribute colored pens so reviewers can annotate pseudocode directly next to flowchart symbols.

What to look for

Provide students with a simple flowchart containing 3-4 symbols. Ask them to write the corresponding pseudocode on their exit ticket. Check for accurate translation of each symbol's function and correct syntax.

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

A few notes on teaching this unit

Teach this by modeling how to read flowcharts aloud, pausing at each symbol to ask, 'What does this arrow tell the next step?' Avoid rushing to code syntax; focus first on the logic’s direction. Research shows students grasp loops better when they physically walk through pretest versus post-test conditions on a whiteboard before writing pseudocode.

Successful learning looks like students accurately mapping flowchart symbols to pseudocode keywords, maintaining the original logic’s flow and decisions without skipping steps. They should also explain their choices to peers, showing they understand why syntax follows the visual path.

---

Watch Out for These Misconceptions

• During Pair Mapping Relay, watch for students adding semicolons or Python keywords like 'elif' in pseudocode.

  Prompt them to compare their drafts to the class’s agreed-upon pseudocode template, emphasizing that pseudocode uses plain English such as 'ELSE IF' without punctuation.

• During Small Group Flowchart Scramble, watch for students always using FOR loops for any repeated block.

  Have groups present their loop choice and trace the condition’s location in the flowchart, reinforcing that WHILE matches pretest conditions and DO-WHILE matches post-test.

• During Whole Class Equivalence Hunt, watch for students reordering steps to match linear pseudocode expectations.

  Stop the class to physically point to each arrow while students read their pseudocode aloud, forcing them to follow the flowchart’s directional logic.

---

Methods used in this brief

• Numbered Heads Together