# Data Architecture Delivery Pack

Skill: `designing-data-architecture`

[Word report](report.en.docx) · [Excel register](register.en.xlsx)

## Record details

| ID | Field | Project value |
| --- | --- | --- |
| `artifact_id` | Artifact ID | |
| `project` | Project | |
| `skill` | Skill | |
| `version` | Version | |
| `date` | Date | |
| `status` | Status | |
| `author` | Author | |
| `owner` | Owner | |
| `approver` | Approver | |
| `purpose` | Purpose | |
| `business_outcome` | Business outcome | |
| `scope` | Scope and exclusions | |
| `source_inputs` | Inputs and sources | |
| `assumptions` | Assumptions and constraints | |
| `decisions` | Decisions | |
| `rationale` | Rationale | |
| `risks` | Risks | |
| `exceptions` | Exceptions | |
| `open_items` | Open items | |
| `due_date` | Due date | |
| `acceptance_criteria` | Acceptance criteria | |
| `evidence_location` | Evidence location | |
| `reviewer_decision` | Reviewer decision | |
| `next_gate` | Next stage gate | |

## Domain analysis and decisions

### Business outcome and scope (`business_outcome`)

State the business capabilities, decisions, and boundaries the architecture must support.

> Enter project evidence, conclusion, and owner.


### Current-state evidence (`current_state`)

Describe systems, flows, ownership, and known problems with evidence dates.

> Enter project evidence, conclusion, and owner.


### Principles and requirements (`principles`)

Distinguish mandatory constraints from negotiable design preferences.

> Enter project evidence, conclusion, and owner.


### Target architecture (`target_state`)

Describe target capabilities, data boundaries, interfaces, governance, and operations ownership.

> Enter project evidence, conclusion, and owner.


### Transition architecture (`transition`)

Define deliverable interim states, migration order, and compatibility measures.

> Enter project evidence, conclusion, and owner.


### Key decisions and trade-offs (`tradeoffs`)

Record alternatives, trade-offs, approval roles, and triggers for revisiting decisions.

> Enter project evidence, conclusion, and owner.


### Conformance and acceptance (`conformance`)

List standards, exceptions, tests, and view-review evidence.

> Enter project evidence, conclusion, and owner.


### Dependency roadmap (`roadmap`)

Map capability and data dependencies to gates and verifiable exits.

> Enter project evidence, conclusion, and owner.


## Working registers

### Capabilities (`capabilities`)

Compare current and target capabilities with dependencies.

| Capability (`capability`) | Current state (`current`) | Target state (`target`) | Dependency (`dependency`) | Owner (`owner`) | Evidence (`evidence`) |
| --- | --- | --- | --- | --- | --- |
|   |   |   |   |   |   |

### Architecture Decisions (`decisions`)

Record architectural choices, trade-offs, and approval evidence.

| Decision (`decision`) | Rationale (`rationale`) | Impact (`impact`) | Owner (`owner`) | Approver (`approver`) | Evidence (`evidence`) | Review date (`review_date`) |
| --- | --- | --- | --- | --- | --- | --- |
|   |   |   |   |   |   |   |