In short
- Definition: The ability of a system to work alongside other systems, versions or components without conflict, including backward compatibility.
- Goal: Allow upgrades and coexistence without breaking existing users or integrations.
- Example S.M.A.R.T. requirement: 100% of existing API clients working with the new version, and files from the previous two versions opening correctly.
1. Definition
As a non-functional requirement, compatibility describes the ability of a system to work alongside other systems, versions or components without conflict, including with its own previous versions [1].
Breaking a client is easy. Rebuilding its trust is not.Key takeaway
In ISO/IEC 25010:2023, compatibility has two sub-characteristics: co-existence (sharing an environment without harming other products) and interoperability (exchanging and using information). Backward compatibility, keeping older clients, files and integrations working after an upgrade, is a frequent focus [2], [3].
Versioning conventions such as Semantic Versioning help communicate compatibility: a change of major version signals that something may break [4].
2. Goal
The goal is to allow upgrades and coexistence without breaking existing users, data or integrations.
Incompatible changes force everyone to upgrade at once, cause outages in dependent systems and make customers delay updates.
3. How to Measure It (S.M.A.R.T.)
| Metric | Unit | Typical target | How to measure |
|---|---|---|---|
| Existing API clients working after upgrade | % | 100% | Contract tests with recorded client calls |
| Files from previous versions opening correctly | % | 100% for the last 2 major versions | Regression test set |
| Breaking changes without notice | Count | 0 | Release notes review |
| Coexistence conflicts | Count | 0 | Installation tests on shared environments |
4. Example Requirements
Each requirement below is ready to copy into a specification: specific, measurable, achievable, relevant and time-bound.
- API: “100% of existing API clients shall keep working with each new minor version; breaking changes shall only be made in a new major version announced 6 months in advance.”
- Files: “Documents created with the two previous major versions shall open and save correctly in the new version.”
- Coexistence: “The desktop client shall install and run alongside the previous version without changing its settings.”
5. Questions to Ask Stakeholders
- Which clients, files and integrations depend on the current version?
- How long must older versions be supported?
- How will breaking changes be announced?
- Must several versions run side by side?
- Which shared libraries or resources could conflict?
- How will compatibility be tested?
6. Common Pitfalls
- Silent breaking changes. Renaming a field can break unknown clients. Version and announce.
- Supporting old versions forever. Set and publish a deprecation policy.
- Testing only new clients. Keep a suite of tests from older clients and files.
7. Related NFRs
- Categories of Non-Functional Requirements — the full checklist of NFR categories.
- Interoperability — part of compatibility in ISO/IEC 25010.
- Platform Compatibility — running on the required user platforms.
- Integrability — connections must survive upgrades.
- Conformance — shared standards support compatibility.
8. FAQ
The ability of a new version to keep working with clients, files or data made for older versions.
The ability to share an environment with other products without harming them.
It signals incompatible changes through the major version number, so users know what to expect.
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. | [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. |
|---|---|---|---|
| API | Application programming interface | Defined way for one program to request data or services from another. | [7] |
| FAQ | Frequently asked questions | List of common questions with their answers. | [8] |
| IEC | International Electrotechnical Commission | International standards body for electrical and electronic technologies; it publishes joint “ISO/IEC” standards with ISO. | [9] |
| 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. | [1] |
Terms
Plain-language definitions of technical and project-management terms used in this article.
| Term | Plain-language definition | Ref. |
|---|---|---|
| Deprecation | Marking a feature as obsolete and scheduled for removal. | [10] |
| Library | Reusable package of code that programs include instead of writing it themselves. | [11] |
| Regression | Bug where something that used to work stops working after a change. | [12] |
| Semantic Versioning | Version-number convention MAJOR.MINOR.PATCH that signals the kind of change. | [13] |
| Stakeholder | Person or group with an interest in the system: users, sponsors, operators, regulators. | [14] |
10. Sources and Further Reading
- [1] “Non-functional requirement.” Wikipedia. https://en.wikipedia.org/wiki/Non-functional_requirement (accessed Nov. 18, 2026).
- [2] “ISO/IEC 25010 product quality model.” ISO 25000. https://iso25000.com/index.php/en/iso-25000-standards/iso-25010 (accessed Nov. 18, 2026).
- [3] “Backward compatibility.” Wikipedia. https://en.wikipedia.org/wiki/Backward_compatibility (accessed Nov. 18, 2026).
- [4] semver.org. “Semantic Versioning 2.0.0.” Semantic Versioning. https://semver.org/ (accessed Nov. 18, 2026).
- [5] “International Organization for Standardization.” Wikipedia. https://en.wikipedia.org/wiki/International_Organization_for_Standardization (accessed Nov. 19, 2026).
- [6] “SMART criteria.” Wikipedia. https://en.wikipedia.org/wiki/SMART_criteria (accessed Nov. 19, 2026).
- [7] “API.” Wikipedia. https://en.wikipedia.org/wiki/API (accessed Nov. 19, 2026).
- [8] “FAQ.” Wikipedia. https://en.wikipedia.org/wiki/FAQ (accessed Nov. 19, 2026).
- [9] “International Electrotechnical Commission.” Wikipedia. https://en.wikipedia.org/wiki/International_Electrotechnical_Commission (accessed Nov. 19, 2026).
- [10] “Deprecation.” Wikipedia. https://en.wikipedia.org/wiki/Deprecation (accessed Nov. 19, 2026).
- [11] “Library (computing).” Wikipedia. https://en.wikipedia.org/wiki/Library_(computing) (accessed Nov. 19, 2026).
- [12] “Software regression.” Wikipedia. https://en.wikipedia.org/wiki/Software_regression (accessed Nov. 19, 2026).
- [13] “Software versioning.” Wikipedia. https://en.wikipedia.org/wiki/Software_versioning (accessed Nov. 19, 2026).
- [14] “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 @marcusurbenz; inline photo by @abrkett, both on Unsplash.








