Computing · Year 10

Active learning ideas

The Von Neumann Architecture

Active learning builds deep understanding by letting students manipulate physical and social models of the Von Neumann architecture. When learners construct components, role-play cycles, and simulate bottlenecks, they turn abstract concepts into memorable experiences that lectures alone cannot match.

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

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

Activity 01

• Chalk Talk
• 45 min · Small Groups

Model Building: Von Neumann Components

Provide cardstock, markers, and string. Students draw and label CPU, memory, I/O, and buses, then connect them. Groups simulate data flow by passing paper slips representing instructions between components.

Explain the significance of the stored program concept in modern computing.

Facilitation Tip

During Model Building: Von Neumann Components, walk the room to ask groups which part they think will become the bottleneck first and why they placed it where they did.

What to look for

Provide students with a simple diagram of the Von Neumann architecture. Ask them to label the main components (CPU, Memory, I/O, Buses) and write one sentence explaining the function of the Control Unit and one sentence describing the Von Neumann bottleneck.

• Understand
• Analyze
• Evaluate
• Self-Awareness
• Self-Management

Activity 02

• Chalk Talk
• 30 min · Pairs

Role-Play: Fetch-Execute Cycle

Assign roles: one student as memory holds instruction cards, another as CPU fetches, decodes, executes with props. Pairs rotate roles over 10 cycles, timing each to note bottlenecks.

Analyze how the Von Neumann bottleneck impacts system performance.

Facilitation Tip

During Role-Play: Fetch-Execute Cycle, call out a clock tick every 15 seconds so students feel the rhythm of fetch, decode, execute, and store.

What to look for

Present students with a scenario: 'A program needs to read data from a file and then perform a calculation on it.' Ask them to describe, in two steps, how the Von Neumann architecture would handle this task, referencing the fetch-execute cycle.

• Understand
• Analyze
• Evaluate
• Self-Awareness
• Self-Management

Activity 03

• Chalk Talk
• 35 min · Small Groups

Bottleneck Simulation: Queue Challenge

Use a single line of desks as the bus. Students pass instruction and data cards through it in turns. Measure time for multiple processes to show slowdown, then compare with parallel lines for Harvard.

Compare the Von Neumann architecture with alternative architectures like Harvard.

Facilitation Tip

During Bottleneck Simulation: Queue Challenge, rotate the role of traffic cop if the queue stalls to reinforce that shared access is the core issue.

What to look for

Pose the question: 'Imagine a computer that could fetch an instruction and data simultaneously. How might this differ from the Von Neumann architecture, and what potential performance benefits could it offer?' Facilitate a class discussion comparing this hypothetical to the Harvard architecture.

• Understand
• Analyze
• Evaluate
• Self-Awareness
• Self-Management

Activity 04

• Chalk Talk
• 40 min · Whole Class

Architecture Debate: Von Neumann vs Harvard

Divide class into teams. Provide pros/cons cards. Teams prepare 2-minute arguments on performance, cost, simplicity, then vote and discuss real-world examples like embedded systems.

Explain the significance of the stored program concept in modern computing.

Facilitation Tip

During Architecture Debate: Von Neumann vs Harvard, hand each side a one-paragraph summary of their opponent’s strongest point before they begin so arguments stay evidence-based.

What to look for

Provide students with a simple diagram of the Von Neumann architecture. Ask them to label the main components (CPU, Memory, I/O, Buses) and write one sentence explaining the function of the Control Unit and one sentence describing the Von Neumann bottleneck.

• Understand
• Analyze
• Evaluate
• Self-Awareness
• Self-Management

A few notes on teaching this unit

Start with a quick whole-class sketch of the architecture on the board, labeling only CPU, Memory, Buses, and I/O. Ask students to predict what happens if two things try to use the bus at once. This reveals prior knowledge before any activity begins. Avoid rushing the debrief; spend at least 10 minutes after each simulation to connect the physical actions back to real hardware behavior. Research shows that students who act out the fetch-execute cycle retain the sequence twice as well as those who simply hear it described.

Students will explain how instructions and data share memory, trace the fetch-execute cycle in real time, identify hardware trade-offs, and articulate why the shared bus creates delays. Their language will show they grasp dynamic loading, separation of roles, and performance impacts.

---

Watch Out for These Misconceptions

• During Model Building: Von Neumann Components, watch for students who place the program permanently inside the CPU.

  After they finish the model, ask each group to swap out the memory card for a new one. If they protest that the program is gone, point to the stored program concept and remind them that the program lives in main memory and can be replaced.

• During Bottleneck Simulation: Queue Challenge, watch for students who claim the bottleneck disappears in modern computers.

  During the debrief, time the queue again after adding a cache simulation (a separate quick queue). Ask students to compare the two timings and connect the speed difference to real-world cache use.

• During Architecture Debate: Von Neumann vs Harvard, watch for students who assume Harvard is always faster.

  Prompt the Harvard side to calculate the extra wires and pins required for separate data and instruction buses, then ask the class whether the speed gain justifies the cost in a smartphone versus a medical sensor.

---

Methods used in this brief

• Chalk Talk