Computing · Year 7

Active learning ideas

The Fetch-Decode-Execute Cycle

Active learning works well for the Fetch-Decode-Execute cycle because students often struggle with abstract hardware processes. Moving through stations, sorting cards, and running simulations makes the invisible steps visible, turning confusion into clear understanding through physical participation.

• National Curriculum Attainment Targets
• KS3: Computing - Computer Systems

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

Activity 01

• Simulation Game
• 45 min · Small Groups

Role-Play: CPU Stations

Assign roles: one student as memory holding instruction cards, one as program counter, one as control unit for decode, and one as ALU for execute. Groups practice 5-10 cycles with simple instructions like ADD 2+3. Rotate roles after each round and discuss bottlenecks observed.

Explain the steps involved in the Fetch-Decode-Execute cycle.

Facilitation Tip

During the CPU Stations role-play, circulate and time each group to highlight how speed creates the illusion of parallel processing.

What to look for

Provide students with a simple flowchart of the Fetch-Decode-Execute cycle. Ask them to label each stage and write one key action that happens during that stage in their own words.

• Apply
• Analyze
• Evaluate
• Create
• Social Awareness
• Decision-Making

Activity 02

• Simulation Game
• 30 min · Pairs

Card Sort: Cycle Flowchart

Provide jumbled cards showing fetch, decode, execute steps with descriptions and diagrams. In pairs, students sequence them into a flowchart, then test by 'running' a short program. Add extension cards for branching or interrupts.

Analyze how each stage of the cycle contributes to program execution.

Facilitation Tip

For the Cycle Flowchart card sort, provide red and green pens so students can mark correct and incorrect connections during peer review.

What to look for

Pose the question: 'Imagine the Decode stage suddenly takes 100 times longer than usual. What would happen to a program running on the computer? Explain your reasoning, referring to the cycle.'

• Apply
• Analyze
• Evaluate
• Create
• Social Awareness
• Decision-Making

Activity 03

• Simulation Game
• 50 min · Whole Class

Unplugged Simulation: Instruction Runner

Students create paper CPU models with registers and memory slots. Whole class follows teacher-led instructions, timing cycles for simple programs. Compare times with 'faulty' stages to predict performance impacts.

Predict the impact of a bottleneck in one stage of the cycle on overall performance.

Facilitation Tip

In the Instruction Runner unplugged simulation, give each student a role card that clearly lists their actions for one stage to prevent overlap.

What to look for

Students write down the three main stages of the Fetch-Decode-Execute cycle. For each stage, they must list one component of the CPU primarily responsible for that stage (e.g., Program Counter for Fetch).

• Apply
• Analyze
• Evaluate
• Create
• Social Awareness
• Decision-Making

Activity 04

• Simulation Game
• 40 min · Pairs

Blockly Challenge: Cycle Visualizer

Use online block-based tools to drag fetch-decode-execute blocks into loops. Students build and run mini-programs, observing step-by-step execution highlights. Pairs predict and log cycle counts for different tasks.

Explain the steps involved in the Fetch-Decode-Execute cycle.

Facilitation Tip

In the Blockly Challenge, model one complete cycle on the board before students start to reduce frustration with the tool.

What to look for

Provide students with a simple flowchart of the Fetch-Decode-Execute cycle. Ask them to label each stage and write one key action that happens during that stage in their own words.

• Apply
• Analyze
• Evaluate
• Create
• Social Awareness
• Decision-Making

A few notes on teaching this unit

Teach this topic by moving from concrete to abstract, starting with unplugged simulations and role-plays before introducing visualizers. Avoid overwhelming students with jargon; focus on the function of each stage first. Research shows that physical movement and multi-sensory input improve retention of sequential processes, so prioritize activities where students embody the cycle rather than just observe it.

By the end of these activities, students will articulate the sequential nature of the cycle and identify the role of each stage. They will also correct common misconceptions through peer interaction and hands-on modeling, demonstrating both conceptual clarity and collaborative problem-solving.

---

Watch Out for These Misconceptions

• During the CPU Stations role-play, watch for students assuming all instructions are processed simultaneously despite being spread across the room.

  Use a timer to measure how long each group takes to complete one cycle. Ask students to calculate how many cycles would occur in one second if the class acted as one CPU, highlighting the sequential and rapid nature of the process.

• During the Cycle Flowchart card sort, watch for students treating the fetch stage as a one-time event rather than a repeating step.

  Include multiple identical instruction cards in the sort and have students physically loop the fetch stage back to the start to demonstrate repetition. Ask them to count how many times fetch occurs for a program with three instructions.

• During the Instruction Runner unplugged simulation, watch for students blending the decode and execute stages into a single action.

  Assign separate students to the decode and execute roles for the same instruction. Have them practice their parts in slow motion first, then speed up to show the clear separation between interpreting and performing the instruction.

---

Methods used in this brief

• Simulation Game