> For the complete documentation index, see [llms.txt](https://specs.govstack.global/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://specs.govstack.global/implementation-playbook/implementation/design-architecture/5-a-system-landscape.md).

# 5-A System Landscape

## Purpose

The System Landscape Diagram

* describes
  * the IT architecture of your organization (or a department of that)
  * the services provided by the organization
  * the systems required to provide those services
* gives an overview of what systems exist in an organization and how they interact with each other
* informs about
  * dependencies & bottlenecks
  * reuse within the organization
    * usage / adoption of building blocks (for example a central Identity component)
  * redundancies & duplication

## Scope

A single diagram can usually only hold the information on a subset of systems. In the context of this playbook, the System Landscape should describe

* a single organization
* all software systems of that organization that
  * are necessary to provide the e-government services of that organization
  * follow the same or similar governance (for example all systems using GovStack)
* all interfaces between those systems
* all outside interfaces of those systems
* should be grouped into clusters representing the services provided by the organization (one cluster - one service / Fachverfahren)

## How to do it

* If the System Landscape Diagram already exists, just update it, by adding the information from the System Context diagram.
* If it does not exist, it can easily be created from System Context
  * It might be useful to add additional boxes to create groups of systems, where suitable
* Optionally: if you want to further complete the System Landscape, go back to the previous step and create System Context for further systems. This way you will document the Government Architecture step-by-step.

Example System Landscape Diagram: 

<figure><img src="/files/9TMjWCg7DFR4AaxTE4CY" alt=""><figcaption><p>Adapted from https://c4model.com (CC BY 4.0). Changes made.</p></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://specs.govstack.global/implementation-playbook/implementation/design-architecture/5-a-system-landscape.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.