Know and understand the methods that software producers employ to prevent software copyright legislation being broken
Topic 9 – Audience
Objective
Know and understand the methods that software producers employ to prevent software copyright legislation being broken, and appreciate how the audience influences the design and delivery of ICT solutions.
1. Audience appreciation (Syllabus 9.1)
In ICT, the audience is the group of people who will use or be affected by a solution. Identifying audience needs helps shape the functionality, usability, and legal compliance of software.
- Methods of audience analysis: surveys, interviews, questionnaires, persona creation, and observation of current practices.
- Typical audience groups in schools:
- Students – need intuitive interfaces, quick access to learning resources, and clear guidance on legal use of software.
- Teachers – require tools for lesson planning, grading, and data protection, with more control over licences.
- Administrators – focus on budgeting, licence management, and compliance with school policies.
- Classroom example: Designing a timetable app.
- For students the priority is a simple, colour‑coded view of lessons.
- For teachers the app must allow editing, publishing changes, and exporting data securely.
- For administrators the solution must track licence usage and generate reports for audit.
2. Why protect software? (Syllabus 9.2)
- Software is intellectual property protected by copyright – the legal right of the creator to control copying, distribution, and adaptation for a set period (usually the life of the author plus 70 years).
- Unauthorised copying can cause significant financial loss for developers and reduce incentives for further innovation.
- Copyright protection works alongside the Data‑Protection Act; personal data stored or processed by software must be kept confidential and secure, reinforcing e‑safety responsibilities.
3. Methods used by software producers
3.1 Legal measures
- End‑User Licence Agreements (EULAs) – a contract presented at installation that defines permitted uses.
Example: most commercial office suites require users to accept an EULA before the software can be installed.
- Copyright notices – statements such as “© 2025 Company Name. All rights reserved.” displayed on splash screens, documentation, or web pages.
- Enforcement actions – legal proceedings, cease‑and‑desist letters, or court orders against individuals or organisations that infringe copyright.
Example: a 2023 UK High Court ruling (*Microsoft Corp v. FS Software Ltd*) upheld an injunction against a company distributing cracked versions of Windows, confirming that circumvention of DRM is illegal under the Copyright, Designs and Patents Act 1988.
3.2 Technical protection measures (TPM)
- Digital Rights Management (DRM) – encryption plus licence‑server verification that controls who can decrypt and run the software.
- Product activation – a unique key is validated online before the software becomes fully functional.
Example: Microsoft Office 365 requires activation after installation.
- Serial numbers / licence keys – alphanumeric codes entered during installation or first‑run, often checked against a local database.
- Hardware dongles – physical devices that must be attached to the computer for the software to run; the programme checks for the dongle at start‑up.
- Obfuscation – source or binary code is transformed (renamed, reordered, encrypted) to make reverse‑engineering difficult.
- Watermarking – hidden identifiers embedded in the executable or output files to trace unauthorised copies.
3.3 Operational controls
- Online verification – periodic checks with a licence server to confirm that a licence is still valid.
- Automatic updates – ensure users run the latest authorised version and can disable cracked or outdated copies.
- Usage monitoring – logging of usage patterns to detect abnormal activity that may indicate piracy.
3.4 Educational & awareness strategies
- Campaigns that explain the impact of piracy on jobs, the economy, and personal data security.
- Providing clear information on legal alternatives (e.g., free trials, freemium models, open‑source equivalents).
4. Ethical perspective
Respecting copyright is not only a legal requirement; it protects users from the hidden risks of pirated software, such as malware, data breaches, and unreliable performance. By using legitimate software, audiences help sustain a trustworthy digital ecosystem and preserve the rights of developers.
5. Comparison of protection methods
| Method | How it works | Advantages | Disadvantages |
|---|---|---|---|
| EULA | Legal contract displayed at installation; user must accept before proceeding. | Clearly defines user obligations; easy to enforce in court. | Relies on users reading and understanding the text; can be ignored. |
| Copyright notice | Visible statement of ownership placed on software screens, manuals or web pages. | Simple, low‑cost reminder of legal ownership. | Does not prevent copying; only serves as evidence of claim. |
| Enforcement actions | Legal proceedings, cease‑and‑desist letters, or court orders against infringers. | Strong deterrent when publicised; can remove illegal copies. | Time‑consuming and costly; may not stop widespread piracy. |
| DRM | Encryption plus licence‑server verification controls who can decrypt and run the software. | Robust technical barrier; can limit unauthorised distribution. | May inconvenience legitimate users; can be cracked over time. |
| Product activation | Unique key is checked online; full functionality is unlocked only after successful validation. | Prevents mass distribution of unauthorised copies. | Requires internet access; activation servers can experience downtime. |
| Serial numbers / licence keys | Alphanumeric code entered during installation; often verified against a local database. | Simple to implement; familiar to users. | Easily shared or generated by key‑gens if not combined with online checks. |
| Hardware dongle | Physical device must be present for the software to run; the programme checks for the dongle at start‑up. | Very difficult to duplicate; ties licence to a specific machine. | Additional hardware cost; can be lost or damaged. |
| Obfuscation | Code is transformed (renamed, reordered, encrypted) to hide logic and structure. | Raises the skill level required to reverse‑engineer the software. | Does not stop copying; only slows down attackers. |
| Watermarking | Unique, hidden identifiers are embedded in the executable or output files. | Helps trace the source of illegal copies. | Can be removed by skilled crackers; adds processing overhead. |
6. Typical DRM workflow
7. Key take‑aways for students
- Software protection combines legal contracts, technical barriers, operational monitoring, and awareness campaigns.
- Each method has strengths and weaknesses; a layered (defence‑in‑depth) approach is most effective.
- Understanding these measures helps you comply with copyright law, protect personal data, and make ethical choices about software use.
- Identifying the audience ensures that protection measures do not unduly hinder legitimate users.
8. Mini‑task (practical classroom activity)
Task: In groups of 3‑4, choose a common school software (e.g., a graphics editor, a learning management system, or a spreadsheet). Produce a short poster that includes:
- The main audience(s) for the software and at least one specific need of each audience.
- Two legal protection methods and two technical protection measures used by the software.
- One ethical implication of using pirated copies of this software.
Present your poster to the class and discuss how the chosen protection methods balance security with user convenience.