Software Licences Exam Questions

• B Open-source licence (1)
• The only correct answer is B. The correct answer is open-source licence (accept open source licence, open-source software licence, open source software licence).
• A is not correct because copyright is a legal right that stops others copying the work
• C is not correct because a patent protects an invention
• D is not correct because a proprietary licence keeps the source code closed

• D Proprietary (1)
• The only correct answer is D. The correct answer is proprietary.
• A is not correct because copyright is a method of intellectual property protection, not a type of software
• B is not correct because open-source software has a licence that allows users to view and modify the source code
• C is not correct because a patent is a method of intellectual property protection that protects an invention, not a type of software

• C Patent (1)
• The only correct answer is C. The correct answer is patent.
• A is not correct because copyright protects creative works such as program code, not an invention
• B is not correct because an open-source licence sets out how software may be used, not how an invention is protected
• D is not correct because a trademark protects a brand name or logo

• C Permission to use the software under set conditions (1)
• The only correct answer is C. The correct answer is permission to use the software under set conditions.
• A is not correct because the copyright stays with the creator and is not transferred by a licence
• B is not correct because a licence does not give the user ownership of the source code
• D is not correct because a licence can restrict selling copies of the software

Award one mark for:

• Open-source (licence) (1)

Allow open source (software licence) / OSS / FOSS.

Do not accept freeware/shareware.

Do not accept proprietary.

Award one mark for any of the following up to a maximum of two marks:

• The source code is not released/made available (1)
• A licence must be purchased/obtained before the software can be used (1)
• The user cannot modify/adapt the software (1)
• The software remains the property of the developer/company (1)

Allow 'the user must pay for it' for the licence point.

Do not accept 'software that is not open source' (circular).

Do not accept 'software that anyone can edit' (this describes open-source software).

Award one mark for any of the following up to a maximum of two marks:

• Source code (must be) made available/accessible/distributed (with the software) (1)
• Any modified version/changes (must be) released/shared under the same licence (1)
• The original author/copyright notice (must be) kept/credited (1)
• The licence/terms (must be) included/supplied with any copy/redistribution (1)
• Changes/alterations (must be) stated/documented (1)

Allow wording such as 'must share changes' for the modified version being released under the same licence.

Do not accept 'the software must be free of charge/must not be sold/cannot be charged for' (open-source software can be sold/distributed for a fee).

Do not accept 'the source code must be kept secret' (this is a proprietary licence).

Do not accept 'anyone can use it/access it' (too general).

Award one mark for any of the following up to a maximum of two marks:

• Copying the software (1)
• Sharing/redistributing the software (1)
• Selling the software/copies of it (1)
• Renting/lending the software (1)
• Modifying/changing the software (1)
• Installing the software on more devices than the licence allows (1)
• Using the software without a valid licence (1)

Allow pirating/illegal copying (for copying the software).

Allow distributing/passing on (for sharing/redistributing the software).

Allow editing/changing/reverse engineering the code (for modifying the software).

Treat each restriction as a separate point; copying the software and sharing/redistributing it are different restrictions.

Do not accept 'using the software' on its own.

Award up to two marks for a linked description such as:

• The source code is not released/kept by the developer (1) so users cannot view or change the code (1)
• The user must buy/pay for a licence (1) before the software can be installed/used (1)
• Only the compiled program is supplied (1) so the user cannot modify/adapt the software (1)
• The software cannot be shared/copied (1) because this would break the terms of the licence (1)

Do not accept 'it costs money' on its own, with no reference to buying a licence.

Do not accept characteristics of open-source software, e.g. the source code is available to edit.

Award up to two marks for a linked description such as:

• An open-source licence makes the source code accessible/available (1) so users can edit/adapt/modify it to add new features (1)
• An open-source licence allows users to amend/change the source code (1) so they can fix errors/bugs and improve how the software works (1)
• An open-source licence allows anyone to access/study the source code (1) so more programmers can review/test it and suggest improvements (1)

Do not accept answers that only say the software is free/free of charge or that anyone can use it, as these do not explain how the software is improved.

Do not accept descriptions of proprietary licences, such as paying for a licence or closed source.

Award up to two marks for a linked description such as:

• A licence/license is a legal agreement between the developer/owner and the user/end user/customer (1) that sets out what the user is/is not allowed to do with the software (1)
• It states how many devices/users may install or run the software (1) so the software is not installed/used on more devices/users than the developer allows (1)
• It protects the developer's intellectual property/copyright (1) by stopping the software being copied/used/redistributed without permission (1)
• It sets out the terms/conditions of use (1) that the user must agree to before using the software (1)

Allow a single unlinked point, such as 'it sets out what the user is allowed to do with the software', for one mark.

Do not accept 'it is a contract/a legal document' with no purpose given.

Do not accept descriptions of product keys, activation or how to install the software.

Do not accept answers that only describe copyright, patents or trademarks with no reference to a licence.

Award up to two marks for a linked description such as:

• The software must not be sold (1) so it remains free for other users to obtain (1)
• The source code must be included when the software is shared (1) so anyone who receives it can also study/change it (1)
• Any modified version must be released under the same licence (1) so the software stays open-source for future users (1)

A valid condition on its own can earn one mark; the second mark is for a linked development of the effect.

Do not accept 'the user is not allowed to change the source code' or 'a fee must be paid' as these are conditions of proprietary software.

Do not accept 'it is free' or 'anyone can use it' as these do not describe a condition.

Award up to two marks for a linked explanation such as:

• The source code is kept secret/closed/hidden (1) so other developers/companies cannot copy/modify the game (1)
• The company can charge users for a licence/license (1) so it earns money from each copy sold (1)
• The company keeps control/ownership of the software (1) so it decides how the game is used/sold (1)
• The game can only be installed/used by users with a licence/license (1) so the company does not lose sales to pirated/unlicensed copies (1)

For both marks, the expansion must follow/associate with the statement.

Allow answers that contrast with open-source software if the reason is made clear, e.g. users of open-source software could modify and redistribute the game (1) so the company keeps the game as it intended (1)

Do not accept 'to make money' on its own without linking it to charging for a licence.

Do not accept 'it is more secure', or 'to protect the game'/'to stop copying', without saying what is protected (e.g. the source code) or who is prevented from copying.

Do not accept copyright/patent/trademark named on its own as the reason: these are other methods of protection and do not explain why a proprietary licence is chosen.

Award up to two marks for a linked explanation such as:

• There is no licence fee to pay (1) so the charity saves money/can spend its money on other things (1)
• The source code can be accessed/edited (1) so the charity can adapt the software to its needs (1)
• The software can be improved by a community of developers (1) so improvements/bug fixes are made available to the charity (1)
• The charity can install the software on as many computers as it needs (1) without buying extra licences (1)

For both marks, the expansion must follow/associate with the statement.

A point without a linked reason can earn (1) but not (2).

Do not accept 'it is free' on its own as a point; it must be linked to no licence fee/cost saving.

Do not accept 'it is cheaper'/'it saves money' on its own without a linked reason such as no licence fee to pay.

Do not accept 'it is easier to use' without a linked reason.

Do not accept 'it is open source' or 'open-source is free to use' on its own; this restates the question without a benefit.

Award up to two marks for a linked explanation such as:

• The programmer must not sell/redistribute the software for profit (1) because the licence requires it to remain free for other users (1)
• The programmer must make the source code available (1) so that other programmers can study/improve it (1)
• The programmer must share any changes they make (1) so that other users benefit from the improvements (1)
• The programmer must release a modified version under the same licence (1) so that the software stays open-source (1)
• The programmer must keep the original copyright notice (1) so that the original author is identified as the creator of the code (1)

For both marks, the expansion must follow/associate with the statement.

Allow other wordings of a restriction for the first mark, e.g. 'must not charge for it', 'must let other people use their modified version', 'must make the source code available'.

The restriction must be a condition of the licence, not a general good practice, e.g. 'it is good to share' is not creditworthy.

Do not accept 'they cannot use it for business/commercially' without a linked reason.

Do not accept 'they must pay for it' as this is not a restriction of open-source licences.

Do not accept restrictions of a proprietary licence, such as 'they cannot copy the software' or 'they cannot change the source code'.

Do not accept 'the software is free' on its own without a named restriction.

Do not award the second mark for a restatement of the point, e.g. 'so they have to share changes' or 'so the author gets credit' on its own.

Do not award marks twice for the same restriction worded in different ways, e.g. 'share changes' and 'release modified versions under the same licence'.

Award up to two marks for a linked explanation such as:

• The company can take legal action/legal proceedings against the user (1) because the user has broken the licence agreement/terms (1)
• The user may have to pay an additional cost/be charged for extra licences (1) because a licence only covers a set number of installations/computers (1)
• The user's licence may be cancelled/revoked (1) so they are no longer permitted to use the software (1)
• The company may require/instruct the user to remove/uninstall the software (1) because it is installed without a valid licence (1)

For both marks, the expansion must follow/associate with the statement.

Do not accept 'the software will stop working' without linking it to the licence terms.

Accept stopping use of the software only where it follows from the licence being cancelled/revoked, not from a technical fault.

Do not accept technical faults, such as a virus or the software crashing, as a consequence of breaking the licence terms.

Do not accept a reason that simply repeats the stem, such as 'because they installed it on more computers than allowed', without saying why that matters.

Indicative content

Rights under each licence

• An open-source licence gives the college access to the source code, so its IT team can read it and change the software to suit administration tasks.
• An open-source licence allows the college to redistribute the software, provided that any changed versions it distributes are released under the same licence.
• The college must still keep to the terms of an open-source licence, such as keeping copyright notices, so the software is not free of conditions.
• A proprietary licence must be bought before the software can be installed, and the college must buy a licence for each computer it uses.
• A proprietary licence does not provide the source code, so the college cannot modify the software or pass copies to another organisation.
• The terms of a proprietary licence restrict copying and redistribution, so the college must keep records of its licences to remain compliant.

Benefits and drawbacks for the college

• Open-source software usually has no licence fee, so the college can install it on more computers and spend its limited funding on other resources.
• Open-source software can be adapted by the IT team, but this takes time and programming skill that a small team may not have.
• Community support for open-source software may be slower than official support, so faults could disrupt college administration for longer.
• Proprietary software costs more because a licence is needed for each computer, which uses up the college's limited funding.
• Proprietary software comes with official support and updates, which suits a small IT team and reduces disruption for administration staff.
• Proprietary software is less flexible, so staff may have to change their working practices because the college cannot alter the source code.
• A mixture could be used: open-source software for general administration and proprietary software where reliable support is essential.

Levels

• Level 0 (0 marks): No rewardable content.
• Level 1 (1–2 marks): Basic, independent points are made, showing elements of understanding of key concepts/principles of computer science. (AO1) The discussion will contain basic information with little linkage between points made or application to the context. (AO2)
• Level 2 (3–4 marks): Demonstrates adequate understanding of key concepts/principles of computer science. (AO1) The discussion shows some linkages and lines of reasoning with some structure and application to the context. (AO2)
• Level 3 (5–6 marks): Demonstrates comprehensive understanding of key concepts/principles of computer science to support the discussion being presented. (AO1) The discussion is well developed, with sustained lines of reasoning that are coherent and logically structured, and which clearly apply to the context. (AO2)

Level 3 responses must discuss both open-source and proprietary licences and apply benefits and drawbacks to the college; a response that covers only one type of licence is limited to Level 2.

Credit a basic point for stating that proprietary software requires a licence, but do not accept 'free', 'expensive' or 'anyone can use it' on their own; cost points must be linked to the college's funding. 'Open-source software is not copyrighted' is incorrect and earns no credit.

Indicative content

Protection of the source code

• Releasing the application as open-source makes the source code available to anyone, so the company cannot keep its algorithms or code secret.
• Copyright automatically protects the application whether it is released as open-source or proprietary; the licence then sets out what users are allowed to do with the code.
• A proprietary licence keeps the source code closed, so the company retains control over how the application is used, copied and changed.
• With an open-source licence, other developers can legally copy, modify and redistribute the code, which makes it harder for the company to protect its intellectual property.
• Some open-source licences include copyleft conditions, which require anyone who distributes a modified version to release it under the same licence, so the company could not make a modified version proprietary later.
• A proprietary licence can include terms that stop users from copying or selling the application without permission, backed by copyright.
• A patent could protect a new technical method used by the application, but it would not stop users seeing the source code once it is released as open-source.

Income for the company

• Open-source software can be downloaded without paying a licence fee, so the company would lose the licence income from each copy and would need to charge for support, training or add-ons instead.
• Proprietary software generates income from a licence fee for each copy sold, which can fund further development.
• An open-source release may attract more users, some of whom might later pay for support, training or extra services.
• Proprietary licensing gives the company more control over pricing and can protect sales from unauthorised copying.
• The company may lose sales if customers can download and share an open-source version for free instead of paying for it.

Collaboration and development

• Open-source release allows other programmers to contribute improvements and find bugs, which can speed up development for a small company with limited resources.
• A community of users could add features that the company does not have the time or money to build itself.
• The company may lose control of the direction of the product if many outside contributors change the code in different ways.
• Proprietary development keeps the code within the company, so the team can maintain a consistent design and quality.
• Open-source code may be forked by competitors, creating rival versions of the application that the company does not control.

Levels

• Level 0 (0 marks): No rewardable content.
• Level 1 (1–2 marks): Basic, independent points are made, showing elements of understanding of key concepts/principles of computer science. (AO1) The discussion will contain basic information with little linkage between points made or application to the context. (AO2)
• Level 2 (3–4 marks): Demonstrates adequate understanding of key concepts/principles of computer science. (AO1) The discussion shows some linkages and lines of reasoning with some structure and application to the context. (AO2)
• Level 3 (5–6 marks): Demonstrates comprehensive understanding of key concepts/principles of computer science to support the discussion being presented. (AO1) The discussion is well developed, with sustained lines of reasoning that are coherent and logically structured, and which clearly apply to the context. (AO2)

Level 3 responses must consider both open-source and proprietary approaches and their effect on the company's profit or intellectual property; responses that discuss only one approach, or make only general points with little application to the company, are limited to Level 2.

Do not accept 'open-source is free' on its own, 'anyone can use it', or the claim that open-source software has no copyright; free download must be linked to the effect on the company's income.