You are viewing a free preview of this lesson.
Subscribe to unlock all 10 lessons in this course and every other course on LearningBro.
A program is not a physical object you can lock in a drawer — it is information, copied perfectly and instantly by anyone who has it. So how do the people who write software get protected, paid and credited for their work? The answer is intellectual property (IP) law, which grants creators legally enforceable rights over the things they make, and software licensing, the contracts that say what you are allowed to do with someone else's software. This is a discursive 1.5 topic: as well as knowing the law, you must be able to weigh the competing models — should an organisation buy proprietary software or adopt open source? what does a developer gain or give up by releasing code under a particular licence? — and discuss the impact of software piracy. We cover copyright (the Copyright, Designs and Patents Act 1988), patents and trademarks, the spectrum of licensing models (proprietary, FOSS/open source, freeware, shareware, Creative Commons), and the costs of piracy.
This lesson addresses the H446 1.5 content on the protection and licensing of software and other works:
(Phrasing here paraphrases the specification content; it is not a verbatim quote.)
Intellectual property is the legal recognition that creations of the mind — inventions, written and artistic works, software, designs, brand names and logos — can be owned, just as physical property can. IP law gives the creator a set of exclusive rights: the right to control how the work is copied, used, distributed and adapted, and the right to benefit financially from it. The justification is partly fairness (creators should reap what they sow) and partly incentive: if anyone could copy software the instant it was written, there would be far less reason to invest the effort of writing it. IP law is the bargain society strikes — temporary, enforceable control for creators in exchange for the creation, and eventual release, of new works.
The three forms that matter for this topic protect different things, and a frequent exam error is to muddle them.
| IP right | Protects | Example in computing |
|---|---|---|
| Copyright | The expression of an idea — the actual code, text, images, music — but not the underlying idea itself. | The specific source and object code of a program; its on-screen artwork. |
| Patent | A new invention: a novel product or process providing a technical solution to a problem. | A genuinely novel hardware design or a technical method with an inventive step. |
| Trademark | A sign (name, logo, slogan) that distinguishes a trader's goods or services. | A software company's name and logo, protecting its brand identity. |
The Copyright, Designs and Patents Act 1988 is the UK's principal statute for copyright, and it is the one that protects software.
Copyright protects original works from being copied, distributed, adapted or performed without the rights-holder's permission. Its defining features are:
| Feature | Detail |
|---|---|
| What it covers | Literary works (which includes software source and object code), as well as music, art, film, broadcasts and databases. |
| Automatic | Copyright arises automatically the moment a qualifying work is created and recorded — there is no registration and no fee. |
| Duration | For literary, dramatic, musical and artistic works, the lifetime of the creator plus 70 years — long after the creator's death. |
| Ownership | Usually the creator, but where a work is made by an employee in the course of employment, the employer owns it by default. |
| Idea vs expression | Copyright protects the expression (the actual code written), not the abstract idea or algorithm — someone may write their own program to do the same job without infringing. |
Because software is a "literary work", you may not copy, modify or distribute it without permission, and reverse-engineering it is generally restricted. The crucial consequence is that every legitimate use of software you did not write yourself happens under a licence — a permission the rights-holder grants on stated terms. The licence is what gives back some of the rights copyright reserves; without one, the default position is "you may do almost nothing".
A patent protects an invention rather than an expression. To be patentable, an invention must be new, involve an inventive step (not obvious), and be capable of industrial application. Unlike copyright, a patent is not automatic: it must be applied for, examined and granted, which is costly and public (the invention is disclosed in return for protection), and it lasts a shorter, fixed term (commonly up to 20 years from filing). A subtle and examinable point: in the UK/Europe, software "as such" generally cannot be patented — that is the realm of copyright — although software producing a genuine technical effect sometimes can. So a program's code is protected by copyright; only an underlying technical invention might attract a patent.
A trademark protects a brand: the name, logo or slogan under which goods or services are sold, so that customers can identify their origin and are not deceived by imitators. Trademarks can be registered and, unlike copyright and patents, can be renewed indefinitely as long as they remain in use. For a software company, the trademark protects the identity (the product name and logo), while copyright protects the code — two different rights guarding two different things.
Exam Tip: Keep the three rights distinct. Copyright = automatic, protects the expression (the code), very long duration. Patent = registered, protects a technical invention, shorter fixed term. Trademark = protects a brand sign, renewable indefinitely. Stating what each protects and whether it is automatic or registered is usually where the marks are.
A software licence is the legal agreement that defines how a piece of software may be used, copied, modified and distributed. Far from a formality, the licence is the entire mechanism by which copyright is translated into "what you are actually allowed to do". The models form a spectrum from tightly closed to maximally open.
| Model | Source code? | Modify? | Redistribute? | Cost | Typical purpose |
|---|---|---|---|---|---|
| Proprietary (closed source) | Hidden | No | No | Usually paid (purchase or subscription) | A vendor sells a product and protects its code and revenue. |
| Open source / FOSS | Open to all | Yes | Yes (under the licence's terms) | Usually free of charge | Collaborative development; freedom to study, change and share. |
| Freeware | Usually hidden | No | Sometimes (unchanged) | Free of charge | Software given away at no cost, but still proprietary. |
| Shareware | Hidden | No | Often, to share the trial | Free to try, then pay | "Try before you buy" — limited or time-restricted until purchased. |
Two distinctions cause endless confusion and are worth nailing down:
Open-source software (often "free and open-source software", FOSS) makes the source code freely available so that anyone may study, modify and redistribute it, subject to the chosen licence. This is the model behind a great deal of foundational software. Its open-source licences themselves divide into two philosophies:
| Licence style | Rule | Consequence for a developer using it |
|---|---|---|
| Copyleft (e.g. the GNU GPL) | Any derivative work you distribute must be released under the same open licence, with source code made available. | You may build on it freely, but you cannot fold it into closed proprietary software and keep your changes secret — the openness is "viral". |
| Permissive (e.g. MIT, BSD, Apache-style) | Few restrictions; derivatives may be released under any licence, including proprietary, usually only requiring that the original notice be kept. | You can incorporate it into closed commercial products without opening your own code. |
This copyleft/permissive choice has real strategic weight. A developer who wants their contribution to stay open forever chooses copyleft; one who wants the widest possible adoption, including by commercial closed products, chooses permissive. Companies are often wary of copyleft precisely because of its viral obligation, while individual idealists may prefer it for the same reason.
Creative Commons (CC) is not for software but for creative works — images, text, music, video — offering creators a standardised menu of permissions so they need not write a custom licence. Its building blocks combine:
| Element | Meaning |
|---|---|
| BY (Attribution) | You must credit the creator. |
| SA (Share-Alike) | Derivatives must use the same CC licence (the CC analogue of copyleft). |
| NC (Non-Commercial) | Use is allowed for non-commercial purposes only. |
| ND (No Derivatives) | You may share the work but not modify it. |
| CC0 | The creator waives rights, placing the work effectively in the public domain. |
So "CC BY-NC-SA", for instance, means credit the author, no commercial use, and share any adaptation under the same terms. Creative Commons matters in computing for assets, documentation and educational materials, and it shows the same open-versus-controlled tension as software licences, transposed to media.
Software piracy is the unauthorised copying, distribution or use of software in breach of its licence and of copyright. It takes several forms — making and selling counterfeit copies, illegal downloading, "softlifting" (installing one licensed copy on more machines than the licence allows), and pre-loading unlicensed software onto computers for sale. All share the same root: using software in ways the rights-holder did not permit.
Piracy is often dismissed as victimless, which a good answer should challenge by setting out its impact:
| Impact | Explanation |
|---|---|
| On developers | Lost revenue reduces the funds available to maintain, improve and support software, and undermines the incentive to create it — the very thing copyright exists to protect. |
| On users | Pirated copies receive no official updates or support, and frequently carry malware (a tampered installer is a classic infection route), so the "free" software can be costly. |
| On security | Unpatched, modified software is a weak point that endangers not only the user but networks they connect to. |
| On the economy | Reduced legitimate sales mean less tax revenue and fewer resources for the software industry and the jobs it supports. |
| Legal | Infringement is unlawful under the Copyright, Designs and Patents Act 1988, exposing infringers to civil and potentially criminal liability. |
The honest, examinable nuance is that piracy is also sometimes argued to spread skills or seed future paying customers, and the debate over how best to respond — stricter enforcement, technical protection, or cheaper and more convenient legitimate access — is a live one. The strongest answers acknowledge the harms and the contested responses rather than treating it as simple theft.
If copyright and licences are the legal way to control what is done with software and media, Digital Rights Management (DRM) is the technical way — software and hardware measures that enforce a licence's terms automatically, whether or not the user reads or respects them. Where a licence says "you may play this on your own devices", DRM makes it so that only authorised devices actually can.
| Aspect | Detail |
|---|---|
| Purpose | To prevent unauthorised copying, sharing and modification of digital content, so creators are paid and licence terms are obeyed. |
| How it works | Content is typically encrypted, and only authorised devices or software hold the keys to decrypt and use it; access may be tied to an account, a device limit or an online check. |
| Where it appears | Streaming services, e-books, paid games and downloadable media, and some software activation schemes. |
The link to the wider course is direct: DRM is encryption applied to enforcement, so it rests on exactly the cryptographic ideas met in the security topic. But DRM is genuinely contested, and a discursive answer should weigh both sides rather than assume it is simply "good for creators".
| Arguments for DRM | Arguments against DRM |
|---|---|
| Protects creators' rights and helps ensure they are paid, sustaining future work. | Inconveniences honest, paying users — for example by limiting how many devices may be used, or refusing legitimate transfers. |
| Deters casual mass copying and sharing. | Can render purchases unusable if the verification servers are later switched off — buyers may lose access to content they paid for. |
| Lets businesses offer flexible models (rental, time-limited access) that rely on enforceable limits. | Is routinely circumvented by determined infringers, so it often fails against the very piracy it targets, hitting only the law-abiding. |
| Reassures rights-holders enough to release content digitally at all. | May restrict legitimate uses (such as accessibility adaptations or lawful personal back-ups). |
Subscribe to continue reading
Get full access to this lesson and all 10 lessons in this course.