20.14 Architect Playbook & Checklist
Before creating a solution
- business capability defined
- source systems identified
- data ownership assigned
- security classification known
- freshness and availability targets agreed
- expected volume and growth estimated
Before development
- tenant and space boundaries agreed
- naming standards applied
- integration pattern selected
- semantic contract defined
- observability requirements defined
Before transport
- dependencies reviewed
- package scoped
- security validated
- test evidence available
- target environment ready
- release approval recorded
Before production
- smoke tests passed
- reconciliation passed
- schedules verified
- monitoring active
- owner and support path known
- recovery procedure documented
Architecture defense questions
- Why this tenant topology?
- Why these space boundaries?
- Why federation versus persistence?
- Why this transport mechanism?
- What is the rollback strategy?
- What happens when the source is unavailable?
- How is data correctness proven?
- How is capacity controlled?
- Who owns the product after go-live?
- What would make you redesign it?
Final principle
Enterprise Datasphere is not finished when the model is deployed. It is finished when the capability can be changed, operated, measured and recovered safely.