Non-functional requirements template

Measurable quality attributes — availability, performance, security, recovery and more — with how each is verified.

Use this templateFree, opens in your browser. No sign-up.

Non-functional requirements template
Trade-offs to discuss
Quality attribute
Requirement (measurable)
How we verify
Priority
Availability
99.9% per month (≤ 43 min downtime)
Uptime monitor, SLO dashboard
Must
Performance
p95 < 300 ms at 500 requests/s
Load test (k6) before each release
Must
Scalability
Handle 10× peak by scaling out
Scale test, autoscaling review
Should
Security
OWASP Top 10, TLS 1.2+, encryption at rest
Yearly pen test, SAST in CI
Must
Recoverability
RPO 15 min, RTO 1 hour
Restore drill every quarter
Must
Observability
Traces + logs for every request
Game days, alert review
Should
Maintainability
Build < 10 min; new engineer ships in week 1
CI metrics, onboarding feedback
Could
Compliance
GDPR: export + delete data within 30 days
Audit, DPIA
Must
Availability vs cost (multi-AZ or multi-region?)
Consistency vs latency for reads
Security controls vs developer speed
Non-functional requirements
The non-functional requirements template as it opens in Kelvo: 3 sticky notes and 1 table.

What's on the board

Trade-offs to discuss
Availability vs cost (multi-AZ or multi-region?) · Consistency vs latency for reads · Security controls vs developer speed

Table columns: Quality attribute, Requirement (measurable), How we verify, Priority.

How to use this template

  1. Click Use this template. It opens in the Kelvo app as a new board, saved in your browser.
  2. Double-click any box to change its text. Replace the examples with your own content.
  3. Sketch, then convert. Draw boxes and arrows with the pen, select the strokes and click Convert sketch: they become real boxes and links.
  4. Ask Kelvo right on the board (Pro). With Pro, type @kelvo and what you want in any box or text, for example “@kelvo add error handling”, and press Enter. The change is made there and the request disappears; ⌘Z undoes it.
  5. One page per level. Put the C4 context view on one page and the container view on the next, so each diagram stays readable.

Good for

  • architect
  • nfr
  • quality attributes
  • requirements
  • Agreeing on boundaries and responsibilities between services
  • Recording why a design was chosen (and what was rejected)
  • Comparing integration options side by side

Related templates

  • C4 system context diagram template previewC4 system context diagram

    C4 level 1: the system in scope, the people who use it and the external systems it depends on, with a legend.

  • C4 container diagram template previewC4 container diagram

    C4 level 2: the apps, APIs, databases and queues inside the system boundary, with the technology on each link.

  • Microservices with API gateway template previewMicroservices with API gateway

    Clients behind an API gateway, services that each own their database, and an event bus for asynchronous work.

  • Event-driven architecture template previewEvent-driven architecture

    Producers publish facts to a broker; independent consumers react — with the design rules that keep it reliable.

  • LLM application architecture template previewLLM application architecture

    Production building blocks around a model: gateway, guardrails, orchestrator, cache, vector DB, tools and observability.

  • UML use case diagram template previewUML use case diagram

    Actors, the system boundary and the use cases they take part in, with «include» and «extend» relationships.

All solution architecture diagram templates · All templates

Use the non-functional requirements template