Computing · Year 10

Active learning ideas

Copyright, Designs and Patents Act

Active learning works because Year 10 students need to see the real-world impact of intellectual property choices in software. When they audit actual products, debate security models, or join a mock open-source project, abstract legal concepts become tangible business and ethical decisions they can evaluate for themselves.

• National Curriculum Attainment Targets
• GCSE: Computing - Ethical, Legal, and Cultural Impacts

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

Activity 01

• Inquiry Circle
• 25 min · Pairs

Inquiry Circle: The Software Audit

Students look at the software they use daily (Windows, Android, Linux, Chrome, Firefox). They must categorise each as Open Source or Proprietary and identify who 'owns' it and how they make money.

Explain how copyright protects digital creations.

Facilitation Tip

During the Software Audit, assign each small group one piece of software to investigate so they can collect concrete evidence about price, license terms, and company revenue models before presenting back.

What to look for

Provide students with three scenarios: a programmer sharing code online, a company releasing a new app with a unique interface, and a musician uploading a song. Ask them to identify which type of intellectual property (copyright, patent, trademark) is most relevant to protecting each scenario and briefly explain why.

• Analyze
• Evaluate
• Create
• Self-Management
• Self-Awareness

Activity 02

• Formal Debate
• 35 min · Small Groups

Formal Debate: The Security Question

One side argues that Open Source is more secure because 'many eyes' can find bugs. The other side argues Proprietary is more secure because hackers can't see the source code to find vulnerabilities. Students must use real-world examples to support their points.

Differentiate between copyright, patents, and trademarks in the context of software.

Facilitation Tip

For the Security Debate, give each side a one-page brief with key facts about open versus proprietary security practices to keep the discussion focused and evidence-based.

What to look for

Pose the question: 'Is it always possible or even desirable to enforce strict intellectual property rights for digital content?' Facilitate a class discussion where students consider the balance between creator rights, public access, and innovation, referencing specific examples like Wikipedia or public domain works.

• Analyze
• Evaluate
• Create
• Self-Management
• Decision-Making

Activity 03

• Simulation Game
• 40 min · Small Groups

Simulation Game: The Open Source Project

Students are given a simple 'recipe' (code). One group must follow it exactly (Proprietary). The other group is allowed to modify and improve it, sharing their 'patches' with other groups (Open Source) to see which recipe ends up better.

Analyze the challenges of enforcing intellectual property rights online.

Facilitation Tip

In the Open Source Project simulation, provide a starter code repository with a clear issue to fix, so students experience collaboration constraints firsthand rather than theorizing about them.

What to look for

Present students with definitions of copyright, patent, and trademark. Ask them to match each definition to the correct term. Follow up by asking them to provide one example of a digital creation that would be protected by each type of IP.

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

A few notes on teaching this unit

Teachers should anchor the topic in students’ lived experience by starting with software they already use. Avoid presenting open versus proprietary as a moral binary; instead, emphasize trade-offs using business cases and technical constraints. Research shows that when students role-play as developers, lawyers, or executives, they grasp nuance faster than through lecture alone.

Successful learning looks like students confidently explaining why a company might choose open source for reliability and why another might pay for proprietary software for support. They should be able to compare licenses, justify their stance in debate, and articulate how design decisions reflect philosophical or financial priorities.

---

Watch Out for These Misconceptions

• During the Collaborative Investigation: The Software Audit, watch for students equating 'free download' with open source.

  Use the audit worksheet to prompt students to check the license field in the software’s about page or source repository, highlighting that price and freedom are separate concepts.

• During the Structured Debate: The Security Question, watch for blanket claims that proprietary software is always more secure.

  Direct students to the debate brief’s comparison of security disclosure practices, where open-source projects often fix vulnerabilities faster due to public scrutiny.

---

Methods used in this brief

• Inquiry Circle
• Formal Debate
• Simulation Game