The Solution Design Reference
Purpose: Technical specification for implementers.
Who this page is for
| Audience | Why it matters to you |
|---|---|
| Developers | Build to this spec |
| Architects | Define the SDR |
The Solution Design Reference (SDR)
The SDR is the technical blueprint. Developers follow this exactly.
SDR structure
Variable: prop2
Purpose: Form type
Values: contact | complaint
Scope: Hit
Owner: Product
Implementation: Set in data layer before form submit
QA Test: Verify prop2 matches form type selectedSDR for all variables
Create one row per variable (prop, eVar, event):
- Variable name
- Purpose (one sentence)
- Valid values
- Scope (hit/visit/visitor)
- Owner
- Implementation details
- QA test cases
Using the SDR
For developers: "What should I send?" → Check SDR For QA: "What should I verify?" → Check SDR For analysts: "What does prop2 mean?" → Check SDR
---
Next: Naming conventions