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.

• Year 10
• Computing
• 4 activities
• 30 min–50 min

Learning Objectives

1. Analyze a complex real-world problem and identify at least three distinct sub-problems that can be addressed independently.
2. Design a decomposition plan for a given scenario, clearly outlining the hierarchical breakdown of tasks.
3. Evaluate the effectiveness of different decomposition strategies for improving collaborative problem-solving efficiency.
4. Compare and contrast the decomposition approaches used in two different software development projects.

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.

Prepare & details

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.

Setup: Groups at tables with problem materials

Materials: Problem packet, Role cards (facilitator, recorder, timekeeper, reporter), Problem-solving protocol sheet, Solution evaluation rubric

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

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.

Prepare & details

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.

Setup: Groups at tables with problem materials

Materials: Problem packet, Role cards (facilitator, recorder, timekeeper, reporter), Problem-solving protocol sheet, Solution evaluation rubric

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

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.

Prepare & details

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.

Setup: Groups at tables with problem materials

Materials: Problem packet, Role cards (facilitator, recorder, timekeeper, reporter), Problem-solving protocol sheet, Solution evaluation rubric

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

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.

Prepare & details

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.

Setup: Groups at tables with problem materials

Materials: Problem packet, Role cards (facilitator, recorder, timekeeper, reporter), Problem-solving protocol sheet, Solution evaluation rubric

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

Teaching This Topic

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.

What to Expect

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

Common Misconception

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

What to Teach Instead

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.

Common Misconception

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

What to Teach Instead

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.

Common Misconception

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

What to Teach Instead

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.

Assessment Ideas

Exit Ticket

After Recipe Breakdown, collect each pair’s final decomposition map and check that it includes at least two sub-levels beneath the main steps. Look for clear grouping and hierarchy.

Discussion Prompt

During Autonomous Driving Decomposition, ask groups to present their layered breakdown and explain how changes in one layer (e.g., sensor accuracy) would impact another. Listen for references to dependencies and integration.

Quick Check

After Mobile App Design Plan, display one group’s decomposition publicly and ask the class to identify one task that could be further broken down. Collect responses on mini whiteboards to gauge recognition of deeper levels.

Extensions & Scaffolding

• Challenge: Ask students to decompose a GCSE Computing past paper question into sub-problems and compare their hierarchy with a peer.
• Scaffolding: Provide a partially completed decomposition table for the Autonomous Driving activity to guide students who struggle with starting points.
• Deeper exploration: Invite students to research how decomposition is used in software engineering (e.g., Agile sprints) and present their findings to the class.

Key Vocabulary

Decomposition	The process of breaking down a complex problem or system into smaller, more manageable parts. This makes the problem easier to understand, solve, and manage.
Sub-problem	A smaller, simpler problem that is part of a larger, more complex problem. Solving sub-problems contributes to solving the main problem.
Hierarchical structure	An arrangement of items in levels, where each level represents a different degree of scope or detail. Decomposition often results in a hierarchical breakdown of tasks.
Modularity	The degree to which a system's components may be separated and recombined. Decomposition promotes modularity, allowing parts of a system to be developed or replaced independently.