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.

3 of 55 deliverables shown.

flowchart TB
  subgraph sell["Sell"]
    direction LR
    s1["CRM<br/><i>SaaS · Sales</i>"]
    s2["Quoting<br/><i>bespoke · Sales</i>"]
    s3["Pricing A<br/><i>legacy · Sales</i>"]
    s4["Pricing B<br/><i>legacy · Regional</i>"]
  end
  subgraph fulfil["Fulfil"]
    direction LR
    f1["Order Mgmt<br/><i>bespoke · Ops</i>"]
    f2["WMS<br/><i>COTS · Ops</i>"]
    f3["Carrier Portal<br/><i>SaaS · Ops</i>"]
  end
  subgraph support["Support"]
    direction LR
    b1["ERP<br/><i>COTS · Finance</i>"]
    b2["Billing<br/><i>mainframe · Finance</i>"]
    b3["HRIS<br/><i>SaaS · HR</i>"]
    b4["Expenses<br/><i>SaaS · unowned</i>"]
  end
  s3 -.->|"same capability"| s4

Structural View

Application Landscape Diagram

Every application in the estate placed against the business areas it serves, so duplication and orphans become visible.

Application Portfolio Management Discovery

flowchart TB
  subgraph core["Customer-Facing"]
    direction LR
    c1["Customer<br/>Management"]
    c2["Product &<br/>Catalogue"]
    c3["Order<br/>Capture"]
    c4["Fulfilment"]
  end
  subgraph enable["Enabling"]
    direction LR
    e1["Pricing &<br/>Promotion"]
    e2["Inventory<br/>Management"]
    e3["Payments &<br/>Settlement"]
    e4["Returns &<br/>Claims"]
  end
  subgraph support["Supporting"]
    direction LR
    s1["Finance &<br/>Accounting"]
    s2["Human<br/>Resources"]
    s3["Procurement"]
    s4["Risk &<br/>Compliance"]
  end

Structural View

Business Capability Map

What the business is able to do, arranged as a stable nested hierarchy of abilities with no processes, systems or org units on it.

Capability Mapping Discovery

quadrantChart
  title Business value against technical health
  x-axis "Poor technical health" --> "Good technical health"
  y-axis "Low business value" --> "High business value"
  quadrant-1 Invest
  quadrant-2 Migrate or re-engineer
  quadrant-3 Eliminate
  quadrant-4 Tolerate
  "Order management": [0.28, 0.92]
  "Payment gateway": [0.81, 0.95]
  "Customer portal": [0.74, 0.78]
  "Pricing engine": [0.22, 0.84]
  "Mainframe billing": [0.14, 0.88]
  "Legacy CRM": [0.19, 0.34]
  "Reporting portal": [0.31, 0.26]
  "Expenses tool": [0.68, 0.22]
  "Intranet wiki": [0.72, 0.18]
  "Partner gateway": [0.44, 0.66]

Analysis Artifact

Application Portfolio Heat Map

Every application placed on business value against technical health, so that invest, tolerate, migrate and eliminate become positions rather than opinions.

Application Portfolio Management Discovery