In short
- Definition: The degree to which a system can be changed without introducing defects or degrading quality.
- Goal: Make changes safe and predictable.
- Example S.M.A.R.T. requirement: Typical changes affecting no more than 3 modules, and fewer than 2% of changes causing a regression.
1. Definition
As a non-functional requirement, modifiability describes how easily a system can be changed without introducing defects or degrading its quality [1].
A change that touches ten modules will eventually break one of them.Key takeaway
In ISO/IEC 25010:2023, modifiability is a sub-characteristic of maintainability. It depends on low coupling (changes stay local), high cohesion (related logic stays together), clear interfaces and good automated tests that catch regressions [2], [3].
Modifiability is often discussed in software architecture as a key quality attribute, analyzed with change scenarios: “if we change X, how many modules are affected and how long does it take?”
2. Goal
The goal is to make changes safe and predictable, so the team can evolve the system with confidence.
Low modifiability turns every change into a risk, slows delivery and leads teams to avoid touching parts of the code.
3. How to Measure It (S.M.A.R.T.)
| Metric | Unit | Typical target | How to measure |
|---|---|---|---|
| Modules affected per typical change | Count | ≤ 3 | Analysis of merged changes |
| Regression rate | % of changes causing a regression | < 2% | Defects linked to changes |
| Change lead time | Days from request to production | < 10 for typical changes | Ticket and pipeline timestamps |
| Architecture rule violations | Count | 0 | Automated architecture tests |
4. Example Requirements
Each requirement below is ready to copy into a specification: specific, measurable, achievable, relevant and time-bound.
- Change impact: “Typical change requests shall affect no more than 3 modules, measured on all changes over a quarter.”
- Quality: “Fewer than 2% of production changes shall cause a regression found after release.”
- Architecture: “Automated architecture tests shall prevent forbidden dependencies between modules on every build.”
5. Questions to Ask Stakeholders
- Which parts of the system change most often?
- Which changes are expected in the next year?
- How much regression risk is acceptable?
- How are module boundaries defined and enforced?
- How good is the automated test safety net today?
- Who reviews changes to critical modules?
6. Common Pitfalls
- Shared databases between modules. They couple everything. Give each module ownership of its data.
- Changing without tests. Regressions go unnoticed. Add tests before modifying risky code.
- God classes. Huge components attract every change. Split them.
7. Related NFRs
- Maintainability — modifiability is part of maintainability.
- Testability — tests make modifications safe.
- Flexibility — the ability to absorb future change.
- Extensibility — adding features without changing existing code.
8. FAQ
Modifiability is about changing the code safely; flexibility is the broader ability to accommodate future change.
How much modules depend on each other. Lower coupling means changes stay local.
Track how many modules each change touches, how long changes take and how often they cause regressions.
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. | [1] |
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] |
| Pipeline (CI/CD) | Automated sequence of steps that builds, tests and deploys each code change. | [9] |
| Production environment | The live system that real users use, as opposed to test environments. | [10] |
| Regression | Bug where something that used to work stops working after a change. | [11] |
| Stakeholder | Person or group with an interest in the system: users, sponsors, operators, regulators. | [12] |
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] “Coupling (computer programming).” Wikipedia. https://en.wikipedia.org/wiki/Coupling_(computer_programming) (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] “CI/CD.” Wikipedia. https://en.wikipedia.org/wiki/CI/CD (accessed Nov. 19, 2026).
- [10] “Deployment environment.” Wikipedia. https://en.wikipedia.org/wiki/Deployment_environment (accessed Nov. 19, 2026).
- [11] “Software regression.” Wikipedia. https://en.wikipedia.org/wiki/Software_regression (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 @sasun1990; inline photo by @mimithecook, both on Unsplash.




