Computational Thinking: Abstraction

Active learning works well for abstraction because students need to see how simplification removes complexity. When they manipulate real, tangible examples like maps or sandwiches, the mental shift from details to core function becomes visible and memorable.

• Year 10
• Computing
• 3 activities
• 15 min–25 min

Learning Objectives

1. Analyze the essential features of a complex system by identifying and excluding irrelevant details.
2. Design an abstract model representing a real-world scenario, clearly defining included and excluded elements.
3. Explain how abstraction simplifies problem-solving in large-scale software development.
4. Compare different levels of abstraction for a given problem, justifying the choice of detail.

Problem-Based Learning

⏱ 20 min·Small Groups

Decomposition Challenge: The Robot Sandwich

One student acts as a 'robot' who only follows literal instructions. The rest of the group must decompose the complex task of making a jam sandwich into tiny, logical steps to ensure the robot doesn't make a mess.

Prepare & details

Explain how abstraction helps manage complexity in large software projects.

Facilitation Tip: During the Robot Sandwich activity, circulate with a checklist of steps so students notice the difference between task instructions and actual robot actions.

Setup: Groups at tables with access to research materials

Materials: Problem scenario document, KWL chart or inquiry framework, Resource library, Solution presentation template

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

Gallery Walk

⏱ 25 min·Small Groups

Gallery Walk: Map Design

Display various maps (London Underground, a topographical map, a treasure map). Students move between stations to identify what information has been removed (abstracted) and why that makes the map more useful for its specific purpose.

Prepare & details

Analyze what information can be safely ignored when creating a model of a complex transit network.

Facilitation Tip: For the Map Design Gallery Walk, provide colored sticky notes for students to label features as 'essential' or 'ignore' while they move between stations.

Setup: Wall space or tables arranged around room perimeter

Materials: Large paper/poster boards, Markers, Sticky notes for feedback

• Understand
• Apply
• Analyze
• Create
• Relationship Skills
• Social Awareness

Think-Pair-Share

⏱ 15 min·Pairs

Think-Pair-Share: Pattern Recognition in Daily Life

Students identify repetitive patterns in their daily routines or in popular apps (like social media feeds). They pair up to discuss how these patterns could be turned into a general algorithm that works for everyone.

Prepare & details

Design an abstract model for a real-world system, justifying the elements included and excluded.

Facilitation Tip: In the Think-Pair-Share, give pairs only one minute each to share so quieter students have space to contribute before group discussion.

Setup: Standard classroom seating; students turn to a neighbor

Materials: Discussion prompt (projected or printed), Optional: recording sheet for pairs

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

Teaching This Topic

Teachers should model abstraction by thinking aloud as they strip down a problem in front of students. Avoid explaining abstraction in abstract terms—use concrete examples first, then connect them to programming concepts like functions or classes. Research shows that students grasp abstraction faster when they first practice it on familiar, non-digital tasks.

What to Expect

Students will articulate which details matter and which can be ignored in a given problem. They will justify their choices using clear criteria and connect abstraction to real-world examples beyond the classroom.

Watch Out for These Misconceptions

Common Misconception

During Abstraction Gallery Walk: Map Design, watch for students who think adding more labels makes a map better.

What to Teach Instead

Redirect them to focus on their sticky notes that identify which map features are essential for navigation versus those that can be omitted. Ask, 'If you gave this map to a tourist, which three things would they need to find the train station?'

Common Misconception

During Think-Pair-Share: Pattern Recognition in Daily Life, watch for students who equate abstraction with summarizing.

What to Teach Instead

Use the sandwich-making steps they wrote to show how abstraction removes steps entirely. Ask, 'Which step could a robot skip if we only care about the final sandwich being wrapped?'

Assessment Ideas

Discussion Prompt

After Decomposition Challenge: The Robot Sandwich, present the scenario of planning a school fair. Ask students to identify the most important things to consider for success and what details can be ignored for now. Listen for students who explicitly state which information was deemed unnecessary.

Quick Check

During Abstraction Gallery Walk: Map Design, provide students with a bicycle diagram and ask them to create a one-sentence description of its primary function. Collect their descriptions to check if they focused on transportation and omitted mechanical details.

Exit Ticket

After Think-Pair-Share: Pattern Recognition in Daily Life, ask students to write down one example of abstraction they encountered outside of computing that day. Collect their notes to verify they can explain what was simplified and what details were ignored.

Extensions & Scaffolding

• Challenge students to design an abstraction of a school timetable that a new student could understand in five minutes.
• For students who struggle, provide partially completed abstraction models with three details already highlighted.
• Deeper exploration: Have students compare two different abstractions of the same system and critique which one is more effective for a given audience.

Key Vocabulary

Abstraction	The process of simplifying complexity by focusing on essential characteristics and ignoring irrelevant details.
Model	A simplified representation of a system or concept, used to understand or predict its behavior.
Essential Detail	Information that is crucial for understanding or solving a problem and must be included in an abstraction.
Irrelevant Detail	Information that does not affect the core functionality or understanding of a problem and can be safely ignored during abstraction.