In short
- Definition: The ability of a system to exchange information with other systems and use the information exchanged.
- Goal: Make the system work smoothly within a wider ecosystem of tools and partners.
- Example S.M.A.R.T. requirement: 100% of messages valid against the agreed format, and fewer than 0.1% rejected by partner systems.
1. Definition
As a non-functional requirement, interoperability describes the ability of a system to exchange information with other systems and to use the information it receives [1], [2].
Two systems can exchange perfectly valid files and still disagree on what a “customer” is. Agree on meaning, not only on format.Key takeaway
In ISO/IEC 25010:2023, interoperability is a sub-characteristic of compatibility. It works at several levels: technical (connecting), syntactic (common formats), semantic (shared meaning of the data) and organizational (agreed processes) [3].
Interoperability usually relies on shared standards: data formats, APIs, code lists and protocols, often specific to a sector such as health, finance or government.
2. Goal
The goal is to make the system work smoothly within a wider ecosystem of tools, partners and public services.
Poor interoperability means manual re-entry, error-prone conversions and data that loses meaning between systems.
3. How to Measure It (S.M.A.R.T.)
| Metric | Unit | Typical target | How to measure |
|---|---|---|---|
| Messages valid against the agreed format | % | 100% | Schema validation logs |
| Messages rejected by partners | % | < 0.1% | Partner acknowledgments |
| Supported standards | List | As specified | Conformance statement |
| Semantic errors | Count per month | Decreasing trend | Reconciliation and partner feedback |
4. Example Requirements
Each requirement below is ready to copy into a specification: specific, measurable, achievable, relevant and time-bound.
- Partner exchange: “100% of messages sent to partners shall validate against the agreed schema, and fewer than 0.1% shall be rejected by partner systems each month.”
- Health data: “Patient records shall be exchanged using the national health data standard and its official code lists.”
- Open data: “Public datasets shall be published in an open, documented format with a published data dictionary.”
5. Questions to Ask Stakeholders
- Which systems and organizations must exchange data with ours?
- Which standards are mandatory in our sector or country?
- Which code lists and definitions must be shared?
- Which versions of each standard must be supported?
- How will partners test their connections?
- Who resolves disagreements about data meaning?
6. Common Pitfalls
- Only syntactic agreement. Same format, different meaning. Share a data dictionary.
- Custom formats. Proprietary formats lock partners in. Prefer open standards.
- No partner testing. Validate with real partners before go-live.
7. Related NFRs
- Categories of Non-Functional Requirements — the full checklist of NFR categories.
- Integrability — how easily systems can be connected in the first place.
- Conformance — strict adherence to the shared standards.
- Compatibility — ISO/IEC 25010 places interoperability under compatibility.
- Data Integrity — exchanged data must stay accurate.
8. FAQ
Commonly: technical (connection), syntactic (format), semantic (meaning) and organizational (processes and agreements).
No. Partners also need shared formats, meanings and rules for using the data.
Validate messages against schemas and run joint tests with partner systems.
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. |
|---|---|---|---|
| ISO | International Organization for Standardization | Independent international body that publishes standards, such as ISO/IEC 25010 for software quality. Its short name comes from the Greek “isos” (equal) and is said as a word. | [4] |
| 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. |
|---|---|---|---|
| API | Application programming interface | Defined way for one program to request data or services from another. | [6] |
| FAQ | Frequently asked questions | List of common questions with their answers. | [7] |
| IEC | International Electrotechnical Commission | International standards body for electrical and electronic technologies; it publishes joint “ISO/IEC” standards with ISO. | [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. |
|---|---|---|
| Log | Time-stamped record of events written by software, used for troubleshooting and audit. | [9] |
| Schema | Formal description of how data is structured. | [10] |
| Stakeholder | Person or group with an interest in the system: users, sponsors, operators, regulators. | [11] |
10. Sources and Further Reading
- [1] “Interoperability.” Wikipedia. https://en.wikipedia.org/wiki/Interoperability (accessed Nov. 18, 2026).
- [2] “Non-functional requirement.” Wikipedia. https://en.wikipedia.org/wiki/Non-functional_requirement (accessed Nov. 18, 2026).
- [3] “ISO/IEC 25010 product quality model.” ISO 25000. https://iso25000.com/index.php/en/iso-25000-standards/iso-25010 (accessed Nov. 18, 2026).
- [4] “International Organization for Standardization.” Wikipedia. https://en.wikipedia.org/wiki/International_Organization_for_Standardization (accessed Nov. 19, 2026).
- [5] “SMART criteria.” Wikipedia. https://en.wikipedia.org/wiki/SMART_criteria (accessed Nov. 19, 2026).
- [6] “API.” Wikipedia. https://en.wikipedia.org/wiki/API (accessed Nov. 19, 2026).
- [7] “FAQ.” Wikipedia. https://en.wikipedia.org/wiki/FAQ (accessed Nov. 19, 2026).
- [8] “International Electrotechnical Commission.” Wikipedia. https://en.wikipedia.org/wiki/International_Electrotechnical_Commission (accessed Nov. 19, 2026).
- [9] “Logging (computing).” Wikipedia. https://en.wikipedia.org/wiki/Logging_(computing) (accessed Nov. 19, 2026).
- [10] “Database schema.” Wikipedia. https://en.wikipedia.org/wiki/Database_schema (accessed Nov. 19, 2026).
- [11] “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 @cbpsc1; inline photo by @kit, both on Unsplash.








