C4 Model Software Architecture Projection

EdgeNode projects digital twin structural ontologies into Simon Brown's C4 model for software architecture. By translating root structural units into system boundaries, hierarchical child nodes into encapsulated components, and relationship types into labeled dependency arrows, the compiler generates clear, scope-driven architectural views.

High-Level C4 Mapping Overview

While ArchiMate answers which enterprise layer an entity inhabits, C4 models how software building blocks are scoped, contained, and connected.

Core Design Principles Behind the Mapping

1. Hierarchy is Structural Containment: The twin's node tree directly determines C4 nesting. Child nodes are rendered inside the boundary box of their parent node.
2. Type-Driven Kinds: The C4 element classification is strictly determined by Definition type rather than name heuristics.
3. Canonical C4 Visual Syntax: Renders using official C4 color schemes, standardized element text stacks (Name, [Kind], [Technology], Description), dashed boundaries, and plain solid arrows.
4. Scope Over Metrics: Unlike ArchiMate, C4 diagrams omit labor costs and processing durations. C4 communicates architectural scope, preserving operational metrics solely as latency suffixes on dependency connectors.

1. System Boundaries and Structural Containment

The layout engine partitions nodes into Boundaries (Groups) and Leaf Elements:

Boundary Groups

Rendered as dashed, grey-stroked, rounded boundary containers displaying the structural unit's name. Group nodes are never rendered as standalone boxes; they act as the bounding context. Edges terminating directly on group nodes are omitted because containment expresses the relationship.

Leaf Elements

All child nodes and non-boundary root entities are rendered as concrete C4 blocks positioned inside their respective parent boundaries.

2. Element Classification & Palette

Leaf nodes are classified into standardized C4 kinds based on their Definition type in the active semantic twin:

3. Dependency Connectors & Latency Labels

Unlike ArchiMate, which uses multiple distinct arrowheads (diamonds, triangles, open arrows) to distinguish relationship verbs, C4 standardizes on plain solid arrows:

• Connector Semantics: All relationships render as solid directional arrows.
• Label Syntax: The connector label explicitly states the domain verb and cumulative latency: <verb> [<cumulative latency>s] (e.g., requires [0.010s]).

4. Layered Layout Algorithm

The C4 rendering engine structures elements using longest-path topological layering:

• Columns (Stage Rank): Calculated via longest-path dependency depth over all relationships except composes. Composition is treated as structural containment rather than directional flow.
• Rows (Tracks): Within each boundary and column intersection, elements stack vertically. Unparented elements occupy a shared baseline track.
• Boundary Wrapping: Dashed bounding boxes expand dynamically to encompass all internal child components.

Worked Example: Trading Platform Architecture

Consider an enterprise digital twin modeling an electronic trading environment:

Data Model

• Root Boundary: Trading Platform (Definition type = 'structural_unit', parent_id = NULL).
• Child Nodes:
  • Order Service (Definition type = 'process', parent = Trading Platform) $\rightarrow$ Container.
  • Ledger (Definition type = 'artifact', parent = Trading Platform) $\rightarrow$ Database.
  • Risk Rules (Definition type = 'concept', parent = Trading Platform) $\rightarrow$ Component.
• Relationships:
  • Order Service $\xrightarrow{\text{requires [0.010s]}}$ Ledger.
  • Order Service $\xrightarrow{\text{couples [0.005s]}}$ Risk Rules.

Comparison Across Modeling Standards