Documenting Non-Functional Requirements
Learn how to document NFRs with measurable targets using NeoArc's structured NFR blocks. Create requirements that are testable, traceable, and auditable.
Non-functional requirements (NFRs) define the quality attributes of your system. Performance, availability, security, scalability. Unlike functional requirements that describe what the system does, NFRs describe how well it does it.
Adding an NFR Block
NFR Block Fields
Category
Group NFRs by type to help organise requirements:
This example uses the NeoArc NFR content block.
Priority
Using MoSCoW prioritisation:
This example uses the NeoArc NFR content block.
This example uses the NeoArc NFR content block.
Writing Good NFRs
This example uses the NeoArc NFR content block.
This example uses the NeoArc NFR content block.
NFR Status Tracking
Track the lifecycle of each NFR:
Connecting NFRs to Architecture
Place NFR blocks near the architecture they constrain. A service design page should include the NFRs that service must meet. This helps readers understand not just what the architecture is, but what quality attributes it must achieve.
The NFR blocks you see on this page were created using NeoArc's structured NFR block type. This same approach is used throughout this documentation site to document quality requirements alongside architecture.