Functional Requirements — What the system should do?
Mnemonic: CUJWDI - Can Users Journey, Work, Data, Integrate?
Capabilities → Users & Access → User Journeys → Workflows → Data → Integrations
- Capabilities: What capabilities should the new solution provide?
- Users & Access: Who will use the system, and what functionality should they be able to access?
- User Journeys: What are the most important user journeys?
- Workflows: What workflows need to be automated?
- Data: What types of data will the system process?
- Integrations: What systems or services need to be integrated?
Non-Functional Requirements — How well the system should do it?
Mnemonic: PSPO - Perfect Systems Protect Operations
Performance → Scale → Protection → Operations
1. Performance
- Users: How many users do you expect?
- Traffic: What is the expected transaction/request volume?
- Latency: What response time or latency is required?
- Availability: What level of availability is required?
2. Scale
- Scalability: How much should the system scale?
- Growth: How much future growth do you anticipate?
3. Protection
- Security: What security requirements apply?
- Compliance: What compliance and regulatory requirements apply?
- Backup & DR: What are the backup and disaster-recovery requirements?
- RTO/RPO: What are the RTO and RPO requirements?
4. Operations
- Observability: What monitoring, logging, and tracing requirements exist?
- SLA/SLO: What SLA/SLO expectations apply?
Quick Recall
Functional — CUJWDI - Can Users Journey, Work, Data, Integrate?
Capabilities → Users → Journeys → Workflows → Data → Integrations
Non-Functional — PSPO
Performance → Scale → Protection → Operations