← Files Product & App ArchitectARCHIVED FILE

references/nonfunctional-quality.md

981 Bytes · Nov 20, 2026 · 06:43 UTC

↓ Download file

See the change to this file →

# Security, Privacy, Performance and Reliability Requirements

Treat nonfunctional requirements as measurable design constraints, not a blanket checklist.

## Security and privacy
Classify data and trust boundaries, authn/authz, tenant/resource isolation, secrets, logging redaction, retention, deletion and abuse scenarios. Use OWASP ASVS 5.0 when implementation-level control requirements apply. No security guarantees from a diagram alone.

## Reliability and operations
Define needed SLOs, expected dependency failures, retry/backoff/idempotency, backups and restore drills, migration strategy, observability, support and rollback. Don't mandate enterprise SRE features for a one-user prototype.

## Performance and cost
State workload assumptions and budgets. Identify expensive flows, caching/freshness tradeoffs, scaling triggers and measurable performance criteria. Never invent dollar quotes or performance test results. Distinguish assumptions from validated benchmarks.

SHA-256: 3918b051d4655da9f2a681ca1fad7e571ae633cb676f31035755861f007321a9