In short
- Definition: The ease with which a system can be changed to handle future, possibly unforeseen, requirements.
- Goal: Keep the cost of future change low.
- Example S.M.A.R.T. requirement: 80% of change requests implemented in under 5 person-days without architectural change.
1. Definition
As a non-functional requirement, flexibility describes how easily a system can be changed to handle future requirements, including ones nobody can predict today [1], [2].
Flexibility is not making everything changeable. It is making the likely changes cheap.Key takeaway
In ISO/IEC 25010:2023, flexibility is a top-level characteristic that replaced portability. It groups adaptability, scalability, installability and replaceability [3].
Flexibility comes from design choices: modular architecture, clear interfaces, configuration over code, and avoiding decisions that are hard to reverse. It always has a cost, so the requirement should say where flexibility is worth paying for.
2. Goal
The goal is to keep the cost of future change low, so the system can follow the business instead of slowing it down.
Rigid systems turn small business changes into large projects, and push teams towards workarounds or replacement.
3. How to Measure It (S.M.A.R.T.)
| Metric | Unit | Typical target | How to measure |
|---|---|---|---|
| Effort for typical changes | Person-days per change request | 80% under 5 person-days | Change request tracking |
| Changes needing architectural rework | % of change requests | < 10% | Change review |
| Lead time for business rule changes | Days | < 10 | Ticket timestamps |
| Coupling indicators | Modules affected per change | ≤ 3 on average | Code analysis of changes |
4. Example Requirements
Each requirement below is ready to copy into a specification: specific, measurable, achievable, relevant and time-bound.
- Business rules: “80% of change requests to pricing rules shall be implemented in under 5 person-days without architectural change, measured each quarter.”
- Product catalog: “New product types shall be addable through configuration, without code change, within 2 days.”
- Architecture: “Replacing the payment provider shall require changes only in the payment integration module.”
5. Questions to Ask Stakeholders
- Which parts of the business are most likely to change?
- How often do rules, products or processes change today?
- Which changes must business users make themselves?
- Which decisions would be expensive to reverse later?
- What is acceptable lead time for a typical change?
- How much are we willing to invest now for future flexibility?
6. Common Pitfalls
- Building for every possible future. Speculative generality adds complexity. Focus on likely changes.
- Tight coupling. Shared databases and hidden dependencies make every change ripple.
- Ignoring data. Rigid data models often block change more than code does.
7. Related NFRs
- Categories of Non-Functional Requirements — the full checklist of NFR categories.
- Adaptability — fitting new contexts, a sub-characteristic of flexibility.
- Modifiability — changing code safely.
- Extensibility — adding features through extension points.
- Scalability — part of flexibility in ISO/IEC 25010:2023.
- Portability — moving to other platforms.
8. FAQ
In the 2023 edition, flexibility replaced portability as a top-level characteristic, with adaptability, scalability, installability and replaceability under it.
Through the effort and lead time of real change requests over time.
No. It adds cost and complexity. Invest where change is likely and costly.
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. |
|---|---|---|---|
| FAQ | Frequently asked questions | List of common questions with their answers. | [6] |
| IEC | International Electrotechnical Commission | International standards body for electrical and electronic technologies; it publishes joint “ISO/IEC” standards with ISO. | [7] |
| 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. |
|---|---|---|
| Database | Organized store of data that software can query and update. | [8] |
| Stakeholder | Person or group with an interest in the system: users, sponsors, operators, regulators. | [9] |
10. Sources and Further Reading
- [1] “Flexibility (engineering).” Wikipedia. https://en.wikipedia.org/wiki/Flexibility_(engineering) (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] “FAQ.” Wikipedia. https://en.wikipedia.org/wiki/FAQ (accessed Nov. 19, 2026).
- [7] “International Electrotechnical Commission.” Wikipedia. https://en.wikipedia.org/wiki/International_Electrotechnical_Commission (accessed Nov. 19, 2026).
- [8] “Database.” Wikipedia. https://en.wikipedia.org/wiki/Database (accessed Nov. 19, 2026).
- [9] “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 @worldsbetweenlines; inline photo by @bamin, both on Unsplash.








