Enterprise Architecture Diagram Generator (ArchiMate)

Quick Start: Add !include <archimate/Archimate> → Declare typed elements → Connect with Rel_* macros → Group into layers with rectangle → Wrap in ```plantuml fence.

⚠️ IMPORTANT: Always use ```plantuml or ```puml code fence. NEVER use ```text — it will NOT render as a diagram.

When To Use / Diagnostic Intake

适用于表达业务、应用、技术及迁移视图。先确定受众、观点、当前/目标状态、必须出现的实体和关系；仅有清单时不推断生产依赖。

Workflow

选择一个视图→核实元素类型与关系→建立唯一别名→生成 PlantUML→渲染并核对图例及边界。

Tools and Dependencies

需要兼容 stdlib ArchiMate 宏的 PlantUML 渲染器；调用前确认环境可用。无渲染器时提供源文件并说明验证范围。

Critical Rules

• Every diagram starts with @startuml and ends with @enduml
• Must include !include <archimate/Archimate> before using any macros
• Element syntax: Layer_Type(alias, "Label")
• Relationship syntax: Rel_Type(fromAlias, toAlias, "label")
• Use rectangle "Layer" { ... } to group elements into ArchiMate layers
• Directional suffixes _Up, _Down, _Left, _Right control relationship direction

Element Macros

Business Layer

Application Layer

Technology Layer

Motivation Layer

Strategy Layer

Implementation Layer

Relationship Macros

All relationships support directional suffixes: _Up, _Down, _Left, _Right.

Quick Example

@startuml
!include <archimate/Archimate>

rectangle "Business" {
  Business_Actor(customer, "Customer")
  Business_Process(order, "Order Process")
  Business_Service(orderSvc, "Order Service")
}

rectangle "Application" {
  Application_Component(orderApp, "Order System")
  Application_Service(orderAPI, "Order API")
}

rectangle "Technology" {
  Technology_Node(server, "App Server")
  Technology_Device(db, "Database Server")
}

Rel_Triggering(customer, order, "places order")
Rel_Realization(order, orderSvc, "realizes")
Rel_Serving(orderAPI, orderSvc, "serves")
Rel_Realization(orderApp, orderAPI, "realizes")
Rel_Assignment(server, orderApp, "runs on")
Rel_Serving(db, server, "stores data")
@enduml

Diagram Types

Capability Upgrade

Mode Selection

• Quick: 根据用户描述生成单视角 ArchiMate 图。
• Standard: 选择业务、应用、技术、动机或迁移视角，并输出可渲染 PlantUML。
• Deep: 结合项目架构、业务能力、系统清单、数据流和迁移计划，形成多视角架构图包。

Viewpoint Decision Logic

先判断用户要解释什么：业务能力、应用集成、技术部署、动机目标、安全控制还是迁移路线。不同问题不能混在一张图里；复杂架构应拆成多个 viewpoint。

Quality Gates

• 元素层级符合 ArchiMate 语义，不混用业务/应用/技术层。
• 关系类型准确，避免全部使用普通箭头。
• 图中节点数量适中，必要时拆图。
• 命名能被业务和技术读者理解。
• 输出包含可复制 PlantUML 和简短解读。

Deliverable Catalog

Delivery Verification Materials

• 场景与预期交付：合成案例及缺失输入、注入指令变体。
• 逐项验收依据：本能力特有的检查项与复核记录。