System Landscape Diagram
The widest view. Shows all software systems within an organizational boundary and how they relate to each other and to people.
Scope
An enterprise, organization, department, or any defined boundary containing multiple software systems.
Elements
- Primary: People and software systems within the chosen scope
- No containers or components — everything stays at the software system level
Audience
Everyone — technical and non-technical. This is the enterprise architecture view. Answers: "What systems do we have, who uses them, and how do they connect?"
How It Differs from System Context
A System Context diagram focuses on ONE system and shows what surrounds it. A System Landscape diagram has NO single focus — it shows the entire portfolio equally. Think of it as a System Context diagram without the zoom.
What to Include
- All software systems relevant to the scope
- All user roles/types that interact with these systems
- Relationships between systems showing what flows
- Clear organizational boundary
What NOT to Include
- Internal structure of any system
- Infrastructure or deployment details
- Systems outside the organizational scope (unless they're key external dependencies)
When to Create
- For larger organizations managing multiple systems
- When onboarding someone to an entire technical landscape
- As a bridge to enterprise architecture discussions
- When planning cross-system initiatives or migrations
- To identify duplication or integration opportunities across systems