NFR Block
Document non-functional requirements with measurable targets, priorities, and verification methods. Track performance, security, availability, and other quality requirements.
Non-functional requirements (NFRs) define quality attributes of the system: how fast, how secure, how reliable. Unlike functional requirements that describe what the system does, NFRs describe how well it does it. Documenting NFRs with measurable targets enables verification and drives architecture decisions.
When to Use
Block Properties
| Property | Required | Description |
|---|---|---|
| Title | Yes | Short name for the NFR |
| Description | Yes | Detailed explanation of the requirement |
| Category | Yes | Type of quality attribute being specified |
| Statement | Yes | The formal requirement expressed as a measurable target |
| Priority | No | MoSCoW priority: must, should, could, or wont |
| Scope | No | What this NFR applies to (services, endpoints, etc.) |
| Rationale | No | Why this NFR exists and why the target was chosen |
| Target | No | The measurable target value or threshold |
| Tolerance | No | Acceptable variance from the target |
| Measurement Method | No | How compliance will be verified |
| Status | No | Current state: proposed, agreed, implemented, verified, or retired |
| Review Date | No | When to re-evaluate the requirement |
| Notes | No | Additional context or observations |
Category Values
Priority Values (MoSCoW)
Example: Performance NFR
A performance requirement with specific latency targets.
Example: Availability NFR
An availability requirement with uptime and recovery targets.
Example: Security NFR
A security requirement for data protection.
Example: Scalability NFR
A scalability requirement for handling growth.
Example: Operability NFR
An operability requirement for deployment and monitoring.