# Non-Functional Requirements

Testable requirements that describe system qualities and operating constraints such as reliability, security, performance, usability, and maintainability.

- Type: term
- Domain: Engineering & architecture
- Level: Intermediate
- Last reviewed: 2026-09-22
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/non-functional-requirements/>)

## What it means

Non-functional requirements, often called quality requirements or architecture characteristics, describe how well a system must operate and the constraints under which it must do so. They cover concerns such as reliability, security, performance efficiency, accessibility, compatibility, maintainability, and portability. Useful NFRs connect a quality to a specific scenario and measurable outcome.

## Why it matters

A product can implement every requested feature and still fail because it is slow, unsafe, inaccessible, expensive to operate, or impossible to change. NFRs influence architecture early: they shape boundaries, redundancy, data handling, testing, infrastructure, and delivery practices. Explicit measures also let product, engineering, operations, security, and compliance discuss trade-offs using shared evidence.

## When to use it

Elicit NFRs for any consequential product, prioritizing qualities that affect user trust, legal duties, business viability, or engineering risk. Detail them before decisions that are expensive to reverse, then refine them as evidence improves. Small experiments still need essential safety and privacy constraints, but not an exhaustive enterprise checklist.

## How it works

1. Identify stakeholders and failure consequences, including users, operators, support, security, compliance, and maintainers.
2. Use a quality model as a prompt, then select characteristics relevant to this product rather than copying every category.
3. Write scenarios with a trigger, operating conditions, affected component, expected response, and measurable threshold.
4. Prioritize competing qualities and record acceptable trade-offs, assumptions, and the cost of missing each target.
5. Link requirements to architecture decisions, acceptance tests, load tests, security controls, and production indicators.
6. Review thresholds against real usage and revise them when user needs, risks, architecture, or economics change.

## A practical example

Instead of saying “the checkout must be fast and reliable,” a team specifies that during forecast peak load, 95% of payment-submission responses complete within two seconds, monthly successful-request availability is at least 99.95%, and ambiguous payment outcomes are reconciled without charging a customer twice. Tests and production indicators trace to each target.

## Where it breaks

The term “non-functional” can wrongly imply secondary importance, and quality categories overlap. Precise-looking targets may be arbitrary without user or operational evidence. Requirements can conflict—stronger consistency may reduce availability, for example—and not every quality is captured by one number. Measures need context, ownership, and periodic review rather than contractual theater.

## Common mistakes

- Writing vague adjectives such as scalable, secure, intuitive, or highly available without scenarios and measures.
- Copying a generic checklist while missing qualities that drive this product's actual risks.
- Setting thresholds without workload, user, regulatory, economic, or failure-consequence context.
- Documenting NFRs once but failing to connect them to decisions, tests, telemetry, and review triggers.

## Visualization

[View the visualization on the website](<https://wiki.soroush.uk/topic/non-functional-requirements/#visualization-non-functional-requirements>)

## Sources

1. [Reasoning About Software Quality Attributes](<https://insights.sei.cmu.edu/library/reasoning-about-software-quality-attributes/>) — Carnegie Mellon Software Engineering Institute · Institutional research report
2. [Azure Well-Architected Framework Workloads](<https://learn.microsoft.com/en-us/azure/well-architected/workloads>) — Microsoft Learn · Institutional architecture guidance
3. [Develop an Architecture Design Specification](<https://learn.microsoft.com/en-us/azure/well-architected/architect-role/architecture-design-specification>) — Microsoft Learn · Institutional requirements guidance

## Related topics

- [Architecture Decision Record](<https://wiki.soroush.uk/topic/architecture-decision-record/>)
- [Evolutionary Architecture](<https://wiki.soroush.uk/topic/evolutionary-architecture/>)
- [Build vs. Buy](<https://wiki.soroush.uk/topic/build-vs-buy/>)
