In short
- Definition: The extent to which a system relies on external suppliers, services, components or teams to operate or evolve.
- Goal: Identify and control the risks created by third parties, such as outages, price changes or end of support.
- Example S.M.A.R.T. requirement: 100% of critical third-party services covered, with no single supplier able to stop the service for more than 4 hours.
1. Definition
As a non-functional requirement, dependency on other parties describes how much a system relies on external suppliers, cloud services, open-source components, partners or other internal teams to work and to evolve [1], [2], [3].
You cannot remove every dependency, but you can decide which ones you are willing to bet the service on.Key takeaway
Every dependency brings a risk: outage, price increase, end of support, security flaw, change of terms or supplier failure. The requirement is to know these dependencies, limit the critical ones and have a plan for each.
This includes vendor lock-in: the cost of leaving a supplier can become so high that the organization loses its negotiating power [4].
2. Goal
The goal is to identify and control the risks created by third parties, so that no single supplier can stop the service or impose unacceptable conditions.
Unmanaged dependencies surface at the worst time: during a supplier outage, a security alert in a library nobody knew was used, or a sudden price change.
3. How to Measure It (S.M.A.R.T.)
| Metric | Unit | Typical target | How to measure |
|---|---|---|---|
| Critical dependencies documented | % with contract, SLA and exit plan | 100% | Dependency register |
| Maximum impact of one supplier outage | Hours of service interruption | < 4 h | Architecture review and failover tests |
| Unsupported components in use | Count | 0 | Software inventory and SBOM |
| Supplier SLA met | % of months | ≥ 95% | Supplier performance reports |
4. Example Requirements
Each requirement below is ready to copy into a specification: specific, measurable, achievable, relevant and time-bound.
- Cloud services: “Every third-party service rated critical shall have a documented contract, SLA and exit plan before go-live, reviewed yearly.”
- Resilience: “No single external supplier shall be able to interrupt order taking for more than 4 hours; this shall be verified by a failover test twice a year.”
- Components: “The system shall contain no component past its end of support, as shown by the monthly software bill of materials scan.”
5. Questions to Ask Stakeholders
- Which external services, suppliers and teams does the system depend on?
- Which of them could stop the service if they failed?
- What do contracts and SLAs guarantee, and what are the penalties?
- How hard would it be to replace each critical supplier?
- Who monitors suppliers’ security and financial health?
- What happens to our data if a supplier stops its service?
6. Common Pitfalls
- Not knowing all dependencies. Hidden ones, such as libraries or SaaS tools adopted by teams, are often the riskiest. Keep an inventory.
- Trusting the supplier’s SLA alone. An SLA gives compensation, not uptime. Design for the supplier’s failure.
- No exit plan. Plan data export and replacement before you need them.
7. Related NFRs
- Escrow — protects access to source code if a supplier fails.
- Portability — makes it easier to switch platforms or suppliers.
- Legal and Licensing — licenses and contracts define what you may do with third-party components.
- Availability — a service is only as available as its critical dependencies allow.
- Security — third-party components are a frequent source of vulnerabilities.
8. FAQ
A situation where leaving a supplier is so costly or complex that the customer is effectively stuck with it.
A list of all components and libraries in a piece of software, used to track licenses, versions and vulnerabilities.
No. They often bring value and reliability. The aim is to choose them knowingly and plan for their failure.
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. | [1] |
| SMART | Specific, Measurable, Achievable, Relevant, Time-bound | Criteria for writing a goal or requirement so that anyone can check whether it has been met. | [5] |
Initialisms
| Abbreviation | Stands for | Definition | Ref. |
|---|---|---|---|
| FAQ | Frequently asked questions | List of common questions with their answers. | [6] |
| 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. | [7] |
| SLA | Service level agreement | Contract that commits a provider to a level of service, with remedies if it is missed. | [8] |
Terms
Plain-language definitions of technical and project-management terms used in this article.
| Term | Plain-language definition | Ref. |
|---|---|---|
| Cloud | Computing resources (servers, storage, services) rented over the internet from a provider. | [9] |
| Failover | Automatic switch to a standby component when the main one fails. | [10] |
| Library | Reusable package of code that programs include instead of writing it themselves. | [11] |
| Open source | Software whose source code is published under a license that lets anyone use, change and share it. | [12] |
| Stakeholder | Person or group with an interest in the system: users, sponsors, operators, regulators. | [13] |
| Uptime | Time during which a system is working and available. | [14] |
| Vendor lock-in | Dependence on one supplier that makes switching costly or difficult. | [4] |
| Vulnerability | Weakness in software that an attacker could exploit. | [15] |
10. Sources and Further Reading
- [1] “Software supply chain.” Wikipedia. https://en.wikipedia.org/wiki/Software_supply_chain (accessed Nov. 18, 2026).
- [2] “Contingency Planning Guide for Federal Information Systems, SP 800-34 Rev. 1.” NIST. https://www.nist.gov/publications/contingency-planning-guide-federal-information-systems-including-updates-through (accessed Nov. 18, 2026).
- [3] “Non-functional requirement.” Wikipedia. https://en.wikipedia.org/wiki/Non-functional_requirement (accessed Nov. 18, 2026).
- [4] “Vendor lock-in.” Wikipedia. https://en.wikipedia.org/wiki/Vendor_lock-in (accessed Nov. 18, 2026).
- [5] “SMART criteria.” Wikipedia. https://en.wikipedia.org/wiki/SMART_criteria (accessed Nov. 19, 2026).
- [6] “FAQ.” Wikipedia. https://en.wikipedia.org/wiki/FAQ (accessed Nov. 19, 2026).
- [7] “Software as a service.” Wikipedia. https://en.wikipedia.org/wiki/Software_as_a_service (accessed Nov. 19, 2026).
- [8] “Service-level agreement.” Wikipedia. https://en.wikipedia.org/wiki/Service-level_agreement (accessed Nov. 19, 2026).
- [9] “Cloud computing.” Wikipedia. https://en.wikipedia.org/wiki/Cloud_computing (accessed Nov. 19, 2026).
- [10] “Failover.” Wikipedia. https://en.wikipedia.org/wiki/Failover (accessed Nov. 19, 2026).
- [11] “Library (computing).” Wikipedia. https://en.wikipedia.org/wiki/Library_(computing) (accessed Nov. 19, 2026).
- [12] “Open-source software.” Wikipedia. https://en.wikipedia.org/wiki/Open-source_software (accessed Nov. 19, 2026).
- [13] “Project stakeholder.” Wikipedia. https://en.wikipedia.org/wiki/Project_stakeholder (accessed Nov. 19, 2026).
- [14] “Uptime.” Wikipedia. https://en.wikipedia.org/wiki/Uptime (accessed Nov. 19, 2026).
- [15] “Vulnerability (computer security).” Wikipedia. https://en.wikipedia.org/wiki/Vulnerability_(computer_security) (accessed Nov. 19, 2026).
Written by Philippe Huard · LinkedIn · Last updated: November 18, 2026 · Header photo by @markusspiske; inline photo by @kar111, both on Unsplash.




