System Landscape — Reladraw template

内部系统全景. Copy the source, paste into the official playground, done. No coordinates — every position is stated relative to something else.

Preview

CRM ERP BI Portal ETL

Source (.reladraw)

node crm "CRM"
node erp "ERP"  right of crm
node bi "BI"  right of erp
node portal "Portal"  below crm
node etl "ETL"  below erp
edge crm -> etl
edge erp -> etl
edge etl -> bi
edge portal -> crm

How to use

  1. Open the Reladraw playground
  2. Paste the source above — the diagram re-solves live
  3. Export SVG from the playground, or render locally: npx reladraw system-landscape.reladraw -o out.svg

When to use this template

The internal-systems map: CRM, ERP and BI beside each other, a portal feeding the CRM, and an ETL layer moving data between them. Use it in onboarding docs and integration planning — every new engineer asks what talks to what in week one.

How to customize

  1. Add a data warehouse. Add node dwh "Warehouse" right of bi and edge bi -> dwh "sync".
  2. Show batch vs realtime. Label edges: edge etl -> bi "nightly batch" vs edge web -> crm "realtime".
  3. Mark a legacy system. Suffix: node erp "ERP (legacy, sunsetting 2027)" — landscape docs age well with dates.

FAQ

What is a system landscape diagram?

The one-page map of your organization’s software: each major system as a node, integrations as edges. It answers what exists and what connects to what — the first diagram every new engineer needs.

How much detail should a landscape diagram have?

Major systems and integration directions only. Column lists, table names, and API routes belong one level down — a landscape that tries to show everything stops being read.

How do I show data flow direction?

Every edge already has an arrow. For mixed flows, draw two edges with different labels (sync vs nightly) — the pair tells the real story.

Related templates

A/B Test FlowRAG PipelineML Model Lifecycle