Learn AI ↗

Deliverables

The curriculum covers what an architect should know. This covers what an architect actually hands over: 55 artifacts, each with a worked example, a note on when it is worth producing, who reads it, and the ways it usually goes wrong. Filter by the artifact's type, the kind of engagement that calls for it, the stack or industry it is drawn against, or the audience it is written for.

Identify the deliverable → 42 diagrams, shown one at a time with the answer withheld. Nothing to submit.

Type Any Structural View8 Behavioural View7 Data View7 Deployment & Infrastructure View7 Security View7 Governance Artifact8 Planning Artifact5 Analysis Artifact6
Use case Any Greenfield Build29 Legacy Migration19 Cloud Landing Zone13 Data Platform Build10 AI / ML Platform2 Integration Programme13 Security Uplift12 Cost Optimisation12 Merger & Acquisition Integration14 Regulatory Remediation11 Resilience Programme9 Vendor Selection10
Technology Any Cloud-Agnostic55 Azure2 AWS2 Kubernetes4 Kafka2 Databricks1 Hybrid3
Domain Any Cross-Industry55 Retail & E-Commerce3 Banking & Payments12 Healthcare & Pharma8 Insurance1
Audience Any CxO25 Architecture Review Board38 Engineering36 Operations & SRE22 Security12 Finance9 Regulator & Audit8

3 of 55 deliverables shown. 

flowchart TB
  cust(["Customer"])
  agent(["Support Agent"])
  sys["Order Management<br/>the system being described"]
  pay["Payment Gateway<br/>external SaaS"]
  erp["ERP<br/>existing on-premises"]
  mail["Email Provider<br/>external SaaS"]
  crm["CRM<br/>external SaaS"]

  cust -->|"places and tracks orders"| sys
  agent -->|"amends and refunds orders"| sys
  sys -->|"authorises and captures"| pay
  sys -->|"posts financial documents"| erp
  sys -->|"sends confirmations"| mail
  sys -->|"reads account and entitlement"| crm
Structural View

System Context Diagram

The single box of your system surrounded by the people and external systems it talks to, and nothing about how it is built inside.
Context Diagrams Discovery