In short
- Definition: The ease with which separately developed components or systems can be combined into a working whole.
- Goal: Reduce the effort and risk of connecting components and third-party systems.
- Example S.M.A.R.T. requirement: A new partner system connected through the documented API in under 10 person-days.
1. Definition
As a non-functional requirement, integrability describes how easily separately developed components or systems can be combined into a working whole [1], [2].
The real cost of a system often hides in its integrations. Make them cheap by design.Key takeaway
It depends on well-documented interfaces, standard protocols and data formats, clear contracts, versioning and good error handling. An API described with the OpenAPI Specification, for example, can be read by people and by tools that generate clients and tests [3].
Integrability is about the effort to connect; interoperability is about the ability to exchange and use information once connected.
2. Goal
The goal is to reduce the effort, time and risk of connecting components, partners and third-party systems.
Poor integrability leads to custom point-to-point code, fragile connections and long projects every time a new partner joins.
3. How to Measure It (S.M.A.R.T.)
| Metric | Unit | Typical target | How to measure |
|---|---|---|---|
| Effort to connect a new partner | Person-days | < 10 | Project time tracking |
| Interfaces with machine-readable contracts | % of APIs | 100% | API catalog |
| Integration defects | Defects per integration in the first month | < 3 | Defect tracker |
| Contract test coverage | % of interfaces with automated contract tests | 100% | CI reports |
4. Example Requirements
Each requirement below is ready to copy into a specification: specific, measurable, achievable, relevant and time-bound.
- Partner onboarding: “A new partner system shall be connected through the documented API in under 10 person-days, including testing.”
- API contracts: “Every public API shall be described in an OpenAPI document published in the developer portal and validated in CI.”
- Events: “Business events shall be published on the message bus with versioned schemas, so new consumers can subscribe without changes to the producer.”
5. Questions to Ask Stakeholders
- Which systems must this one connect to, now and later?
- Which integration styles are preferred: APIs, events, files?
- Which standards and formats are mandatory?
- Who owns each interface and its versioning?
- How will integrations be tested end to end?
- How are errors and retries handled between systems?
6. Common Pitfalls
- Undocumented interfaces. Every integrator must reverse-engineer them. Publish contracts.
- Point-to-point spaghetti. Each new link adds complexity. Use shared patterns or an integration layer.
- Breaking changes without versioning. Consumers fail without notice. Version and deprecate.
7. Related NFRs
- Categories of Non-Functional Requirements — the full checklist of NFR categories.
- Interoperability — exchanging and using information across systems.
- Conformance — following standards makes integration easier.
- Extensibility — extension points are a form of integration.
- Compatibility — integrations must survive upgrades on both sides.
8. FAQ
Integrability is about how easily systems can be connected; interoperability is about how well they exchange and use information once connected.
An automated test that checks that a provider and its consumers agree on the interface, without full end-to-end setups.
It provides a standard, machine-readable description of HTTP APIs that tools can use for documentation, code generation and testing.
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. |
|---|---|---|---|
| SMART | Specific, Measurable, Achievable, Relevant, Time-bound | Criteria for writing a goal or requirement so that anyone can check whether it has been met. | [4] |
Initialisms
| Abbreviation | Stands for | Definition | Ref. |
|---|---|---|---|
| API | Application programming interface | Defined way for one program to request data or services from another. | [5] |
| CI | Continuous integration | Practice of merging code changes often, with each change checked automatically by builds and tests. | [6] |
| FAQ | Frequently asked questions | List of common questions with their answers. | [7] |
| HTTP | Hypertext Transfer Protocol | The protocol browsers and services use to exchange data on the web. | [8] |
| 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] |
Terms
Plain-language definitions of technical and project-management terms used in this article.
| Term | Plain-language definition | Ref. |
|---|---|---|
| Code coverage | Share of the code exercised by automated tests. | [9] |
| Deprecation | Marking a feature as obsolete and scheduled for removal. | [10] |
| Schema | Formal description of how data is structured. | [11] |
| Stakeholder | Person or group with an interest in the system: users, sponsors, operators, regulators. | [12] |
10. Sources and Further Reading
- [1] “System integration.” Wikipedia. https://en.wikipedia.org/wiki/System_integration (accessed Nov. 18, 2026).
- [2] “Non-functional requirement.” Wikipedia. https://en.wikipedia.org/wiki/Non-functional_requirement (accessed Nov. 18, 2026).
- [3] “OpenAPI Specification v3.2.0.” OpenAPI Initiative. https://spec.openapis.org/oas/v3.2.0.html (accessed Nov. 18, 2026).
- [4] “SMART criteria.” Wikipedia. https://en.wikipedia.org/wiki/SMART_criteria (accessed Nov. 19, 2026).
- [5] “API.” Wikipedia. https://en.wikipedia.org/wiki/API (accessed Nov. 19, 2026).
- [6] “Continuous integration.” Wikipedia. https://en.wikipedia.org/wiki/Continuous_integration (accessed Nov. 19, 2026).
- [7] “FAQ.” Wikipedia. https://en.wikipedia.org/wiki/FAQ (accessed Nov. 19, 2026).
- [8] “HTTP.” Wikipedia. https://en.wikipedia.org/wiki/HTTP (accessed Nov. 19, 2026).
- [9] “Code coverage.” Wikipedia. https://en.wikipedia.org/wiki/Code_coverage (accessed Nov. 19, 2026).
- [10] “Deprecation.” Wikipedia. https://en.wikipedia.org/wiki/Deprecation (accessed Nov. 19, 2026).
- [11] “Database schema.” Wikipedia. https://en.wikipedia.org/wiki/Database_schema (accessed Nov. 19, 2026).
- [12] “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 @alanaprilio; inline photo by @ttepavac, both on Unsplash.








