Computing · Year 10

Active learning ideas

CPU: Fetch-Execute Cycle & Registers

Active learning turns the abstract Fetch-Execute cycle into something students can see and feel, replacing static diagrams with muscle memory. When learners physically step through each register’s role, the mechanical nature of the CPU becomes memorable long before exam season arrives.

• National Curriculum Attainment Targets
• GCSE: Computing - Computer Systems and Architecture

• 15–40 min
• Pairs → Whole Class
• 3 activities

Activity 01

• Role Play
• 40 min · Whole Class

Role Play: The Human CPU

Assign students roles such as the ALU, Control Unit, and specific registers like the MAR and MDR. Use physical cards as 'data' and have the class execute a simple addition program by physically moving the cards according to the Fetch-Execute cycle.

Analyze how the clock speed of a processor dictates the limits of software performance.

Facilitation Tip

During the Human CPU role play, give each student a small whiteboard so they can jot the value of their register after every step and hold it up for instant peer feedback.

What to look for

Present students with a short, simplified assembly-like code snippet. Ask them to trace the Fetch-Execute cycle for the first three instructions, specifically noting the state of the Program Counter and Accumulator after each instruction.

• Apply
• Analyze
• Evaluate
• Social Awareness
• Self-Awareness

Activity 02

• Formal Debate
• 30 min · Small Groups

Formal Debate: The Performance Paradox

Divide the class into teams representing 'High Clock Speed', 'Multi-core Architecture', and 'Large Cache'. Students must argue why their specific feature is the most important for different user scenarios, such as gaming versus video editing.

Compare the trade-offs between increasing cache size and adding more processing cores.

Facilitation Tip

In the Structured Debate, hand out sentence stems like ‘Higher clock speed improves… but at the cost of…’ to keep arguments focused on CPU architecture rather than brand loyalty.

What to look for

Pose the question: 'If you were designing a CPU for a smartphone, would you prioritize a very high clock speed or a larger cache? Justify your choice by explaining the trade-offs involved.'

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

Activity 03

• Think-Pair-Share
• 15 min · Pairs

Think-Pair-Share: Overclocking Risks

Students research the concept of overclocking and discuss the physical consequences for the hardware. They then pair up to list three pros and three cons before sharing their findings with the class to create a master list of CPU limitations.

Design a processor architecture to prioritize energy efficiency over raw speed.

Facilitation Tip

For the Think-Pair-Share on overclocking, provide a one-page datasheet with power draw and temperature curves so students quantify risks instead of relying on anecdotes.

What to look for

On an index card, have students define the term 'Fetch-Execute Cycle' in their own words and list two registers involved, stating the primary function of each.

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

A few notes on teaching this unit

Start with a brief live demo of a simple assembly instruction moving between registers before any role play begins. Research shows that seeing the cycle once in real time prevents students from treating registers as abstract icons. Avoid spending too much time on clock cycles or pipeline diagrams until students can explain why a single instruction needs fetch, decode, execute anyway. Keep the first concrete example to three instructions so the cognitive load is manageable.

Students will not just name registers but will explain how the Program Counter and Accumulator work together during each tick of the clock. By the end of the sequence they should trace a three-instruction program, predict register states, and justify design trade-offs in under two minutes.

---

Watch Out for These Misconceptions

• During the Structured Debate, watch for students asserting that doubling cores always doubles speed.

  Redirect the debate to the provided datasheet: ask them to compare single-threaded and multi-threaded benchmarks for the same CPU model so they see the software dependency firsthand.

• During the Human CPU role play, watch for students anthropomorphising the CPU by saying it 'understands' the data.

  Hand each student a printed two-line program and instruct them to follow the instructions blindly, without interpreting the values; this mechanical obedience makes the lack of semantic knowledge explicit.

---

Methods used in this brief

• Role Play
• Formal Debate
• Think-Pair-Share