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

Comments

Popular posts from this blog

Example 1: ArchiMate relationship in PlantUML code to demonstrate 15 relationship types

 Following section presents 15 types of relationships in ArchiMate and PlantUML to generate the diagram. Since this code is generated by GEN-AI it may require precision on aspects other than PlantUML syntax: Diagram Plant UML Code:  @startuml '!includeurl https://raw.githubusercontent.com/plantuml-stdlib/Archimate-PlantUML/master/Archimate.puml ' Another way of including Archimate Library (above is commented for following) !include <archimate/Archimate> !theme archimate-standard from https://raw.githubusercontent.com/plantuml-stdlib/Archimate-PlantUML/master/themes title ArchiMate Relationships Overview <style> element{     HorizontalAlignment: left;     MinimumWidth : 180;     Padding: 25; } </style> left to right direction rectangle Other {     Business_Role(Role_SeniorManager, "Senior Manager")     Business_Role(Role_Manager, "Manager") } rectangle Dynamic {     Business_Event(Event_CustomerReques...

Examples 7: ArchiMate flow relationship between elements in layers

Diagram Code @startuml !include < archimate / Archimate > < style > element {     HorizontalAlignment : left ;     MinimumWidth : 180 ;     Padding : 20 ; } note {     BackgroundColor : #FFFFCC ;     RoundCorner : 5 ;     MaximumWidth : 250 ; } </ style > title "ArchiMate 3.2 Valid Flow Relationships" left to right direction ' Business Layer Flow Relationships rectangle "Business Layer Flows" {     Business_Process ( bp1 , "Order Process" )     Business_Process ( bp2 , "Payment Process" )     Rel_Flow ( bp1 , bp2 , "Order data" )     note on link         Flow between Business Processes     end note         Business_Function ( bf1 , "Sales Function" )     Business_Function ( bf2 , "Delivery Function" )     Rel_Flow ( bf1 , bf2 , "Sales information" )     note on link     ...

SmartSimpleTextGenerator: A Smarter Way to Generate Text

  Introduction In the world of text generation, simple n-gram models can produce decent results, but they often lack context-awareness and coherence. To address these limitations, I have developed SmartSimpleTextGenerator , an improved version of my previous project, ImprovedSimpleTextGenerator . This new version enhances the text generation process by integrating Part-of-Speech (POS) tagging , n-gram models , and a back-off strategy , making the generated text more meaningful and contextually relevant. Key Features of SmartSimpleTextGenerator ✅ N-Gram Model with POS Tagging – Uses trigrams (default n=3) and applies POS tagging for better word prediction. ✅ Back-off Strategy – If a trigram sequence is unavailable, it falls back to bigrams and unigrams to ensure smooth text generation. ✅ Sentence Tokenization & Structure Preservation – Tokenizes input text properly while maintaining sentence integrity. ✅ Randomized Word Selection – Generates diverse outputs rather ...