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.

• Year 10
• Computing
• 3 activities
• 25 min–40 min

Learning Objectives

1. Explain how the Copyright, Designs and Patents Act 1988 protects original digital works.
2. Differentiate between copyright, patents, and trademarks as applied to software development.
3. Analyze the legal and ethical challenges of enforcing intellectual property rights for digital content online.
4. Evaluate the implications of open-source licenses versus proprietary software licenses on user freedoms and developer rights.

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.

Prepare & details

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.

Setup: Groups at tables with access to source materials

Materials: Source material collection, Inquiry cycle worksheet, Question generation protocol, Findings presentation template

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

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.

Prepare & details

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.

Setup: Two teams facing each other, audience seating for the rest

Materials: Debate proposition card, Research brief for each side, Judging rubric for audience, Timer

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

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.

Prepare & details

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.

Setup: Flexible space for group stations

Materials: Role cards with goals/resources, Game currency or tokens, Round tracker

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

Teaching This Topic

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.

What to Expect

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

Common Misconception

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

What to Teach Instead

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.

Common Misconception

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

What to Teach Instead

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

Assessment Ideas

Exit Ticket

After the Collaborative Investigation: The Software Audit, provide a scenario where a teacher wants to install an image editor in the computer lab and ask students to recommend either GIMP (open source) or Photoshop (proprietary). Students must justify their choice using audit findings about cost, license, and support.

Discussion Prompt

During the Structured Debate: The Security Question, circulate and listen for students connecting their arguments to real cases like Heartbleed or proprietary backdoors, then call on them to elaborate in the wrap-up.

Quick Check

After the Simulation: The Open Source Project, ask students to write a short reflection on which part of the simulation felt collaborative or restrictive, and how that mirrored real-world open-source communities.

Extensions & Scaffolding

• Challenge early finishers to draft a short policy memo as a company CTO recommending either open source or proprietary software for a new internal tool, citing evidence from the audit or debate.
• Scaffolding for struggling students: Provide a comparison table template with rows for license type, cost, support, modification rights, and security to fill in during the audit.
• Deeper exploration: Ask students to research the relationship between open source licenses (MIT, GPL) and business models, then present how a startup might choose one over the other during the simulation.

Key Vocabulary

Copyright	A legal right that grants the creator of original works of authorship exclusive rights for its use and distribution. This applies to software code, digital art, and written content.
Patent	A government-granted exclusive right for an invention, allowing the patent holder to exclude others from making, using, or selling the invention for a set period. This can apply to novel software algorithms or processes.
Trademark	A symbol, design, or phrase legally registered to represent a company or product. For software, this protects brand names and logos, like 'Microsoft Windows' or 'macOS'.
Intellectual Property (IP)	Creations of the mind, such as inventions, literary and artistic works, designs, and symbols, names, and images used in commerce. Copyright, patents, and trademarks are types of IP.
Open Source License	A type of license for software that allows source code to be viewed, modified, and distributed freely by users, under specific terms defined by the license (e.g., MIT, GPL).