id: system-landscape-map
name:
  ja: "システムランドスケープ（刷新影響）"
  en: "System Landscape (Modernization Impact)"
purpose:
  ja: "業務ドメインとアーキテクチャ層へシステムを配置し、規模・健全性・重要度・連携から刷新優先度を導出する"
  en: "Systems placed by business domain and architecture layer, with the order to modernize following from size, health, criticality and how they interconnect"
# A5 の裁定で draft として移設し、2026-09-04 に型ごとの承認を取って公開した。
status: published
# 索引カードの図版。pnpm layout:render が原本から描く。
still: ./still.png
category: architecture
catalogOrder: 160
jobs:
  - explain-structure
  - prioritize-diagnose
useCases:
  - org
layoutKinds:
  - network
tags: [system-landscape, enterprise-architecture, interface, modernization]
whenToUse:
  - ja: "現行システム構成と刷新順を一画面で議論したい場合"
    en: "Discussing the current estate and the order to replace it, on one screen"
  - ja: "変更影響の大きい連携集中点を説明したい場合"
    en: "Explaining where interfaces concentrate and change hurts most"
avoidWhen:
  - ja: "流量の大きさを多対多の帯幅で示したい場合"
    en: "Showing volume as the width of many-to-many bands"
  - ja: "業務能力の成熟度と投資配分を示したい場合"
    en: "Showing capability maturity and how investment is split"
requiredInputs:
  - ja: "業務ドメインと層"
    en: "The business domains and layers"
  - ja: "システムの規模・健全性・重要度"
    en: "Each system's size, health and criticality"
  - ja: "システム間interface"
    en: "The interfaces between them"
relatedLayouts: [business-capability-map, sankey-flow, heatmap]
dataSchema:
  systems: "{ id, name, domainId, layerId, userCount, health, criticality, note? }[] — 4〜12件"
  interfaces: "{ sourceId, targetId, criticality, label? }[] — 1〜20件"
sources: []