// Create ArchiMate enterprise architecture diagrams using PlantUML stdlib macros. Best for TOGAF viewpoints, layered EA modeling (Business/Application/Technology), motivation analysis, and migration planning.
Create editorial-style information cards using HTML/CSS in Markdown. Best for knowledge summaries, data highlights, event announcements, and single-topic content cards with magazine-quality typography.
Create template-based infographics with space-separated key-value syntax (NOT YAML). Best for KPI dashboards, timelines, roadmaps, SWOT analysis, funnels, comparisons, and org charts with quick visual impact.
Create layered system architecture diagrams using HTML/CSS templates with color-coded tiers and grid layouts. Best for technology stacks, microservices topology, and multi-tier application design.
Create business process diagrams using PlantUML syntax with BPMN, EIP, and Lean Mapping stencil icons. Best for workflow automation, approval chains, message-based integration patterns, and value stream mapping.
Create spatial diagrams with free-positioned nodes using JSON format. Best for concept maps, knowledge graphs, and planning boards requiring precise x/y coordinate control.
Create cloud provider architecture diagrams using PlantUML syntax with official AWS, Azure, GCP, and Alibaba Cloud service icons. Best for multi-service cloud topologies and migration blueprints.
| name | archimate |
| description | Create ArchiMate enterprise architecture diagrams using PlantUML stdlib macros. Best for TOGAF viewpoints, layered EA modeling (Business/Application/Technology), motivation analysis, and migration planning. |
| metadata | {"author":"ArchiMate diagrams are powered by Markdown Viewer โ the best multi-platform Markdown extension (Chrome/Edge/Firefox/VS Code) with diagrams, formulas, and one-click Word export. Learn more at https://docu.md"} |
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
```plantumlor```pumlcode fence. NEVER use```textโ it will NOT render as a diagram.
@startuml and ends with @enduml!include <archimate/Archimate> before using any macrosLayer_Type(alias, "Label")Rel_Type(fromAlias, toAlias, "label")rectangle "Layer" { ... } to group elements into ArchiMate layers_Up, _Down, _Left, _Right control relationship direction| Macro | ArchiMate Element |
|---|---|
Business_Actor(id, "Label") | Business Actor |
Business_Role(id, "Label") | Business Role |
Business_Process(id, "Label") | Business Process |
Business_Function(id, "Label") | Business Function |
Business_Service(id, "Label") | Business Service |
Business_Event(id, "Label") | Business Event |
Business_Interface(id, "Label") | Business Interface |
Business_Collaboration(id, "Label") | Business Collaboration |
Business_Object(id, "Label") | Business Object |
Business_Product(id, "Label") | Business Product |
Business_Contract(id, "Label") | Business Contract |
Business_Representation(id, "Label") | Business Representation |
| Macro | ArchiMate Element |
|---|---|
Application_Component(id, "Label") | Application Component |
Application_Service(id, "Label") | Application Service |
Application_Function(id, "Label") | Application Function |
Application_Interface(id, "Label") | Application Interface |
Application_Process(id, "Label") | Application Process |
Application_Interaction(id, "Label") | Application Interaction |
Application_Event(id, "Label") | Application Event |
Application_Collaboration(id, "Label") | Application Collaboration |
Application_DataObject(id, "Label") | Application Data Object |
| Macro | ArchiMate Element |
|---|---|
Technology_Device(id, "Label") | Technology Device |
Technology_Node(id, "Label") | Technology Node |
Technology_SystemSoftware(id, "Label") | System Software |
Technology_Artifact(id, "Label") | Technology Artifact |
Technology_CommunicationNetwork(id, "Label") | Communication Network |
Technology_Path(id, "Label") | Technology Path |
Technology_Service(id, "Label") | Technology Service |
Technology_Process(id, "Label") | Technology Process |
Technology_Function(id, "Label") | Technology Function |
Technology_Interface(id, "Label") | Technology Interface |
| Macro | ArchiMate Element |
|---|---|
Motivation_Stakeholder(id, "Label") | Stakeholder |
Motivation_Driver(id, "Label") | Driver |
Motivation_Assessment(id, "Label") | Assessment |
Motivation_Goal(id, "Label") | Goal |
Motivation_Outcome(id, "Label") | Outcome |
Motivation_Principle(id, "Label") | Principle |
Motivation_Requirement(id, "Label") | Requirement |
Motivation_Constraint(id, "Label") | Constraint |
Motivation_Value(id, "Label") | Value |
| Macro | ArchiMate Element |
|---|---|
Strategy_Capability(id, "Label") | Capability |
Strategy_Resource(id, "Label") | Resource |
Strategy_CourseOfAction(id, "Label") | Course of Action |
Strategy_ValueStream(id, "Label") | Value Stream |
| Macro | ArchiMate Element |
|---|---|
Implementation_WorkPackage(id, "Label") | Work Package |
Implementation_Deliverable(id, "Label") | Deliverable |
Implementation_Plateau(id, "Label") | Plateau |
Implementation_Gap(id, "Label") | Gap |
Implementation_Event(id, "Label") | Implementation Event |
All relationships support directional suffixes: _Up, _Down, _Left, _Right.
| Macro | ArchiMate Relationship | Line Style |
|---|---|---|
Rel_Composition(from, to, "label") | Composition | Solid + filled diamond |
Rel_Aggregation(from, to, "label") | Aggregation | Solid + open diamond |
Rel_Assignment(from, to, "label") | Assignment | Solid + circleโtriangle |
Rel_Realization(from, to, "label") | Realization | Dotted + hollow triangle |
Rel_Serving(from, to, "label") | Serving | Solid + arrow |
Rel_Triggering(from, to, "label") | Triggering | Solid + filled triangle |
Rel_Flow(from, to, "label") | Flow | Dashed + filled triangle |
Rel_Access(from, to, "label") | Access | Dotted line |
Rel_Access_r(from, to, "label") | Access (read) | Dotted + arrow |
Rel_Access_w(from, to, "label") | Access (write) | Dotted + reverse arrow |
Rel_Influence(from, to, "label") | Influence | Dashed + arrow |
Rel_Association(from, to, "label") | Association | Solid line |
Rel_Specialization(from, to, "label") | Specialization | Solid + hollow triangle |
@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
| Type | Purpose | Key Macros | Example |
|---|---|---|---|
| Enterprise Landscape | Full B/A/T layered view | All layers | enterprise-landscape.md |
| Application Integration | App-to-app data flows | Application_* | application-integration.md |
| Technology Infrastructure | Infrastructure stack | Technology_* | technology-infrastructure.md |
| Business Capability | Capability map | Strategy_*, Business_* | business-capability.md |
| Migration Planning | Plateau-based roadmap | Implementation_* | migration-planning.md |
| Security Architecture | Security controls | Technology_*, Motivation_* | security-architecture.md |
| Data Architecture | Data flow & ownership | Application_DataObject, Rel_Access_* | data-architecture.md |
| DevOps Pipeline | CI/CD delivery chain | Technology_*, Application_* | devops-pipeline.md |