In short
- Definition: The ease with which a system can be supported once in use, including diagnosing problems and helping users.
- Goal: Resolve user issues quickly and at a reasonable cost.
- Example S.M.A.R.T. requirement: 80% of tickets diagnosed using built-in logs without a developer, and median resolution time under 1 business day.
1. Definition
As a non-functional requirement, supportability describes how easily a system can be supported once in use: diagnosing problems, helping users and fixing issues efficiently [1], [2].
Every minute a support agent spends guessing is a minute a customer spends waiting.Key takeaway
Supportable systems give support teams what they need: clear error messages with reference codes, logs and traces they can search, admin tools to view a user’s situation safely, diagnostic exports, and documentation and runbooks.
Supportability is often grouped with other qualities in the FURPS model (Functionality, Usability, Reliability, Performance, Supportability), where it also covers maintainability and configurability [3].
2. Goal
The goal is to resolve user issues quickly and at a reasonable cost.
Hard-to-support systems escalate every ticket to developers, frustrate users and make support costs grow with each new customer.
3. How to Measure It (S.M.A.R.T.)
| Metric | Unit | Typical target | How to measure |
|---|---|---|---|
| Tickets diagnosed without a developer | % | ≥ 80% | Service desk categorization |
| Median resolution time | Business days | < 1 | Service desk statistics |
| Errors shown with a reference code | % of user-facing errors | 100% | UX review |
| Support tools coverage | % of common issues solvable with admin tools | ≥ 90% | Support team review |
4. Example Requirements
Each requirement below is ready to copy into a specification: specific, measurable, achievable, relevant and time-bound.
- Diagnosis: “At least 80% of support tickets shall be diagnosed by the support team using built-in logs and admin tools, without involving developers.”
- Error messages: “Every user-facing error shall show a short reference code that support can use to find the matching log entry.”
- Resolution: “The median resolution time for standard tickets shall stay under 1 business day.”
5. Questions to Ask Stakeholders
- Who supports the system, and at which levels?
- Which issues are most common today?
- What information does support need to diagnose a problem?
- How can support see a user’s situation without breaching privacy?
- Which tools and documentation will support receive before go-live?
- How will developer escalations be measured?
6. Common Pitfalls
- Generic error messages. “Something went wrong” gives support nothing to search for.
- Logs only developers can read. Make logs searchable and understandable for support.
- Training support after launch. Support must be ready on day one.
7. Related NFRs
- Operability — running the system in production.
- Documentation — guides and runbooks for support teams.
- Training — support staff need training too.
- Maintainability — fixes reach users faster when the system is easy to change.
8. FAQ
A model that groups quality requirements into Functionality, Usability, Reliability, Performance and Supportability.
They link what the user sees to the exact log entry, so support can find the cause quickly.
No. It also covers admin tools, documentation, training and how errors are presented.
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. |
|---|---|---|---|
| FURPS | Functionality, Usability, Reliability, Performance, Supportability | Model that groups software quality requirements into five categories. | [3] |
| 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. |
|---|---|---|---|
| FAQ | Frequently asked questions | List of common questions with their answers. | [5] |
| 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] |
| UX | User experience | Everything a person experiences when using a product: ease, emotions, and the whole journey. | [6] |
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. | [7] |
| Production environment | The live system that real users use, as opposed to test environments. | [8] |
| Runbook | Step-by-step procedure for routine operations or for handling a known problem. | [9] |
| Stakeholder | Person or group with an interest in the system: users, sponsors, operators, regulators. | [10] |
| Trace | Record of one request’s path through all the services that handled it. | [11] |
10. Sources and Further Reading
- [1] “Technical support.” Wikipedia. https://en.wikipedia.org/wiki/Technical_support (accessed Nov. 18, 2026).
- [2] “Non-functional requirement.” Wikipedia. https://en.wikipedia.org/wiki/Non-functional_requirement (accessed Nov. 18, 2026).
- [3] “FURPS.” Wikipedia. https://en.wikipedia.org/wiki/FURPS (accessed Nov. 18, 2026).
- [4] “SMART criteria.” Wikipedia. https://en.wikipedia.org/wiki/SMART_criteria (accessed Nov. 19, 2026).
- [5] “FAQ.” Wikipedia. https://en.wikipedia.org/wiki/FAQ (accessed Nov. 19, 2026).
- [6] “User experience.” Wikipedia. https://en.wikipedia.org/wiki/User_experience (accessed Nov. 19, 2026).
- [7] “Logging (computing).” Wikipedia. https://en.wikipedia.org/wiki/Logging_(computing) (accessed Nov. 19, 2026).
- [8] “Deployment environment.” Wikipedia. https://en.wikipedia.org/wiki/Deployment_environment (accessed Nov. 19, 2026).
- [9] “Runbook.” Wikipedia. https://en.wikipedia.org/wiki/Runbook (accessed Nov. 19, 2026).
- [10] “Project stakeholder.” Wikipedia. https://en.wikipedia.org/wiki/Project_stakeholder (accessed Nov. 19, 2026).
- [11] “Tracing (software).” Wikipedia. https://en.wikipedia.org/wiki/Tracing_(software) (accessed Nov. 19, 2026).
Written by Philippe Huard · LinkedIn · Last updated: November 18, 2026 · Header photo by @charanjeet_dhiman; inline photo by @machec, both on Unsplash.




