Requirements & Non-Functional Requirements
Functional requirements
Define:
- source onboarding
- domain modeling
- semantic reuse
- analytical consumption
- data products
- cross-domain sharing
- self-service discovery
- historical reporting
- near-real-time use cases
Non-functional requirements
Create measurable targets for:
| Area | Example architecture question |
|---|---|
| Availability | What business services must remain available? |
| Freshness | How quickly must source changes become consumable? |
| Performance | What response time is acceptable for critical workloads? |
| Security | Which data requires row-level restrictions? |
| Recovery | What are the RPO and RTO targets? |
| Scalability | What growth and concurrency must be supported? |
| Governance | What must be classified, cataloged, and traceable? |
| Cost | Which workloads drive capacity consumption? |
Do not invent numbers merely to complete a template. Every target should have a business justification.
Priority model
Classify requirements as:
Must → Should → Could → Won't
Then map each architecture decision to the requirements it satisfies.