Computing · JC 1

Active learning ideas

Standard Algorithms (Searching and Sorting)

Active learning works for this topic because problem decomposition and abstraction require students to wrestle with concrete examples, not just listen to definitions. When students physically break apart problems or strip away details, they internalize these skills in ways that passive study cannot match. These hands-on tasks also surface the cognitive conflicts that reveal misconceptions early, so you can address them before they take root.

• MOE Syllabus Outcomes
• 9569 1.2.1 Implement standard searching algorithms
• 9569 1.2.2 Implement standard sorting algorithms

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

Activity 01

• Think-Pair-Share
• 30 min · Pairs

Think-Pair-Share: Decompose a Game Level

Present a simple game scenario like navigating a maze. Students think individually for 3 minutes on sub-problems (pathfinding, obstacles, scoring). Pairs discuss and list 4-5 sub-problems, then share with class for voting on best decompositions. End with class refinement.

How does binary search improve upon linear search?

Facilitation Tip

During the Think-Pair-Share activity, circulate and listen for students who use vague terms like 'it needs to work better' and redirect them to name specific sub-problems like 'detect collision' or 'update score'.

What to look for

Present students with a scenario, such as planning a school event. Ask them to: 1. List three sub-problems they would decompose the event into. 2. Identify one detail they would abstract away and explain why it's not essential for the initial planning.

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

Activity 02

• Stations Rotation
• 45 min · Small Groups

Stations Rotation: Abstraction Levels

Set up stations with a problem like sorting student records. Station 1: full details (names, IDs, grades). Station 2: abstract to data types. Station 3: core logic (compare, swap). Station 4: pseudocode. Groups rotate, documenting changes at each.

What are the differences between bubble, insertion, and quick sort?

Facilitation Tip

In the Station Rotation, place a timer at each station to keep groups focused on the abstraction task at hand, not lingering on irrelevant details.

What to look for

Pose the question: 'What are the risks of oversimplifying a problem during the abstraction process?' Facilitate a class discussion, prompting students to provide specific examples of how oversimplification could lead to errors or incomplete solutions in software development or system design.

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

Activity 03

• Jigsaw
• 50 min · Small Groups

Jigsaw: Project Decomposition

Divide a large task like building a chat app into expert roles (UI, messaging, storage). Each small group masters one part, then reforms to teach and integrate. Students create a decomposition diagram.

How do we evaluate the efficiency of these algorithms?

Facilitation Tip

For the Jigsaw activity, assign each expert group a different project artifact (e.g., flowchart, data table) so they see how decomposition cuts across formats.

What to look for

Provide students with a pseudocode snippet for a simple algorithm (e.g., calculating average score). Ask them to identify which parts represent decomposed steps and which represent abstracted concepts. Then, ask them to explain one detail that could be abstracted further.

• Understand
• Analyze
• Evaluate
• Relationship Skills
• Self-Management

Activity 04

• Stations Rotation
• 25 min · Individual

Individual Pseudocode Challenge

Give a real-world problem like library book search. Students decompose alone, abstract to pseudocode, then pair to critique and improve. Collect for class gallery walk.

How does binary search improve upon linear search?

Facilitation Tip

When reviewing pseudocode solutions in the Individual Pseudocode Challenge, ask students to label each line with whether it is a decomposed step or an abstracted concept.

What to look for

Present students with a scenario, such as planning a school event. Ask them to: 1. List three sub-problems they would decompose the event into. 2. Identify one detail they would abstract away and explain why it's not essential for the initial planning.

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

A few notes on teaching this unit

Experienced teachers approach this topic by modeling how to zoom in and out of problems, not just assigning decomposition tasks. They use real-world analogies, like comparing problem-solving to planning a meal where you first decide what to cook (abstraction) then list the steps (decomposition). Avoid teaching abstraction as a standalone concept; integrate it into every modeling activity so students see its purpose. Research shows that students benefit from seeing multiple examples of the same problem decomposed in different ways, so vary your examples to highlight flexible thinking.

Successful learning looks like students confidently breaking problems into meaningful parts without over-splitting, and identifying which details matter for solving the core task. You will see them using abstraction to focus on essential logic, such as timing intervals instead of exact color names in a traffic light model. Evidence of mastery appears in their ability to explain why certain details were removed and how that clarity helps manage larger projects.

---

Watch Out for These Misconceptions

• During the Think-Pair-Share activity, watch for students who assume decomposition means breaking problems into the smallest possible pieces.

  Prompt them to reflect on their broken-down problems during the pair discussion: ask, 'Does this step still feel manageable, or has it become too small?' Have students test their breakdowns on a sample problem like planning a party to see if smaller steps complicate the plan instead of simplifying it.

• During the Station Rotation activity, watch for students who treat abstraction as removing all details equally.

  Ask groups to present their abstraction choices and explain why some details were kept (e.g., state changes) while others were removed (e.g., exact color names). Use the station’s modeling materials to visually compare abstractions and highlight when key elements like error handling get overlooked.

• During the Jigsaw activity, watch for students who believe decomposition and abstraction only apply to coding, not planning.

  Have expert groups focus on planning artifacts like flowcharts or data tables, and require them to explain how their chosen decomposition and abstraction choices guide the initial design phase. After the activity, ask them to reflect on how these skills reduced potential rework in their planning process.

---

Methods used in this brief

• Think-Pair-Share
• Stations Rotation
• Jigsaw