What belongs in a solution’s system context diagram?

Question

IT Interview Practice · Accepted Answer

A **system context diagram** shows the system being designed, the people using it and the external systems it interacts with. It establishes scope before the team discusses internal implementation.

## Example: a returns portal

```text
[Customer] -- submits return --> [Returns portal]
[Support agent] -- reviews return --> [Returns portal]
[Returns portal] -- checks order --> [Order system]
[Returns portal] -- requests receipt --> [Warehouse system]
```

Use named relationships that describe the business interaction. Make the system in scope visually distinguishable from its neighbors. Include a short purpose for unfamiliar systems so a business stakeholder can understand the diagram.

## What to review

Check whether any actor or dependency is missing, which interactions cross organizational boundaries and whether the chosen scope matches the business objective. The diagram can reveal that an apparently small portal depends on a warehouse team outside the project.

Keep internal services, tables and deployment nodes for more detailed views. Mixing them into the context view makes the boundary harder to understand.

## Interview signal

Explain what the diagram helps people agree on: scope and external relationships. It does not prove security, timing or failure behavior; those need additional views and evidence.

Reference: [C4 system context diagram](https://c4model.com/diagrams/system-context).

Example: a returns portal

What to review

Interview signal

Related questions