In short
- Definition: The ability of a system to keep consistent behavior and performance over time, without crashes or unexpected changes.
- Goal: Give users and operators a predictable system.
- Example S.M.A.R.T. requirement: Crash-free sessions above 99.8%, and no performance degradation over a 7-day soak test.
1. Definition
As a non-functional requirement, stability describes the ability of a system to keep consistent behavior and performance over time, without crashes, hangs or unexpected changes [1], [2].
A system that works on Monday and crawls on Friday is not stable, even if it never crashes.Key takeaway
Stability problems often appear only after hours or days: memory leaks, growing queues, slow degradation, or rare crashes. They are found with soak tests, long-running tests at normal load, and with crash reporting in production [3].
For mobile and desktop apps, a common stability metric is the share of crash-free sessions or users.
2. Goal
The goal is a predictable system for users and operators.
Unstable systems need frequent restarts, lose user work and erode confidence even when each incident is short.
3. How to Measure It (S.M.A.R.T.)
| Metric | Unit | Typical target | How to measure |
|---|---|---|---|
| Crash-free sessions | % | > 99.8% | Crash reporting tool |
| Performance degradation over a soak test | % change in response time | < 5% over 7 days | Soak test |
| Unplanned restarts | Per month | 0 | Operations logs |
| Hangs or freezes | Count per 10,000 sessions | < 1 | Application monitoring |
4. Example Requirements
Each requirement below is ready to copy into a specification: specific, measurable, achievable, relevant and time-bound.
- Mobile app: “Crash-free sessions shall stay above 99.8% for each release, measured over 30 days.”
- Server: “Response times shall not degrade by more than 5% over a 7-day soak test at normal load.”
- Operations: “No service shall need a scheduled restart to stay healthy.”
5. Questions to Ask Stakeholders
- How long does the system run without restart?
- What instability have users experienced before?
- Which components are most likely to degrade over time?
- How will crashes be reported and analyzed?
- Is a soak test part of the release process?
- What is an acceptable crash rate?
6. Common Pitfalls
- Only short tests. Leaks and slow degradation need long runs.
- Scheduled restarts as a fix. They hide problems instead of solving them.
- No crash reporting. Without data, rare crashes are never fixed.
7. Related NFRs
- Categories of Non-Functional Requirements — the full checklist of NFR categories.
- Reliability — stability supports reliable operation over time.
- Memory Optimization — leaks are a common cause of instability.
- Robustness — handles unexpected inputs without crashing.
- Performance — stable performance over time.
8. FAQ
The percentage of user sessions that end without the app crashing.
A long test at normal load, often several days, to reveal leaks and slow degradation.
They are close. Reliability focuses on failures over time; stability also covers consistent behavior and performance.
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. |
|---|---|---|---|
| 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] |
Terms
Plain-language definitions of technical and project-management terms used in this article.
| Term | Plain-language definition | Ref. |
|---|---|---|
| Incident | Unplanned interruption or degradation of a service. | [6] |
| Log | Time-stamped record of events written by software, used for troubleshooting and audit. | [7] |
| Memory leak | Bug where a program keeps memory it no longer needs, so its usage grows over time. | [8] |
| Production environment | The live system that real users use, as opposed to test environments. | [9] |
| Stakeholder | Person or group with an interest in the system: users, sponsors, operators, regulators. | [10] |
10. Sources and Further Reading
- [1] “Soak testing.” Wikipedia. https://en.wikipedia.org/wiki/Soak_testing (accessed Nov. 18, 2026).
- [2] “Non-functional requirement.” Wikipedia. https://en.wikipedia.org/wiki/Non-functional_requirement (accessed Nov. 18, 2026).
- [3] “Crash (computing).” Wikipedia. https://en.wikipedia.org/wiki/Crash_(computing) (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] “Incident management.” Wikipedia. https://en.wikipedia.org/wiki/Incident_management (accessed Nov. 19, 2026).
- [7] “Logging (computing).” Wikipedia. https://en.wikipedia.org/wiki/Logging_(computing) (accessed Nov. 19, 2026).
- [8] “Memory leak.” Wikipedia. https://en.wikipedia.org/wiki/Memory_leak (accessed Nov. 19, 2026).
- [9] “Deployment environment.” Wikipedia. https://en.wikipedia.org/wiki/Deployment_environment (accessed Nov. 19, 2026).
- [10] “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 @jeremythomasphoto; inline photo by @doctorgyprons, both on Unsplash.








