Community resourceWorksheet

J277 1.6.1 Open-source and proprietary licences

Part 4 of 5 · J277 1.6 · Digital impacts: Essentials

Open-source and proprietary licences, linking their permissions to users' and developers' needs.

Students will:

  • compare defining licence features
  • explain contextual benefits and drawbacks
  • distinguish source access from copyright ownership
  • avoid automatic claims about cost, support or security
  • justify a suitable licence or support choice

Inside: 3 text sections, 3 multiple-choice activities, 1 completion activity, 6 written answers. 18 marks. Suggested teaching time: 40–60 minutes. 1 diagram.

Includes a teacher guide with suggested sections, timings and common misconceptions.

Series: J277 1.6 · Digital impacts: Essentials, part 4 of 5.

Shared by Coding PathwayVerified teacher

  • 13 cells
  • About 45 minutes
  • CC BY-SA 4.0
  • Shared 17 Aug 2026
  • Updated 27 Oct 2026

Preview

The whole resource, exactly as a class sees it. Answers and marking are held back.

Open-source and proprietary licences

A software licence grants permission for uses such as installing, copying, changing or distributing software. It sets conditions for those uses.

LicenceDefining features
Open sourceSource code is available, and users may change and redistribute the software under its licence conditions.
ProprietarySource code is normally not supplied to users; the owner controls the permissions granted. It is commonly sold as an off-the-shelf product or subscription.

Both can have copyright. Open source does not necessarily mean no charge; proprietary software can also be free to use. Publishing code without a suitable licence is not enough to make it open source.

Permissions depend on the licence Open-source licences provide source-code access and rights to change the software under conditions. Proprietary licences normally withhold the source and restrict user permissions. Copyright can apply to both. Open sourceAccess and change source codeFollow the licence conditions ProprietarySource code normally withheldOwner grants restricted rights Both can have copyright and conditions.
Fill in the blanks3 marks
An Answer 1 licence provides access to the Answer 2 and permits changes under its terms. A Answer 3 licence normally restricts users' access to that code.
  • source code
  • open-source
  • proprietary
  • unlimited copying
  • password
Multiple choice1 mark

Which statement about open-source software is accurate?

  • AIt is always supplied at no charge
  • BIts licence permits source-code access and modification, with conditions
  • CIt cannot be sold or used by a business
  • DCopyright stops applying as soon as code is published
Written answer2 marks

State two defining features of open-source software.

Students type their answer here.

1. Match features to needs

Users may adapt open-source software, inspect how it works or contribute fixes. They still need the skill and time to maintain changes; support depends on the project or supplier.

A proprietary developer can control official changes and distribution, and may earn income from licences. Users may receive supplier support, but can depend on that supplier for changes and may face continuing costs.

Neither model guarantees quality, security or support. Check the actual licence and service.

Written answer2 marks

A community group needs its booking software to use different labels and symbols. Its volunteers can program. Explain one benefit of an open-source release for the group.

Students type their answer here.

Written answer2 marks

A group has changed an open-source program. Its programming volunteer then leaves. Explain one possible drawback for the group.

Students type their answer here.

Written answer2 marks

A small software company wants to control official changes and distribution of its program. Explain one way a proprietary licence could help.

Students type their answer here.

Written answer2 marks

A school needs a feature changed in a proprietary program. Explain one possible drawback for the school.

Students type their answer here.

Multiple choice1 mark

An organisation needs adapted software and dependable support. What should it check before choosing a licence model?

  • AWhether the software has the longest name
  • BWhether open source guarantees no faults
  • CThe actual modification rights, support arrangements and maintenance responsibilities
  • DWhether proprietary means no copyright
Written answer2 marks

A local history group wants volunteers to adapt and share its new catalogue program with other groups. Recommend open source or proprietary and explain why your choice fits this aim.

Students type their answer here.

Multiple choice1 mark

An open-source developer releases code under a licence requiring retained copyright notices. What should a person redistributing it do?

  • ARemove the notices because open source has no copyright
  • BFollow the licence condition and retain the required notices
  • CAssume nobody owns any rights
  • DRename the author without checking any terms

Review

Check that a reason explains a licence feature and its effect on the stated developer or user. A price, security or support claim needs appropriate qualification.