Skip to content
Computing · Secondary 4

Active learning ideas

The Central Processing Unit (CPU)

Active learning transforms abstract CPU concepts into tangible experiences. Students grasp the fetch-decode-execute cycle faster through movement and hands-on simulations, while concrete models of clock speed and cores make theoretical specs meaningful. This approach builds lasting understanding by connecting ideas to real-world performance outcomes.

MOE Syllabus OutcomesMOE: Computer Architecture - S4MOE: Computer Systems - S4
25–40 minPairs → Whole Class4 activities

Activity 01

Think-Pair-Share30 min · Small Groups

Role-Play: Fetch-Decode-Execute Cycle

Assign roles in small groups: one as memory holding instruction cards, one as fetch unit, one as decoder, and one as executor with props for operations. Groups run 10 sample instructions, timing each cycle and noting bottlenecks. Debrief on how speed affects throughput.

Explain the primary functions of the Central Processing Unit.

Facilitation TipFor the role-play, assign students distinct roles (fetch, decode, execute) with props like index cards for instructions to make the process visible to the class.

What to look forPresent students with two hypothetical CPU specifications (e.g., CPU A: 3.5 GHz, 4 cores; CPU B: 4.0 GHz, 2 cores). Ask them to write which CPU would be better for gaming and which for running many background applications, justifying their choices.

UnderstandApplyAnalyzeSelf-AwarenessRelationship Skills
Generate Complete Lesson

Activity 02

Simulation Game40 min · Pairs

Simulation Game: CPU Clock Speed Tweaks

Pairs use free online CPU simulators to run tasks at different GHz speeds, recording completion times. They graph results and discuss heat implications. Extend by comparing single-core vs multi-core runs on the same tasks.

Analyze how clock speed and core count impact CPU performance.

Facilitation TipIn the simulation activity, provide pre-set clock speeds and core configurations on cards so students can systematically test CPU performance differences.

What to look forFacilitate a class discussion using the prompt: 'Imagine you are building a computer for a specific purpose (e.g., video editing, basic web browsing, scientific research). What CPU characteristics (clock speed, core count) would be most critical for your chosen task, and why?'

ApplyAnalyzeEvaluateCreateSocial AwarenessDecision-Making
Generate Complete Lesson

Activity 03

Think-Pair-Share35 min · Small Groups

Model Building: Multi-Core Processor

Small groups construct paper or LEGO models of a 4-core CPU, assigning threads to cores and simulating parallel execution with colored tokens. They race models against single-core versions for sample workloads. Share findings on efficiency gains.

Predict the limitations of a computer system with a slow or inefficient CPU.

Facilitation TipWhen building multi-core models, use interlocking blocks or labeled paper sections so students can physically separate and recombine cores for clear visualization.

What to look forAsk students to write down the three main stages of the fetch-decode-execute cycle and briefly describe what happens in each stage. Additionally, have them identify one component of the CPU responsible for calculations.

UnderstandApplyAnalyzeSelf-AwarenessRelationship Skills
Generate Complete Lesson

Activity 04

Case Study Analysis25 min · Whole Class

Case Study Analysis: Real CPU Benchmarks

Whole class reviews benchmark data from sites like PassMark for CPUs varying in speed and cores. In pairs, predict performance for gaming vs office tasks, then verify. Discuss predictions in plenary.

Explain the primary functions of the Central Processing Unit.

Facilitation TipDuring the case study, assign each group a different CPU benchmark to research, then have them present findings to compare real-world performance.

What to look forPresent students with two hypothetical CPU specifications (e.g., CPU A: 3.5 GHz, 4 cores; CPU B: 4.0 GHz, 2 cores). Ask them to write which CPU would be better for gaming and which for running many background applications, justifying their choices.

AnalyzeEvaluateCreateDecision-MakingSelf-Management
Generate Complete Lesson

A few notes on teaching this unit

Start with the role-play to establish the fetch-decode-execute cycle as a physical process. Move to simulations to quantify performance, using timers to measure how changes in clock speed or core count affect speed. Avoid diving too deeply into architecture details before students grasp the cycle. Research shows that students retain conceptual knowledge better when they experience the process before analyzing its components. Encourage peer teaching during model-building to reinforce understanding through explanation.

Students will confidently explain how the CPU processes instructions through the fetch-decode-execute cycle. They will analyze trade-offs between clock speed and core count by comparing performance in simulations and justifying choices in discussions. Misconceptions will be corrected through peer feedback and teacher-led demonstrations.


Watch Out for These Misconceptions

  • During the simulation activity, watch for students assuming a 5.0 GHz CPU always outperforms a 3.0 GHz CPU in every task.

    Use the simulation’s timed comparisons to have students run the same multi-threaded task (e.g., opening 10 browser tabs) on both CPUs. Ask them to record completion times and discuss why the higher-clock-speed CPU may not finish first.

  • During the role-play activity, watch for students thinking the CPU operates independently of other components.

    Pause the role-play mid-cycle to ask, 'What happens if the instructions from RAM are delayed?' Have students physically demonstrate the delay by passing index cards slowly, then discuss how cache or RAM speed affects CPU performance.

  • During the model-building activity, watch for students believing each additional core doubles processing speed automatically.

    Provide a worksheet with a graph template where students plot core count against a hypothetical performance metric. After building their models, have them mark where real-world performance plateaus and discuss the role of software optimization in the results.


Methods used in this brief