You are viewing a free preview of this lesson.
Subscribe to unlock all 10 lessons in this course and every other course on LearningBro.
This lesson compares open source and proprietary software, as required by OCR J277 Section 1.6. Understanding the differences between these two software models is important for ethical, legal, and practical reasons.
Open source software is software where the source code is made freely available to the public. Anyone can view, modify, distribute, and improve the code, subject to the terms of the software's open source licence.
| Software | Type |
|---|---|
| Linux | Operating system |
| Firefox | Web browser |
| LibreOffice | Office suite |
| Apache | Web server |
| MySQL | Database |
| Python | Programming language |
| VLC | Media player |
| WordPress | Content management system |
| Android | Mobile operating system (based on open source) |
Proprietary software (also called closed source software) is software where the source code is not made publicly available. The software is owned by a company or individual, and users must purchase a licence to use it.
| Software | Type |
|---|---|
| Microsoft Windows | Operating system |
| Microsoft Office | Office suite |
| Adobe Photoshop | Image editing |
| macOS | Operating system |
| iOS | Mobile operating system |
| Spotify | Music streaming |
| Feature | Open Source | Proprietary |
|---|---|---|
| Source code | Publicly available | Secret / closed |
| Cost | Usually free | Usually requires purchase or subscription |
| Modification | Can be freely modified | Cannot be modified by users |
| Distribution | Can be freely distributed | Distribution restricted by licence |
| Support | Community forums, documentation; paid support sometimes available | Official support from the developer |
| Updates | Community-driven, may be less regular | Regular, scheduled updates from the developer |
| Security | Code can be audited by anyone (more eyes = more bugs found) | Security through obscurity; only the developer can fix vulnerabilities |
| User interface | Can vary; sometimes less polished | Usually polished and consistent |
| Compatibility | May have compatibility issues with proprietary formats | Usually good compatibility with industry standards |
OCR Exam Tip: This is one of the most commonly tested topics in Section 1.6. You must be able to give at least two advantages and two disadvantages of each type. The exam often presents a scenario (e.g. a school or business) and asks which type of software they should choose, with justification.
| Advantage | Explanation |
|---|---|
| Free to use | No purchase or licence cost, reducing expenses |
| Customisable | Source code can be modified to meet specific needs |
| Community support | Large communities of developers contribute improvements and fix bugs |
| Transparency | Anyone can inspect the code for security vulnerabilities or backdoors |
| No vendor lock-in | Users are not dependent on a single company |
| Innovation | Open development encourages collaboration and rapid innovation |
| Disadvantage | Explanation |
|---|---|
| Limited official support | May rely on community forums rather than dedicated support teams |
| Learning curve | Some open source software has a steeper learning curve (e.g. Linux) |
| Compatibility | May not be fully compatible with proprietary file formats |
| Inconsistent quality | Quality varies depending on the community and project funding |
| Security risk | If vulnerabilities are found, attackers can also see the source code |
| Advantage | Explanation |
|---|---|
| Official support | Dedicated customer support, documentation, and training |
| User-friendly | Often designed with a polished, intuitive user interface |
| Regular updates | Scheduled updates, patches, and new features |
| Compatibility | Good integration with other products from the same vendor |
| Reliability | Extensive testing before release |
| Disadvantage | Explanation |
|---|---|
| Cost | Licence fees or subscriptions can be expensive, especially for businesses |
| No customisation | Users cannot modify the software to meet specific needs |
| Vendor lock-in | Dependent on the company for updates, support, and continued availability |
| Lack of transparency | Users cannot inspect the source code for vulnerabilities or backdoors |
| Restrictions | EULA limits how the software can be used and distributed |
| Issue | Open Source View | Proprietary View |
|---|---|---|
| Freedom | Software should be free to use and modify | Developers deserve payment for their work |
| Innovation | Open collaboration drives faster innovation | Profit motive funds research and development |
| Security | Transparency improves security | Hiding source code prevents attackers finding vulnerabilities |
| Access | Everyone should have access to software tools | Quality software requires funded development |
flowchart LR
S((Software<br/>licence model)) --> OSS[Open Source]
S --> PRO[Proprietary]
OSS --> O1["Source code<br/>public"]
OSS --> O2["Free to use,<br/>modify, redistribute"]
OSS --> O3["Community<br/>support"]
OSS --> O4["Examples:<br/>Linux, Firefox,<br/>LibreOffice, Python"]
PRO --> P1["Source code<br/>secret"]
PRO --> P2["Paid licence<br/>+ EULA"]
PRO --> P3["Vendor<br/>support"]
PRO --> P4["Examples:<br/>Windows, MS Office,<br/>Photoshop, iOS"]
O2 --> RISK1["Risk: variable<br/>polish, compatibility"]
P2 --> RISK2["Risk: cost,<br/>vendor lock-in"]
Subscribe to continue reading
Get full access to this lesson and all 10 lessons in this course.