43 lines
1.1 KiB
YAML
43 lines
1.1 KiB
YAML
|
spec_type: non_functional_requirements
|
||
|
|
name: Platform NFRs
|
||
|
|
version: "1.0"
|
||
|
|
|
||
|
|
requirements:
|
||
|
|
- id: NFR-001
|
||
|
|
category: performance
|
||
|
|
title: Response Time
|
||
|
|
description: API response time must be under 200ms for 95th percentile
|
||
|
|
metric: p95_latency
|
||
|
|
target: "< 200ms"
|
||
|
|
|
||
|
|
- id: NFR-002
|
||
|
|
category: scalability
|
||
|
|
title: Concurrent Users
|
||
|
|
description: System must support 10,000 concurrent users
|
||
|
|
metric: concurrent_connections
|
||
|
|
target: ">= 10000"
|
||
|
|
|
||
|
|
- id: NFR-003
|
||
|
|
category: availability
|
||
|
|
title: Uptime SLA
|
||
|
|
description: System availability must be 99.9%
|
||
|
|
metric: uptime_percentage
|
||
|
|
target: ">= 99.9%"
|
||
|
|
|
||
|
|
- id: NFR-004
|
||
|
|
category: security
|
||
|
|
title: Data Encryption
|
||
|
|
description: All data at rest and in transit must be encrypted
|
||
|
|
requirements:
|
||
|
|
- TLS 1.3 for transit
|
||
|
|
- AES-256 for storage
|
||
|
|
|
||
|
|
- id: NFR-005
|
||
|
|
category: reliability
|
||
|
|
title: Data Durability
|
||
|
|
description: No data loss in case of single node failure
|
||
|
|
requirements:
|
||
|
|
- Multi-region replication
|
||
|
|
- Daily backups
|
||
|
|
- Point-in-time recovery
|