Computing · Year 10

Active learning ideas

Computational Thinking: Decomposition

Active learning lets students experience decomposition firsthand, turning abstract problem-solving into tangible skills. By manipulating real-world scenarios, Year 10 students internalise the value of breaking complexity into manageable parts, which is essential for GCSE Computing success.

• National Curriculum Attainment Targets
• GCSE: Computing - Computational Thinking and Algorithms

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

Activity 01

• Collaborative Problem-Solving
• 30 min · Pairs

Pairs: Recipe Breakdown

Students pair up and select a complex recipe, like baking a cake. They identify main stages such as preparation, mixing, and baking, then subdivide each into steps like measuring ingredients or preheating oven. Pairs create a hierarchical diagram and share one insight with the class.

How would you break down the process of autonomous driving into manageable sub-problems?

Facilitation Tip

During Recipe Breakdown, circulate and ask pairs to explain why they placed a step at a certain level, reinforcing hierarchical thinking.

What to look for

Provide students with a scenario, such as 'planning a large music festival.' Ask them to list three main sub-problems and then break down one of those sub-problems into two smaller tasks. Collect these to check for initial understanding of hierarchical breakdown.

• Apply
• Analyze
• Evaluate
• Create
• Relationship Skills
• Decision-Making
• Self-Management

Activity 02

• Collaborative Problem-Solving
• 45 min · Small Groups

Small Groups: Autonomous Driving Decomposition

Form small groups to tackle self-driving car systems. Groups list top-level functions like navigation and safety, then break them into sub-problems such as GPS integration or pedestrian detection. They draw mind maps and discuss integration challenges before presenting.

Construct a decomposition plan for designing a new mobile application.

Facilitation Tip

For Autonomous Driving Decomposition, provide a clear template for recording sub-problems to prevent students from reverting to flat lists.

What to look for

Pose the question: 'Imagine you are building a robot that can sort recycling. How would you decompose this task?' Facilitate a class discussion where students share their decomposition strategies, focusing on identifying the benefits and potential challenges of their chosen approaches.

• Apply
• Analyze
• Evaluate
• Create
• Relationship Skills
• Decision-Making
• Self-Management

Activity 03

• Collaborative Problem-Solving
• 50 min · Whole Class

Whole Class: Mobile App Design Plan

As a whole class, brainstorm a new app idea like a study planner. Teacher facilitates dividing it into features, user flows, and data needs. Students contribute sub-problems on sticky notes, then vote to organise into a shared decomposition chart.

Evaluate the benefits of decomposition for collaborative problem-solving.

Facilitation Tip

In Mobile App Design Plan, assign roles within groups so every student contributes to a specific layer of the decomposition.

What to look for

Present students with a pre-decomposed problem (e.g., a flowchart showing a simple app's features broken down). Ask them to identify one task that could be further decomposed and explain why. This checks their ability to recognize opportunities for deeper breakdown.

• Apply
• Analyze
• Evaluate
• Create
• Relationship Skills
• Decision-Making
• Self-Management

Activity 04

• Collaborative Problem-Solving
• 35 min · Individual

Individual: Personal Project Hierarchy

Students individually decompose a personal goal, such as organising a gaming tournament. They outline main components and sub-tasks in a flowchart. Follow with pairs swapping to suggest improvements, then class gallery walk for feedback.

How would you break down the process of autonomous driving into manageable sub-problems?

Facilitation Tip

During Personal Project Hierarchy, model your own decomposition process aloud to make the thinking visible.

What to look for

Provide students with a scenario, such as 'planning a large music festival.' Ask them to list three main sub-problems and then break down one of those sub-problems into two smaller tasks. Collect these to check for initial understanding of hierarchical breakdown.

• Apply
• Analyze
• Evaluate
• Create
• Relationship Skills
• Decision-Making
• Self-Management

A few notes on teaching this unit

Teach decomposition as a recursive skill, not a linear one. Research shows students benefit from seeing multiple examples of the same problem decomposed in different ways. Avoid rushing to solutions; instead, encourage students to critique each other’s hierarchies to expose gaps. Explicitly link sub-problems back to the whole to reinforce integration, a common pitfall in early attempts.

Students will confidently decompose problems into layered sub-tasks, explain the purpose of each layer, and reassemble components into a coherent solution. They will also transfer these skills to non-coding contexts, demonstrating versatility in their approach.

---

Watch Out for These Misconceptions

• During Recipe Breakdown, watch for students listing steps in a flat sequence instead of grouping related actions into sub-problems.

  Use the recipe cards to model tiered grouping, such as separating 'gather ingredients' from 'mix ingredients' and then 'bake.' Ask students to physically stack related steps to visualise hierarchy.

• During Autonomous Driving Decomposition, watch for students treating sensing, decision-making, and control as equal, independent tasks without showing dependencies.

  Direct students to draw arrows between layers to indicate data flow, such as sensor data feeding into decision-making. Use the template’s connector spaces to make these relationships explicit.

• During Mobile App Design Plan, watch for students decomposing only the user interface and ignoring backend logic or data storage.

  Provide a list of app components (e.g., login screen, database, API) and ask groups to assign each to a layer. Circulate and prompt them to justify why each component belongs where it does.

---

Methods used in this brief

• Collaborative Problem-Solving