Sparx C4 Model Framework Solution

Source

Official solution page

Context

This Sparx Systems solution presents a way to use Enterprise Architect to apply the C4 model framework for software architecture documentation. It is relevant to the [[C4 Framework Options]] thought because it represents an EA-oriented, model-driven approach rather than relying only on external diagramming tools.

C4 framework levels

The solution is organized around the C4 model's progressive levels of detail:

1. System Context — shows the system of interest, its users, and external systems.
2. Container — decomposes the system into applications, services, databases, and other deployable or significant parts.
3. Component — decomposes a container into its major internal building blocks.
4. Code — represents implementation-level detail such as classes and code structures.

The purpose is to let different audiences view the same architecture at an appropriate level of abstraction.

Enterprise Architect approach

The page demonstrates C4-style modeling in EA using model elements, relationships, boundaries, diagrams, and documentation. The approach can be treated as a practical EA modeling pattern or solution configuration. It does not necessarily mean that C4 is a default, built-in EA language in the same way as UML; confirm the exact downloadable technology, templates, or supporting assets on the source page before deployment.

How to use this option

1. Review the source page and any associated diagrams, downloadable files, or implementation assets.
2. Confirm compatibility with the organization's EA version and licensing.
3. Identify the element types, stereotypes, colors, relationship labels, and diagram conventions used by the solution.
4. Decide whether to adopt the supplied configuration directly, adapt it into an internal UML Profile, or formalize it as a custom MDG Technology.
5. Create a pilot model with one system-context view, one container view, and one component view.
6. Define ownership and naming rules for systems, containers, components, people, and external dependencies.
7. Validate that relationships are labeled with meaningful verb phrases and that diagrams remain readable.
8. Add the approach to the organization's architecture modeling standard.
9. Test publishing, reporting, repository collaboration, and model exchange before wider rollout.

Example

For an Order Management system:

System Context:

Customer -> Order Management System : places orders

Order Management System -> Payment Service : authorizes payments

Container:

Order Management System

Web Application

Orders API

Orders Database

Component:

Orders API

Order Controller

Pricing Service

Payment Adapter

Advantages

• Provides a direct Sparx/EA-oriented reference for applying C4.
• Keeps C4 views within the broader EA repository and architecture model.
• Can support traceability between high-level architecture and detailed model content.
• Provides a more consistent starting point than inventing C4 conventions from scratch.
• Can be combined with EA collaboration, repository, documentation, and publishing capabilities.

Limitations and verification points

• Verify whether the page provides a formal MDG Technology, a model template, diagrams, or only an illustrative solution description.
• Confirm the licensing and redistribution terms for any downloadable assets.
• Check compatibility with the deployed EA release.
• Determine whether the approach supports native semantic relationships, reporting, validation, and round-trip exchange.
• Ensure the C4 representation does not become overly detailed or visually complex.
• Establish a source-of-truth policy if C4-PlantUML, Structurizr, code analysis, or other external tools are also used.

Relationship to other C4 options

Recommended evaluation

Treat the Sparx solution as the first EA-specific reference to evaluate. Use it for a small pilot, inspect exactly what assets and conventions it supplies, and then decide whether to use it as-is, adapt it as a UML Profile, or package a governed version as a custom MDG Technology.