A C4 Context diagram tool should help a reader identify the system, its users and its external dependencies in one view. The test is whether a new reader understands the boundary before you explain the implementation.
Inspect a ride-sharing context
Locate the rider and driver, then trace their relationships to the platform. Identify which capabilities depend on another organization’s system. Payments, maps and messaging can have different owners and failure modes even when the user experiences one app.
Do not add every service from the repository to this view. A system context describes the software system in its environment. Internal applications and stores belong in a container view.
Draw the boundary before adding arrows
Write a one-sentence responsibility for the main system. List the people or roles that use it. Then list external systems needed to fulfill that responsibility. If your team cannot agree whether a dependency is internal or external, record who owns and changes it before choosing a visual style.
Each relationship needs a purpose. “Uses” is a starting point; “Requests a ride” or “Authorizes payment” gives reviewers something to validate. A protocol is optional at this level when it adds no useful context.
Try the shared-element test
Download the checkout example, which includes a context view and two deeper views. Its context has a Customer, Commerce platform and Payment provider. Rename the provider once in the model and regenerate the views. The point is shared identity, not matching box colors.
In UXXU, create the external system once and reuse it when adding a container view. Keep each diagram’s layout focused on its audience. Use the connected-model rename demonstration to see this principle before signing up.
Review the result with three questions
Can a reader name the main system’s responsibility? Can they identify the people who use it? Can they name the external dependencies that must be considered during an outage? If any answer requires opening an implementation view, simplify or relabel the context.
The official system context definition and the practical context guide explain the notation. The C4 model tool is the place to evaluate editing and maintaining these views.