Computing · Year 11

Active learning ideas

Introduction to Programming Paradigms

This topic asks students to think like builders who must anticipate problems before they happen, not just coders who make things work. Active learning works because students need to experience firsthand how fragile systems can be, rather than just hear about defensive techniques in theory.

• National Curriculum Attainment Targets
• GCSE: Computing - Programming
• GCSE: Computing - Software Development

• 15–30 min
• Pairs → Whole Class
• 3 activities

Activity 01

• Simulation Game
• 30 min · Pairs

Simulation Game: The Code Breaker

In pairs, one student acts as the 'developer' and the other as the 'malicious user'. The user tries to crash the developer's program using extreme values, wrong data types, or empty inputs, while the developer tries to patch the holes in real-time.

Compare the benefits of object-oriented programming over imperative programming for large projects.

Facilitation Tip

During The Code Breaker simulation, assign clear roles such as 'attacker', 'defender', and 'observer' to ensure every student contributes to the problem-solving process.

What to look for

Present students with three short code snippets, each representing a different paradigm (imperative, OOP, event-driven). Ask them to identify which paradigm each snippet exemplifies and briefly state one characteristic that led to their choice.

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

Activity 02

• Gallery Walk
• 20 min · Small Groups

Gallery Walk: Validation Critique

Post different snippets of validation code around the room (e.g., range checks, length checks, presence checks). Students move in groups to identify which specific errors each snippet prevents and which it might still let through.

Explain how event-driven programming differs from traditional sequential execution.

Facilitation Tip

In the Validation Critique Gallery Walk, provide a simple scoring rubric so students focus on defensible evidence rather than subjective opinions.

What to look for

Facilitate a class discussion using the prompt: 'Imagine you are building a simple calculator application versus a complex social media platform. Which programming paradigm would you choose for each, and why? Consider the benefits for code organization, reusability, and handling user interactions.'

• Understand
• Apply
• Analyze
• Create
• Relationship Skills
• Social Awareness

Activity 03

• Think-Pair-Share
• 15 min · Pairs

Think-Pair-Share: UX vs Security

Students discuss the trade-offs between making a program easy to use and making it secure. For example, should a password require 20 characters and a biometric scan? They then share their 'balanced' security policy with the class.

Analyze a simple problem and determine which programming paradigm would be most suitable for its solution.

Facilitation Tip

Use the Think-Pair-Share UX vs Security discussion to structure turn-taking so quieter students have space to contribute before the whole class shares.

What to look for

Ask students to write down one key difference between imperative and event-driven programming. Then, have them describe a scenario where an object-oriented approach would be significantly more beneficial than an imperative one.

• Understand
• Apply
• Analyze
• Self-Awareness
• Relationship Skills

A few notes on teaching this unit

Experienced teachers approach this topic by framing programming as a service to users, not just a technical task. Avoid letting students treat validation as a checkbox exercise; instead, connect each technique to real-world consequences. Research shows that when students role-play attackers, they better understand why defensive design matters. Keep the focus on concrete, fixable problems rather than abstract theory.

Successful learning looks like students confidently identifying when and why to use input validation, sanitization, and authentication in different contexts. They should be able to explain trade-offs between user experience and security, and justify their design choices with evidence from activities.

---

Watch Out for These Misconceptions

• During The Code Breaker simulation, watch for students who assume validation is only about syntax or format. Redirect them by asking, 'Could a malicious user still cause harm if the input looks correct on the surface?'

  During The Code Breaker simulation, have students test their defenses by crafting inputs that bypass basic checks, then revise their validation rules based on what they learn from the failed attempts.

• During the Validation Critique Gallery Walk, watch for students who believe UI constraints eliminate the need for server-side validation. Redirect them by asking, 'What happens if someone sends data directly to the server without using the UI?'

  During the Validation Critique Gallery Walk, provide actual 'inspect element' tools and sample HTML forms so students can see how easily front-end restrictions can be bypassed.

---

Methods used in this brief

• Simulation Game
• Gallery Walk
• Think-Pair-Share