Skip to main content

PlantUML commands for Archimate

Diagram as a code may be cool thing to learn. PlantUML is a platform and can be installed locally, suing that one can create diagrams using a code syntax. It offers many types of diagrams and here I am posting list of commands in plantuml that help in ArchiMate notation. 

Commands for elements

How does it look like?:


Code

@startuml

!includeurl https://raw.githubusercontent.com/plantuml-stdlib/Archimate-PlantUML/master/Archimate.puml

!theme archimate-standard from https://raw.githubusercontent.com/plantuml-stdlib/Archimate-PlantUML/master/themes

title List of Archimate Elements & Relationships (PlantUML)

' =======================================

' MOTIVATION LAYER (WHY?)

' =======================================

Motivation_Assessment(Assessment, "Assessment")

Motivation_Constraint(Constraint, "Constraint")

Motivation_Driver(Driver, "Driver")

Motivation_Goal(Goal, "Goal")

Motivation_Outcome(Outcome, "Outcome")

Motivation_Principle(Principle, "Principle")

Motivation_Requirement(Requirement, "Requirement")

Motivation_Stakeholder(Stakeholder, "Stakeholder")

Motivation_Value(Value, "Value")

Motivation_Meaning(motMeaning, "Motivation Meaning")


' =======================================

' STRATEGY LAYER (WHAT?)

' =======================================

Strategy_Capability(Capability, "Capability")

Strategy_CourseOfAction(CourseOfAction, "Course of Action")

Strategy_Resource(Resource, "Resource")

Strategy_ValueStream(ValueStream, "Value Stream")


' =======================================

' BUSINESS LAYER (WHO & HOW?)

' =======================================

Business_Actor(Actor, "Business Actor")

Business_Collaboration(BusCollaboration, "Business Collaboration")

Business_Contract(Contract, "Contract")

Business_Event(Event, "Event")

Business_Function(Function, "Business Function")

Business_Interaction(BusInteraction, "Business Interaction")

Business_Interface(BusInterface, "Business Interface")

Business_Location(Location, "Business Location")

Business_Object(BusinessObject, "Business Object")

Business_Process(Process, "Business Process")

Business_Product(Product, "Product")

Business_Representation(Representation, "Representation")

Business_Role(Role, "Business Role")

Business_Service(BusService, "Business Service")


' =======================================

' APPLICATION LAYER (SOFTWARE & DATA SERVICES)

' =======================================

Application_Collaboration(AppCollaboration, "Application Collaboration")

Application_Component(AppComponent, "Application Component")

Application_DataObject(DataObject, "Data Object")

Application_Event(AppEvent, "Application Event")

Application_Function(AppFunction, "Application Function")

Application_Interaction(AppInteraction, "Application Interaction")

Application_Interface(AppInterface, "Application Interface")

Application_Process(AppProcess, "Application Process")

Application_Service(AppService, "Application Service")


' =======================================

' TECHNOLOGY LAYER (INFRASTRUCTURE)

' =======================================

Technology_Artifact(TechArtifact, "Technology Artifact")

Technology_Collaboration(TechCollaboration, "Technology Collaboration")

Technology_CommunicationNetwork(TechNetwork, "Communication Network")

Technology_Device(TechDevice, "Technology Device")

Technology_Event(TechEvent, "Technology Event")

Technology_Function(TechFunction, "Technology Function")

Technology_Interface(TechInterface, "Technology Interface")

Technology_Interaction(TechInteraction, "Technology Interaction")

Technology_Node(TechNode, "Technology Node")

Technology_Path(TechPath, "Technology Path")

Technology_Process(TechProcess, "Technology Process")

Technology_Service(TechService, "Technology Service")

Technology_SystemSoftware(SystemSoftware, "System Software")


' =======================================

' IMPLEMENTATION & MIGRATION LAYER (CHANGES & ROADMAP)

' =======================================

Implementation_Deliverable(Deliverable, "Deliverable")

Implementation_Gap(Gap, "Gap")

Implementation_Plateau(Plateau, "Plateau")

Implementation_WorkPackage(WorkPackage, "Work Package")


' =======================================

' GROUPING ELEMENTS BY LAYER

' =======================================

Grouping(name, "label")

@enduml


Relations (connecting links)

General form
Rel_Name(FromElement, ToElement, Name)

How does it look like?:




Code


@startuml
!includeurl https://raw.githubusercontent.com/plantuml-stdlib/Archimate-PlantUML/master/Archimate.puml
!theme archimate-standard from https://raw.githubusercontent.com/plantuml-stdlib/Archimate-PlantUML/master/themes


title ArchiMate Relationships
skinparam nodesep 5
<style>
interface {
    shadowing 0
    backgroundcolor transparent
    linecolor transparent
    FontColor transparent
}

rectangle {
LineColor: Blue;
LineStyle: 3
MinimumWidth: 400;
FontColor: Red;
}

element {
MinimumWidth: 200;
FontSize: 16;
}

Arrow {
FontColor: Blue;
FontSize: 16;
}
</style>
!include <archimate/Archimate>
left to right direction

rectangle Other {
() From15
() To15

}

rectangle Dynamic {
() From14
() To14
() From13
() To13

} 


rectangle Dependency {
() From12
() To12
() From11
() To11
() From10
() To10
() From9
() To9
() From8
() To8
() From7
() To7
() From6
() To6
() From5
() To5
}



rectangle Structural {
() From4
() To4
() From3
() To3
() From2
() To2
() From1
() To1
}

Rel_Specialization(From15, To15, Specialization)

Rel_Triggering(From14, To14, Triggering)
Rel_Flow(From13, To13, Flow)

Rel_Access_w(From12, To12, Access_w)
Rel_Access_rw(From11, To11, Access_rw)
Rel_Access_r(From10, To10, Access_r)
Rel_Access(From9, To9, Access)
Rel_Influence(From8, To8, Influence)
Rel_Association_dir(From7, To7, \nAssociation_dir)
Rel_Association(From6, To6, Association)
Rel_Serving(From5, To5, Serving)


Rel_Realization(From4, To4, Realization)
Rel_Composition(From3, To3, Composition)
Rel_Assignment(From2, To2, Assignment)
Rel_Aggregation(From1, To1, Aggregation)
@enduml
Labels:

Comments

Post a Comment

Popular posts from this blog

Virtual environments in python

 Creating virtual environments is essential for isolating dependencies and ensuring consistency across different projects. Here are the main methods and tools available, along with their pros, cons, and recommendations : 1. venv (Built-in Python Virtual Environment) Overview: venv is a lightweight virtual environment module included in Python (since Python 3.3). It allows you to create isolated environments without additional dependencies. How to Use: python -m venv myenv source myenv/bin/activate # On macOS/Linux myenv\Scripts\activate # On Windows Pros: ✅ Built-in – No need to install anything extra. ✅ Lightweight – Minimal overhead compared to other tools. ✅ Works across all platforms . ✅ Good for simple projects . Cons: ❌ No dependency management – You still need pip and requirements.txt . ❌ Not as feature-rich as other tools . ❌ No package isolation per project directory (requires manual activation). Recommendation: Use venv if you need a simple, lightweight solut...
Post a Comment
Read more

Building a Simple Text Generator: A Hands-on Introduction

Introduction Text generation is one of the most exciting applications of Natural Language Processing (NLP) . From autocorrect and chatbots to AI-generated stories and news articles , text generation models help machines produce human-like text. In this blog post, we’ll introduce a simple yet effective text generation method using Markov Chains . Unlike deep learning models like GPT, this approach doesn’t require complex neural networks—it relies on probability-based word transitions to create text. We’ll walk through: ✅ The concept of Markov Chains and how they apply to text generation. ✅ A step-by-step implementation , fetching Wikipedia text and training a basic text generator. ✅ Example outputs and future improvements. The Concept of Markov Chains in Text Generation A Markov Chain is a probabilistic model that predicts future states (or words) based only on the current state (or word), rather than the full sentence history. How it works in text generation: 1️⃣ We analyze a gi...
Post a Comment
Read more

Mastering Trade-Off Analysis in System Architecture: A Strategic Guide for Architects

 In system architecture and design, balancing conflicting system qualities is both an art and a science. Trade-off analysis is a strategic evaluation process that enables architects to make informed decisions that align with business goals and technical constraints. By prioritizing essential system attributes while acknowledging inevitable compromises, architects can craft resilient and efficient solutions. This enhanced guide provides actionable insights and recommendations for architects aiming to master trade-off analysis for impactful architectural decisions. 1. Understanding Trade-Off Analysis Trade-off analysis involves identifying and evaluating the conflicting requirements and design decisions within a system. Architects must balance critical aspects like performance, scalability, cost, security, and maintainability. Since no system can be optimized for every quality simultaneously, prioritization based on project goals is essential. Actionable Insights: Define key quality ...
Post a Comment
Read more