In short
- Definition: The ease with which new features can be added and existing customizations carried forward when the system is upgraded.
- Goal: Allow the system to grow with new needs without costly rewrites or lost customizations.
- Example S.M.A.R.T. requirement: A new plug-in added without modifying core code, and 100% of customizations working after a major upgrade.
1. Definition
As a non-functional requirement, extensibility describes how easily new features can be added to a system, and how well existing customizations survive when the system is upgraded [1], [2].
If every new feature requires editing the core, the core will eventually break under its own weight.Key takeaway
Extensible systems offer extension points: plug-in interfaces, APIs, events, scripting or configuration, so that new behavior can be added without modifying the core code [3].
Extensibility is especially important for platforms and products used by many customers, where each one wants something slightly different but all must keep receiving upgrades.
2. Goal
The goal is to let the system grow with new needs without costly rewrites, and without losing customizations at each upgrade.
Systems that are hard to extend accumulate forks and patches, and customers end up stuck on old versions.
3. How to Measure It (S.M.A.R.T.)
| Metric | Unit | Typical target | How to measure |
|---|---|---|---|
| Features added via extension points | % of new features | ≥ 70% | Change review |
| Customizations working after upgrade | % | 100% | Upgrade regression tests |
| Effort to add a typical feature | Person-days | As set per feature type | Time tracking |
| Stable extension API | Breaking changes per year | 0 without deprecation notice | API change log |
4. Example Requirements
Each requirement below is ready to copy into a specification: specific, measurable, achievable, relevant and time-bound.
- Plug-in architecture: “A new payment method shall be addable as a plug-in without modifying the core code, and installed without downtime.”
- Upgrades: “100% of documented customizations shall keep working after a major upgrade, verified by the automated customization test suite.”
- API stability: “Breaking changes to the extension API shall be announced at least 6 months in advance.”
5. Questions to Ask Stakeholders
- What kinds of features do we expect to add in the next years?
- Who will build extensions: our team, partners, customers?
- Which parts of the system must remain stable for extensions?
- How will upgrades treat existing customizations?
- How will extensions be secured and isolated?
- How will the extension API be documented and versioned?
6. Common Pitfalls
- Extension points everywhere. Too many hooks make the system complex. Add them where change is likely.
- Unversioned extension APIs. Uncontrolled changes break every extension. Version and deprecate properly.
- No isolation. A faulty plug-in should not crash the whole system.
7. Related NFRs
- Categories of Non-Functional Requirements — the full checklist of NFR categories.
- Modifiability — modifying existing code versus adding new behavior around it.
- Flexibility — extensibility is one way to stay flexible.
- Integrability — extensions often integrate external systems.
- Compatibility — extensions must stay compatible across versions.
8. FAQ
Extensibility adds new behavior through planned extension points; modifiability is about changing existing code safely.
A defined place in the system, such as a plug-in interface or event, where new behavior can be attached.
Build a sample extension, upgrade the system, and check that it still works without changes.
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] |
| FAQ | Frequently asked questions | List of common questions with their answers. | [6] |
| 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. |
|---|---|---|
| Deprecation | Marking a feature as obsolete and scheduled for removal. | [7] |
| Log | Time-stamped record of events written by software, used for troubleshooting and audit. | [8] |
| Patch | Update that fixes bugs or security holes. | [9] |
| Regression | Bug where something that used to work stops working after a change. | [10] |
| Stakeholder | Person or group with an interest in the system: users, sponsors, operators, regulators. | [11] |
10. Sources and Further Reading
- [1] “Extensibility.” Wikipedia. https://en.wikipedia.org/wiki/Extensibility (accessed Nov. 18, 2026).
- [2] “Non-functional requirement.” Wikipedia. https://en.wikipedia.org/wiki/Non-functional_requirement (accessed Nov. 18, 2026).
- [3] “Plug-in (computing).” Wikipedia. https://en.wikipedia.org/wiki/Plug-in_(computing) (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] “FAQ.” Wikipedia. https://en.wikipedia.org/wiki/FAQ (accessed Nov. 19, 2026).
- [7] “Deprecation.” Wikipedia. https://en.wikipedia.org/wiki/Deprecation (accessed Nov. 19, 2026).
- [8] “Logging (computing).” Wikipedia. https://en.wikipedia.org/wiki/Logging_(computing) (accessed Nov. 19, 2026).
- [9] “Patch (computing).” Wikipedia. https://en.wikipedia.org/wiki/Patch_(computing) (accessed Nov. 19, 2026).
- [10] “Software regression.” Wikipedia. https://en.wikipedia.org/wiki/Software_regression (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 @xavi_cabrera; inline photo by @sen7, both on Unsplash.








