Professional ethics are the standards that guide the behaviour of individuals and organisations in the computing industry. They are essential because:
Real‑world illustration (AO‑2): The 2017 Equifax data breach exposed personal details of ~147 million people. The breach occurred because the company failed to apply a known security patch – an unethical neglect of professional duty that led to massive financial loss, loss of trust, and legal action.
| Action (ethical / unethical) | Stakeholder(s) Affected | Typical Impact |
|---|---|---|
| Secure coding & regular patching (ethical) | Users, client organisations, public | Maintains trust, avoids data loss, complies with law. |
| Unauthorised copying of software (unethical) | Software developer, paying customers | Revenue loss, reduced incentive to innovate. |
| Transparent handling of user data (ethical) | End‑users, regulators | Compliance with GDPR, enhanced reputation. |
| Distributing malware disguised as legitimate software (unethical) | Victims, wider internet community | Financial damage, loss of confidence, possible criminal prosecution. |
Exam‑friendly definition: Copyright gives the creator of an original work the exclusive right to reproduce, distribute, perform publicly, and adapt the work for a limited period.
Without such protection creators would face unauthorised copying, loss of revenue, and difficulty distinguishing original work from derivatives – all of which would undermine innovation and economic growth.
| IP Type | What It Protects | Typical Duration | Key Computing Example |
|---|---|---|---|
| Copyright | Original literary, artistic, musical, and software works | Life of author + 70 years (varies) | Source code of a program |
| Patents | New inventions or technical solutions | 20 years from filing date | Data‑compression algorithm (rarely examined in CS AO‑2) |
| Trademarks | Brand names, logos, slogans | Indefinite, renewable every 10 years | Company logo shown in a software UI |
| Design Rights | Appearance of a product | 15 years (UK) / 25 years (EU) | Icon design for a mobile app |
| Licence Family | Key Conditions | Typical Use‑Case |
|---|---|---|
| Proprietary (e.g., Microsoft ©, Oracle ©) | Source code closed; user receives a limited right to use the compiled product; copying, modification and redistribution prohibited without explicit permission. | Commercial off‑the‑shelf applications where the vendor wants full control and revenue. |
| Permissive Open‑Source (e.g., MIT, BSD) | Allows copying, modification and redistribution, even in proprietary products, provided attribution is retained and a copy of the licence is included. | Libraries or utilities that the author wishes to be widely adopted with minimal restrictions. |
| Copyleft Open‑Source (e.g., GNU GPL, AGPL) | Permits use, modification and redistribution, but any derivative work must be released under the same licence (source code must be made available). | Projects that aim to guarantee that improvements remain free and open to the community. |
You have written a reusable authentication library and want any improvements to remain open.
You have developed a high‑performance graphics engine and want to sell licences, but also allow other companies to embed it in their closed‑source products.
Napster enabled users to share MP3 files without paying royalties. The courts ruled that Napster facilitated copyright infringement, leading to its shutdown. The case highlighted:
Copyright legislation protects creators, promotes innovation, and supplies a clear legal framework for the use and distribution of software and digital content. Understanding the legal rights, the variety of software licences, and the associated ethical responsibilities equips future computer scientists to navigate the complex landscape of digital ownership responsibly.
| AO | What the notes address |
|---|---|
| AO1 – Knowledge & Understanding | Definitions of ethics, copyright, IP types, licence families, professional bodies, AI issues. |
| AO2 – Application | Applying copyright principles to software, interpreting the Napster case, selecting licences for given scenarios. |
| AO3 – Analysis & Evaluation | Justifying licence choices, evaluating ethical dilemmas, discussing the impact of legislation on innovation. |
Flowchart – Lifecycle of a Copyrighted Software Work: Creation → Copyright attaches automatically → Licensing (choose proprietary / permissive / copyleft) → Distribution (sale, download, streaming) → Enforcement (monitoring, infringement action) → Expiry of rights.
Create an account or Login to take a Quiz
Log in to suggest improvements to this note.
Your generous donation helps us continue providing free Cambridge IGCSE & A-Level resources, past papers, syllabus notes, revision questions, and high-quality online tutoring to students across Kenya.