In short
- Definition: The requirement that a system respects software licenses, intellectual property and patents, and is free of legal risks related to them.
- Goal: Avoid lawsuits, license violations and forced redesigns.
- Example S.M.A.R.T. requirement: 100% of third-party components with an approved license recorded in a software bill of materials, and zero incompatible licenses at release.
1. Definition
As a non-functional requirement, legal and licensing describes the obligation for a system to respect software licenses, copyrights, patents and other intellectual property, and to avoid the legal risks attached to them [1], [2], [3].
“We did not know that library was there” is not a defense. Know what you ship.Key takeaway
Modern software contains many third-party components, mostly open source. Each comes with a license: permissive ones such as MIT or Apache-2.0, and copyleft ones such as the GPL family that impose conditions when software is distributed. Commercial components bring their own terms, user counts and audit rights.
Tools such as a software bill of materials (SBOM) and standard license identifiers from the SPDX License List make it possible to know which licenses are in a product and check them automatically [4].
2. Goal
The goal is to avoid lawsuits, license violations, surprise audit bills and forced redesigns.
License problems found late can block a sale, an acquisition or a release, or force the team to replace a component under pressure.
3. How to Measure It (S.M.A.R.T.)
| Metric | Unit | Typical target | How to measure |
|---|---|---|---|
| Components with an identified license | % of components in the SBOM | 100% | SBOM generation in CI |
| Incompatible or forbidden licenses | Count at release | 0 | License policy check |
| Commercial license compliance | Users or instances versus entitlements | Within entitlements | License management tool |
| Legal review of new components | % reviewed before use | 100% of non-approved licenses | Approval workflow |
4. Example Requirements
Each requirement below is ready to copy into a specification: specific, measurable, achievable, relevant and time-bound.
- Open source policy: “Every release shall include an SBOM listing all third-party components with their SPDX license identifiers, and contain zero components under licenses on the forbidden list.”
- Distribution: “Before distributing the mobile app, all required license notices and attributions shall be included in the app’s legal screen.”
- Commercial software: “The number of named users of the reporting tool shall never exceed the purchased licenses, checked monthly.”
5. Questions to Ask Stakeholders
- Will the software be distributed to customers, or only run as a service?
- Which open-source licenses are allowed, restricted or forbidden?
- Which commercial licenses are used, and how are they counted?
- Who approves new third-party components?
- Are there patents or trademarks to consider?
- Do contracts with clients restrict the components we can use?
6. Common Pitfalls
- Ignoring transitive dependencies. Libraries pull in other libraries, each with its own license. Scan the full tree.
- Assuming open source means no obligations. Many licenses require notices, source availability or the same license for derived works.
- Losing track of commercial entitlements. Over-deployment leads to audit bills. Track usage.
7. Related NFRs
- Open Source — covers using and publishing open-source software.
- Compliance — license respect is part of overall compliance.
- Dependency on Other Parties — licenses define what you may do with third-party components.
- Escrow — protects access to licensed source code.
8. FAQ
A software bill of materials: a list of all components and their versions and licenses in a piece of software.
Permissive licenses allow reuse with few conditions; copyleft licenses require derived works to be shared under the same terms when distributed.
Yes. Some licenses, such as the AGPL, also apply when software is offered over a network.
9. Acronyms, Initialisms & Terms
Acronyms are abbreviations pronounced as words (like NASA); initialisms are spelled out letter by letter (like FBI). The classification below follows common pronunciation.
Acronyms
| Abbreviation | Stands for | Definition | Ref. |
|---|---|---|---|
| SBOM | Software bill of materials | Complete inventory of the components and libraries inside a piece of software, used to track licenses and vulnerabilities. | [5] |
| SMART | Specific, Measurable, Achievable, Relevant, Time-bound | Criteria for writing a goal or requirement so that anyone can check whether it has been met. | [6] |
Initialisms
| Abbreviation | Stands for | Definition | Ref. |
|---|---|---|---|
| AGPL | GNU Affero General Public License | Copyleft license like the GPL that also applies when the software is offered as a network service. | [7] |
| CI | Continuous integration | Practice of merging code changes often, with each change checked automatically by builds and tests. | [8] |
| FAQ | Frequently asked questions | List of common questions with their answers. | [9] |
| GPL | GNU General Public License | Copyleft open-source license: modified versions that are distributed must stay under the same license. | [10] |
| MIT | Massachusetts Institute of Technology (MIT License) | Short, permissive open-source license named after the university where it originated. | [11] |
| NFR | Non-functional requirement | Requirement that describes how well a system must work (its qualities, such as speed or security) rather than what it does. | [3] |
| SaaS | Software as a service | Software rented and used over the internet rather than installed locally. | [12] |
| SPDX | Software Package Data Exchange | Open standard for describing software components and their licenses. | [13] |
Terms
Plain-language definitions of technical and project-management terms used in this article.
| Term | Plain-language definition | Ref. |
|---|---|---|
| Copyleft | License rule requiring that modified versions be shared under the same license. | [14] |
| Deployment | Installing a new version of software in the environment where people use it. | [15] |
| Library | Reusable package of code that programs include instead of writing it themselves. | [16] |
| Open source | Software whose source code is published under a license that lets anyone use, change and share it. | [17] |
| Permissive license | Open-source license with few conditions, allowing reuse even in closed products. | [18] |
| Stakeholder | Person or group with an interest in the system: users, sponsors, operators, regulators. | [19] |
10. Sources and Further Reading
- [1] “OSI Approved Licenses.” Open Source Initiative. https://opensource.org/licenses (accessed Nov. 18, 2026).
- [2] “Software license.” Wikipedia. https://en.wikipedia.org/wiki/Software_license (accessed Nov. 18, 2026).
- [3] “Non-functional requirement.” Wikipedia. https://en.wikipedia.org/wiki/Non-functional_requirement (accessed Nov. 18, 2026).
- [4] “Handling License Info, SPDX License List.” SPDX. https://spdx.dev/learn/handling-license-info/ (accessed Nov. 18, 2026).
- [5] “Software supply chain.” Wikipedia. https://en.wikipedia.org/wiki/Software_supply_chain (accessed Nov. 19, 2026).
- [6] “SMART criteria.” Wikipedia. https://en.wikipedia.org/wiki/SMART_criteria (accessed Nov. 19, 2026).
- [7] “GNU Affero General Public License.” Wikipedia. https://en.wikipedia.org/wiki/GNU_Affero_General_Public_License (accessed Nov. 19, 2026).
- [8] “Continuous integration.” Wikipedia. https://en.wikipedia.org/wiki/Continuous_integration (accessed Nov. 19, 2026).
- [9] “FAQ.” Wikipedia. https://en.wikipedia.org/wiki/FAQ (accessed Nov. 19, 2026).
- [10] “GNU General Public License.” Wikipedia. https://en.wikipedia.org/wiki/GNU_General_Public_License (accessed Nov. 19, 2026).
- [11] “MIT License.” Wikipedia. https://en.wikipedia.org/wiki/MIT_License (accessed Nov. 19, 2026).
- [12] “Software as a service.” Wikipedia. https://en.wikipedia.org/wiki/Software_as_a_service (accessed Nov. 19, 2026).
- [13] “Software Package Data Exchange.” Wikipedia. https://en.wikipedia.org/wiki/Software_Package_Data_Exchange (accessed Nov. 19, 2026).
- [14] “Copyleft.” Wikipedia. https://en.wikipedia.org/wiki/Copyleft (accessed Nov. 19, 2026).
- [15] “Software deployment.” Wikipedia. https://en.wikipedia.org/wiki/Software_deployment (accessed Nov. 19, 2026).
- [16] “Library (computing).” Wikipedia. https://en.wikipedia.org/wiki/Library_(computing) (accessed Nov. 19, 2026).
- [17] “Open-source software.” Wikipedia. https://en.wikipedia.org/wiki/Open-source_software (accessed Nov. 19, 2026).
- [18] “Permissive software license.” Wikipedia. https://en.wikipedia.org/wiki/Permissive_software_license (accessed Nov. 19, 2026).
- [19] “Project stakeholder.” Wikipedia. https://en.wikipedia.org/wiki/Project_stakeholder (accessed Nov. 19, 2026).
Written by Philippe Huard · LinkedIn · Last updated: November 18, 2026 · Header photo by @jakubzerdzicki; inline photo by @amstram, both on Unsplash.




