Software → Software Architecture
System Landscape Diagram
A C4 supporting diagram that maps the people and software systems within an organisation, portfolio, or other broad scope.
Motivation
A System Landscape Diagram helps teams understand how a collection of software systems fits together across an organisation, department, or portfolio.
Where it fits
In the C4 Model, it is a supporting diagram rather than one of the four core hierarchical views. It is similar to a System Context Diagram without focusing on one particular software system.
Primary elements
- People within the chosen scope.
- Software systems within or interacting with that scope.
- Relationships that explain how those people and systems interact.
Practical use
Use it to communicate portfolio boundaries, integration dependencies, ownership, duplicated capabilities, and the broader context around individual systems.
Common mistakes
- Turning the landscape into a deployment or infrastructure diagram.
- Showing every technical component instead of software systems.
- Omitting scope, ownership, or relationship descriptions.
- Letting the diagram become stale as the portfolio changes.