liveBook · Manning

Context diagram

As explained in Developer Experience on Kubernetes

A system context diagram is a high-level architecture diagram showing a software system, its users, and the other systems with which it interacts.

A context diagram is a high-level architecture diagram that shows a software system, its users, and the other systems with which it interacts. It defines the system boundary without exposing internal components or implementation technologies, making it useful to both technical and non-technical stakeholders. section 1.4.1 section 1.5

A C4 context diagram identifies two primary abstractions:

  • Person: a human user of the software system. section 1.4.1
  • Software System: the overall system that delivers value to its users. section 1.4.1
  • Interactions: relationships between the system, its users, and external systems. section 1.4.1

MinSalus

A patient uses MinSalus to book appointments with doctors and receive updates about schedule changes or follow-up appointments. The context diagram represents the patient as a Person and MinSalus as the Software System. Developers need a container diagram to inspect internal applications, data services, responsibilities, and interactions. section 1.4.1

How Developer Experience on Kubernetes covers it

How deep it goes
Defines users, systems, and interactions but stops short of internal components and implementation technologies.
Examples
Uses MinSalus, a patient, appointment booking, doctor scheduling, and follow-up notifications.
What it assumes
Introduces Person and Software System abstractions without requiring knowledge of internal implementation technologies.
What you can do after
Evaluate system boundaries and external relationships before investigating internal architecture.
How it connects
Connects the C4 model with software architecture and container diagrams.

Also explained in

Compare how 2 books explain context diagram →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Developer Experience on Kubernetes. The section links point to the parts of the book it draws on.