Problem understanding clarifies the job, business context, and constraints before significant architectural choices. Moving to a solution too quickly risks solving the wrong problem or overlooking a constraint that invalidates it. section 2.0
A solution-ready understanding makes the important distinctions explicit:
- State the job without naming a solution, keeping the solution space open. section 2.4
- Separate architecturally significant requirements from details that do not shape the architecture. section 2.0 section 2.4
- Identify non-functional service tiers, compliance constraints, and applicable architectural standards. section 2.0 section 2.4
- Mark what is defined and what remains open, then decide whether the uncertainty is acceptable. Readiness does not require completeness; some questions are better answered during design or with a prototype. section 2.4
Backoffice customer search
Staff need to locate the right customer record quickly across several criteria. The framing identifies broad search across multiple entities as architecture-shaping, while treating filter ordering as a detail; it also records service tiers and constraints. section 2.4
Table 2.6 Identified requirements
|
Type
|
Requirement
|
Notes
|
|
Functional
|
Full-text search across multiple entities (customers,
orders, interactions).
|
Requires capable search engine; architecture-shaping.
|
|
Functional
|
Filter by date, name, type and other attributes.
|
All filter details are usually not an ASR. We acknowledge
the need but do not spend much time debating or analysing a specific sort
order.
|
|
Availability
|
Standard tier – 99.9% uptime for core search.
|
Multi-node failover should be planned.
|
|
Durability
|
Moderate is acceptable for search index.
|
Indexes can be rebuilt from source, no need to worry about
data loss.
|
|
Latency
|
Acceptable tier – search response under 1s.
|
Indexing and solid query design is required however
without excessive optimisations.
|
|
Throughput
|
Under 200 concurrent users; under 50 requests per second.
|
Not a number to worry about however relevant for choosing
compute provisioning; deprioritises a
need for autoscaling complexity.
|
|
Volatility
|
Ranking and filter logic: Campaign tier. Indexing and
overall search functionality design: Foundational.
|
Initially, filters might be of high volatility while the
problem is still in the early stage. Decoupling it or making it config-driven
could be an idea.
|
|
Security
|
Service-to-service communication must be authenticated and
encrypted
|
Likely control to go with: mutual TLS, organisation
default
|
|
Legal
|
GDPR right to erasure and retention rules
|
Must be designed in, especially the deletion flow.
|
|
Architecture
|
Deployment to existing regions on the adopted cloud
provider.
|
Organisational standard to follow, functionality likely
will be just a part of existing larger infrastructure
|
Browse the requirements table for the example’s functional needs, service tiers, and implementation implications. section 2.4
