Deliverable

Intro

A deliverable is a packaged set of architectural artifacts produced as a single work product. It matters because formal deliverables enable review, sign‑off, and reuse.

Key points:

• Often contractually defined and stakeholder approved.
• May be archived or added to an architecture repository.
• Common use cases: target architecture, standards, roadmaps, decision records.
• Pitfall: unclear acceptance criteria leading to rework.

Examples:

• Current and target state diagrams with rationale.
• Technology standards catalog and principles.
• Release roadmap with dependencies and risks.

In practice:

Define templates, ownership, and sign‑off workflows; store approved versions for traceability.

Related terms: artifact; architecture-repository; architecture-landscape

FAQs:

Q: Who approves deliverables?
A: Relevant stakeholders such as sponsors, domain owners, and governance boards.

Q: How are deliverables maintained?
A: Through version control and periodic review cycles.

‍