In short
- Definition: The requirement or preference that a system, or its components, be published under an open-source license, or be built from open-source components.
- Goal: Benefit from transparency, community contributions and freedom from vendor lock-in.
- Example S.M.A.R.T. requirement: 100% of the product released under the chosen license, with community issues answered within 5 business days.
1. Definition
As a non-functional requirement, open source describes the requirement, or preference, that a system or its components be built from open-source software, or be published under an open-source license [1], [2].
Open source is free to obtain, not free to own. Someone still has to maintain it.Key takeaway
The Open Source Initiative defines open-source software as software distributed under a license that meets its Open Source Definition: it can be used, studied, modified and shared freely [3], [4]. Licenses approved by the OSI, such as MIT, Apache-2.0 or the GPL family, meet these criteria.
Public organizations increasingly require open source to avoid lock-in and reuse what others have built; companies publish code to build communities or standards. Both cases need clear rules on licenses, contributions and maintenance.
2. Goal
The goal is to benefit from transparency, community contributions, reuse and freedom from vendor lock-in.
Without a clear open-source requirement, teams may pick unsuitable licenses, rely on abandoned projects or publish code without the governance to sustain it.
3. How to Measure It (S.M.A.R.T.)
| Metric | Unit | Typical target | How to measure |
|---|---|---|---|
| Product released under an approved license | Yes/No | Yes, under the chosen OSI-approved license | Repository license file and review |
| Components under approved open-source licenses | % | As set by policy (e.g., 100% for public-sector code) | SBOM |
| Response to community issues | Business days | < 5 | Repository statistics |
| Health of key dependencies | Active maintainers and recent releases | At least 2 maintainers and a release in the last 12 months | Dependency review |
4. Example Requirements
Each requirement below is ready to copy into a specification: specific, measurable, achievable, relevant and time-bound.
- Public sector: “All custom code developed for the project shall be published under the EUPL-1.2 or another OSI-approved license chosen by the client, in a public repository, at each release.”
- Community: “Issues opened by external contributors shall receive a first answer within 5 business days.”
- Dependencies: “Critical open-source dependencies shall have at least two active maintainers or a documented plan to replace or support them.”
5. Questions to Ask Stakeholders
- Must the system be open source, use open source, or both?
- Which licenses are acceptable for our business model?
- Who will maintain the public repository and review contributions?
- How will we check the health of the projects we depend on?
- Do contributors need to sign an agreement?
- How will security issues be reported and handled?
6. Common Pitfalls
- Publishing without governance. A public repository needs maintainers, contribution rules and a security policy.
- Depending on abandoned projects. Check activity and maintainers before relying on a component.
- Choosing a license late. The license shapes what others may do. Decide it early.
7. Related NFRs
- Categories of Non-Functional Requirements — the full checklist of NFR categories.
- Legal and Licensing — licenses define obligations when using and publishing open source.
- Dependency on Other Parties — open-source projects are dependencies too.
- Transparency — publishing code makes behavior inspectable.
- Reusability — open source enables reuse across organizations.
8. FAQ
It must meet the Open Source Definition and, in practice, be approved by the Open Source Initiative.
Usually free to obtain, but integration, support, security and maintenance still cost time and money.
Yes. Many business models exist, such as support, hosting, or additional proprietary features.
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. |
|---|---|---|---|
| EUPL | European Union Public Licence | Copyleft open-source license created by the European Commission. | [7] |
| FAQ | Frequently asked questions | List of common questions with their answers. | [8] |
| GPL | GNU General Public License | Copyleft open-source license: modified versions that are distributed must stay under the same license. | [9] |
| MIT | Massachusetts Institute of Technology (MIT License) | Short, permissive open-source license named after the university where it originated. | [10] |
| 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. | [2] |
| OSI | Open Source Initiative | Organization that reviews and approves open-source licenses. | [11] |
Terms
Plain-language definitions of technical and project-management terms used in this article.
| Term | Plain-language definition | Ref. |
|---|---|---|
| Governance | Rules, roles and decision processes that steer how IT is managed. | [12] |
| Stakeholder | Person or group with an interest in the system: users, sponsors, operators, regulators. | [13] |
| Vendor lock-in | Dependence on one supplier that makes switching costly or difficult. | [14] |
10. Sources and Further Reading
- [1] “Open-source software.” Wikipedia. https://en.wikipedia.org/wiki/Open-source_software (accessed Nov. 18, 2026).
- [2] “Non-functional requirement.” Wikipedia. https://en.wikipedia.org/wiki/Non-functional_requirement (accessed Nov. 18, 2026).
- [3] “What is Open Source?.” Open Source Initiative. https://opensource.org/education/what-is-open-source (accessed Nov. 18, 2026).
- [4] “OSI Approved Licenses.” Open Source Initiative. https://opensource.org/licenses (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] “European Union Public Licence.” Wikipedia. https://en.wikipedia.org/wiki/European_Union_Public_Licence (accessed Nov. 19, 2026).
- [8] “FAQ.” Wikipedia. https://en.wikipedia.org/wiki/FAQ (accessed Nov. 19, 2026).
- [9] “GNU General Public License.” Wikipedia. https://en.wikipedia.org/wiki/GNU_General_Public_License (accessed Nov. 19, 2026).
- [10] “MIT License.” Wikipedia. https://en.wikipedia.org/wiki/MIT_License (accessed Nov. 19, 2026).
- [11] “Open Source Initiative.” Wikipedia. https://en.wikipedia.org/wiki/Open_Source_Initiative (accessed Nov. 19, 2026).
- [12] “Corporate governance of information technology.” Wikipedia. https://en.wikipedia.org/wiki/Corporate_governance_of_information_technology (accessed Nov. 19, 2026).
- [13] “Project stakeholder.” Wikipedia. https://en.wikipedia.org/wiki/Project_stakeholder (accessed Nov. 19, 2026).
- [14] “Vendor lock-in.” Wikipedia. https://en.wikipedia.org/wiki/Vendor_lock-in (accessed Nov. 19, 2026).
Written by Philippe Huard · LinkedIn · Last updated: November 18, 2026 · Header photo by @cdr6934; inline photo by @jacksonsophat, both on Unsplash.








