Skip to main content

PlantUML other commands

There are several other commands useful along with core commands for styling and layout. 

' List all ArchiMate icons

@startuml

listsprite

@enduml

-----------------------

' Layout of the elements 

top to bottom direction

' New way of defining style of the elements. Style can be defined for all elements or specific type of element or an annotated element

<style>

element {

FontColor: green;

}

rectangle {

  MinimumWidth: 600;

   VerticalAlignment: left;

  HorizontalAlignment: center

}

</style>

--------------------------------------

' A detailed example of styling 

@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
top to bottom direction

<style>
.a {
  MinimumWidth: 650;
  FontColor: blue;
  VerticalAlignment: left;
  HorizontalAlignment: center;
  BackGroundColor: #faf7f6;
  LineColor: #ff45ff;
  FontStyle: italic;
  LineStyle: 3;
  Padding: 0;
  Margin: 0;
}

.b {
  MinimumWidth: 600;
  
  VerticalAlignment: left;
  HorizontalAlignment: center;
  FontColor: green;
  LineColor: purple;
  LineStyle: dotted;
  margin: 0;
  padding: 0;

}


</style>

rectangle "OuterBox" as OuterBox <<a>>{


rectangle "Motivation Layer" as motivationLayer <<b>>{
 
    Motivation_Stakeholder(Stakeholder, "Project Manager")
    Motivation_Goal(Goal, "Increase Efficiency")
    Motivation_Requirement(Requirement, "Automate Task Assignments")
}

rectangle "Strategy Layer" as strategyLayer <<b>>{

    Strategy_Capability(Capability, "Task Automation")
    Strategy_Resource(Resource, "AI-based Task Engine")
}

rectangle "Business Layer" as businessLayer <<b>>{

    Business_Actor(Actor, "Employee")
    Business_Process(Process, "Task Assignment")
    Business_Service(Service, "Task Management Service")
}

rectangle "Application Layer" as applicationLayer <<b>>{

    Application_Component(AppComponent, "Task Management API")
    Application_Service(AppService, "Task Processing Service")
}

rectangle "Technology Layer" as technologyLayer <<b>> {

    Technology_Node(TechNode, "Cloud Server")
    Technology_Service(TechService, "Database Hosting")
}

}

Stakeholder -[hidden]- Capability
Capability -[hidden]- Actor
Actor -[hidden]- AppComponent
AppComponent -[hidden]- TechNode
@enduml

-------------------------
' Putting elements in a box can be done by various methods: Grouping, rectangle, Mainframe, frame

' Creating a box around everything that is below mainframe 

mainframe This is a **mainframe**

' Creating a box with brackets so that elements inside brackets display in the box
Mainframe OuterFrame {
  frame a {
  }
  frame b {
  }
} 

Themes for Archimate in PlantUML
!theme archimate-handwriting from https://raw.githubusercontent.com/plantuml-stdlib/Archimate-PlantUML/master/themes
!theme archimate-alternate from https://raw.githubusercontent.com/plantuml-stdlib/Archimate-PlantUML/master/themes
!theme archimate-saturated from https://raw.githubusercontent.com/plantuml-stdlib/Archimate-PlantUML/master/themes
!theme archimate-lowsaturation from https://raw.githubusercontent.com/plantuml-stdlib/Archimate-PlantUML/master/themes

Labels:

Comments

Post a Comment

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...
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

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