Computing · Year 6

Active learning ideas

The World Wide Web: Clients and Servers

Active learning works for this topic because the client-server model is invisible to learners yet foundational to how the web operates. When students physically act out requests, responses, and rendering, they build durable mental models that static explanations cannot create.

• National Curriculum Attainment Targets
• KS2: Computing - Computer Systems and Networks

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

Activity 01

• Role Play
• 35 min · Small Groups

Role Play: Client-Server Restaurant

Divide the class into clients who place orders (URLs) with waiters, who relay to kitchen servers preparing dishes (web files). Servers deliver components back through waiters for clients to assemble meals. Debrief on delays or errors to mirror real networks. Rotate roles twice.

Explain the relationship between a client and a server in accessing a website.

Facilitation Tip

For Role Play: Client-Server Restaurant, assign clear roles and enforce a single queue so students experience the queuing and delivery steps repeatedly.

What to look for

Give students a card with the terms 'Client' and 'Server'. Ask them to write one sentence explaining the job of each and one sentence describing how they work together to show a website.

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

Activity 02

• Role Play
• 25 min · Pairs

Browser Comparison Hunt

Pairs access the same three websites on different browsers like Chrome and Firefox installed on class devices. They screenshot and note display differences in layout or speed. Discuss why engines like Blink or Gecko cause variations.

Compare how different web browsers might display the same website.

Facilitation Tip

For Browser Comparison Hunt, provide a short checklist of visual elements to compare so students focus on specific rendering differences rather than general impressions.

What to look for

Present students with a simple analogy, like ordering food at a restaurant. Ask: 'Who is the client? Who is the server? What is the request? What is the response?' Discuss answers as a class.

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

Activity 03

• Role Play
• 45 min · Small Groups

Analogy Model Build

Small groups design and construct physical models, such as a post office with request letters and response parcels containing page parts. Test the model by simulating multiple requests. Present to class with explanations.

Design a simple analogy to explain how a web page is requested and delivered.

Facilitation Tip

For Analogy Model Build, supply index cards and colored markers so students can construct and rearrange their models as they refine their understanding.

What to look for

Ask students: 'Imagine two friends visit the same website on different devices, like a tablet and a phone. Why might the website look slightly different on each one?' Guide them to consider browser differences.

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

Activity 04

• Role Play
• 30 min · Whole Class

Request Card Simulation

Whole class uses printed cards: clients draw request cards, pass to server stations that select and return response cards with file types. Track a full cycle on worksheets, noting sequence and dependencies.

Explain the relationship between a client and a server in accessing a website.

Facilitation Tip

For Request Card Simulation, use numbered cards to represent different file types so students see how servers deliver only what was requested.

What to look for

Give students a card with the terms 'Client' and 'Server'. Ask them to write one sentence explaining the job of each and one sentence describing how they work together to show a website.

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

A few notes on teaching this unit

Teach this topic by first letting students experience the process physically before introducing technical terms. Avoid starting with definitions or diagrams, as these often oversimplify the dynamic client-server interaction. Research shows that students grasp pull-based systems better when they act as clients pulling resources rather than servers pushing them.

Successful learning looks like students using precise vocabulary to describe requests and responses, recognizing that servers do not push data without a prompt, and explaining why different browsers might display pages differently. Evidence includes accurate role-play actions, detailed comparison notes, and clear analogies built from provided materials.

---

Watch Out for These Misconceptions

• During Role Play: Client-Server Restaurant, watch for students treating the shared storehouse as a permanent archive of all internet content.

  Use the storehouse as a temporary supply that must be restocked for each new customer, emphasizing that browsers do not store entire websites permanently.

• During Request Card Simulation, watch for students assuming the server sends all files automatically without a specific request.

  Have students explicitly hand over a request card listing only HTML, CSS, or JavaScript before the server delivers those specific file types.

• During Browser Comparison Hunt, watch for students concluding that all differences are errors rather than intentional design choices.

  Ask students to research rendering engines and include findings in their comparison notes to shift focus from mistakes to intentional variation.

---

Methods used in this brief

• Role Play