Computing · Secondary 4

Active learning ideas

How the CPU Works: Instructions and Processing

Active learning works for this topic because the fetch-decode-execute cycle is a mechanical process that benefits from physical movement and visual modeling. Students retain the timing and coordination of components better when they simulate the steps themselves rather than passively observe diagrams.

• MOE Syllabus Outcomes
• MOE: Computer Architecture - S4
• MOE: Computer Systems - S4

• 25–40 min
• Pairs → Whole Class
• 4 activities

Activity 01

• Simulation Game
• 35 min · Small Groups

Role-Play: Fetch-Decode-Execute Teams

Divide class into groups with roles: one as memory holding instruction cards, one as program counter, one as decoder, and one as executor with props like calculators. Groups practice full cycles on sample instructions like ADD or LOAD, then rotate roles. Debrief on coordination challenges.

Explain the basic steps a CPU takes to carry out an instruction.

Facilitation Tip

During Role-Play: Fetch-Decode-Execute Teams, assign each student a role and have them physically move through stations to simulate the cycle.

What to look for

Present students with a simplified diagram of the fetch-decode-execute cycle. Ask them to label each stage and write one sentence describing the primary action occurring at that stage.

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

Activity 02

• Simulation Game
• 25 min · Pairs

Card Trace: Instruction Pipeline

Provide decks of cards showing instructions and steps. Pairs lay out a sequence, simulate fetching by drawing cards, decoding by matching symbols, and executing by noting results. Extend by adding branches to show control flow.

How does the CPU know what to do next?

Facilitation Tip

Use Card Trace: Instruction Pipeline to visibly track how instructions progress through stages, highlighting delays and dependencies.

What to look for

Pose the question: 'Imagine a CPU is like a chef following a recipe. Which part of the CPU is the chef, which is the recipe book, and which are the ingredients?' Facilitate a class discussion to connect CPU components to this analogy.

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

Activity 03

• Simulation Game
• 40 min · Small Groups

Block Build: CPU Model

Students use interlocking blocks to represent registers, ALU, control unit, and memory. In small groups, assemble the model and walk through processing a calculation like 2+3, moving blocks to mimic data flow. Test with varied instructions.

Analyze how different parts of the CPU might work together to perform a calculation.

Facilitation Tip

In Block Build: CPU Model, require students to label components and demonstrate how data flows between them.

What to look for

Students receive a card with a single instruction (e.g., 'ADD R1, R2'). Ask them to write down the sequence of actions the CPU would take to process this instruction, naming the key components involved in each step.

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

Activity 04

• Simulation Game
• 30 min · Pairs

Simulator Run: Online CPU Trace

Use a web-based CPU simulator. Individually or in pairs, input assembly code, step through cycles, and record register changes. Class shares traces to compare simple vs. looped instructions.

Explain the basic steps a CPU takes to carry out an instruction.

What to look for

Present students with a simplified diagram of the fetch-decode-execute cycle. Ask them to label each stage and write one sentence describing the primary action occurring at that stage.

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

A few notes on teaching this unit

Teachers should emphasize the sequential nature of the cycle while gently introducing parallelism concepts later. Avoid overwhelming students with low-level details about microcode or pipelining stalls. Research suggests that concrete, step-by-step modeling builds the strongest foundation before abstracting to more complex scenarios.

Successful learning looks like students accurately describing the sequence of steps in the fetch-decode-execute cycle and explaining how components like the program counter, control unit, and ALU interact. They should also recognize the role of the clock signal in pacing these operations.

---

Watch Out for These Misconceptions

• During Role-Play: Fetch-Decode-Execute Teams, watch for students assuming all instructions execute simultaneously. Redirect by timing each role and emphasizing the handoff between stages.

  Pause the role-play after each instruction to point out how the program counter advances only after the execute stage completes, reinforcing sequential processing.

• During Card Trace: Instruction Pipeline, watch for students believing the CPU stores the entire program internally. Redirect by having them trace instructions back to a 'memory' pile after each cycle.

  Label a 'main memory' area and require students to return instructions there after decoding, making the separation of memory and processor explicit.

• During Block Build: CPU Model, watch for students assigning all operations to the ALU. Redirect by assigning the control unit a visible 'director' role in their models.

  Ask students to create a flowchart within their model showing the control unit directing the ALU, registers, and program counter during each step.

---

Methods used in this brief

• Simulation Game