The C4 Model Diagram<\/strong> is a hierarchical, four-level architectural framework designed to document software architecture with varying degrees of granular detail. Created by Simon Brown, C4 avoids vague boxes and lines by structuring system maps into four explicit abstraction lenses: Context<\/strong> (System-level scope), Container<\/strong> (Applications and data stores), Component<\/strong> (Internal modules), and Code<\/strong> (Class-level implementations).<\/p>\n To implement this model effectively in text, engineers use the official Building a valid C4 model using PlantUML relies on importing the correct library files, selecting structural macros, establishing boundaries, and using specialized relationship links.<\/p>\n The At the high-level System Context tier, you model internal components, external dependencies, and human end-users. The standard library provides specific macros that accept an ID, a visual label, and an optional descriptive tag:<\/p>\nC4-PlantUML<\/code> standard library extension. This library replaces raw UML shapes with specialized macros that auto-inject distinct colors, shapes, and metadata fields for users, systems, and databases. With VPasCode<\/strong>, you can define these nested environments cleanly in code. The layout engine dynamically routes connection vectors and scales text fields without ruining your layout geometry.<\/p>\nCore Syntax Guide: Elements and Constructs<\/h2>\n
1. Importing the C4 Standard Library Files<\/h3>\n
C4-PlantUML<\/code> extension is broken up into individual files that map directly to the distinct levels of the abstraction model. To prevent performance slowdowns or compiler errors, you should only import the specific file layer your diagram targets:<\/p>\n@startuml\r\n' Include the specific C4 layer file required\r\n!include <C4\/C4_Context>\r\n' Use C4_Container or C4_Component for deeper architectural maps<\/code><\/pre>\n2. Declaring Core Actors and Systems (Context Level)<\/h3>\n
\n
Person(id, \"Label\", \"Description\")<\/code> \u2014 Represents a human user profile or system actor.<\/li>\nSystem(id, \"Label\", \"Description\")<\/code> \u2014 Represents a primary internal software application or service ecosystem.<\/li>\nSystem_Ext(id, \"Label\", \"Description\")<\/code> \u2014 Represents an external system or third-party API dependency (renders in an explicit grey color palette).<\/li>\n<\/ul>\n