Level 1: System Context diagram
Level 2: Container diagram
Level 3: Component diagram
Level 4: Code diagram
System Landscape diagram | Dynamic diagram | Deployment diagram
System Landscape diagram
The C4 model provides a static view of a single software system but, in the real-world, software systems never live in isolation. For this reason, and particularly if you are responsible for a collection of software systems, it's often useful to understand how all of these software systems fit together within the bounds of an enterprise. To do this, you can add another diagram that sits "on top" of the C4 diagrams, to show the system landscape from an IT perspective. Like the System Context diagram, this diagram can show organisational boundaries, internal/external users and internal/external systems.
Essentially this is a high-level map of the software systems at the enterprise level, with a C4 drill-down for each software system of interest. From a practical perspective, a system landscape diagram is really just a system context diagram without a specific focus on a particular software system.
Scope: An enterprise.
Primary elements: People and software systems related to the enterprise in scope.
Intended audience: Technical and non-technical people, inside and outside of the software development team.
Here is a System Landscape diagram from the "Big Bank plc" example workspace, showing all of the users and software systems defined within the workspace