All posts
Allen
Author, Content Operations Manager·Originally published Jan 27, 2026 · Updated Nov 14, 2026
System context diagram cover: an Online store system in the center connected by labeled arrows to a Shopper, Store staff, a Payment provider and an Email service

System Context Diagram: 5 Examples & Symbols (2026)

What changed (Nov 14, 2026): Rewrote the guide around five original example diagrams (online store, mobile banking app, hospital system, SaaS integrations and an ATM Level 0 DFD), added a symbols image and table for C4 and DFD notation, a C4 system context section, a comparison with DFD, container, use case and sequence diagrams, tool-neutral drawing steps with Mermaid code, common mistakes, FAQs and sources. Removed the concept map sections, the AFFiNE-vs-competitors table and unsourced statistics, and replaced the shared cover.

A system context diagram shows one system as a single box in the middle of the page, the people and other systems that use it or that it depends on around the edge, and a labeled arrow for every interaction between them. It answers one question: where does our system stop, and what does it talk to? Because it hides everything inside the box, both developers and non-technical stakeholders can read it, which is why teams draw it first, before any detailed design.

This guide gives you five worked context diagram examples (an online store, a mobile banking app, a hospital system, a SaaS app with integrations and an ATM), the symbols and rules for both the C4 model and the classic data flow (Level 0 DFD) style, and a step-by-step method for drawing your own.

Disclosure: AFFiNE publishes this guide and makes a whiteboard app. All five examples are fictional and were drawn for this article. The method works in any diagramming tool, and we show AFFiNE as one way to do it, next to other options.

Update note (November 14, 2026): We rewrote this guide around real example diagrams, added the C4 system context notation, and removed claims we could not source.

What is a System Context Diagram?

A system context diagram (also called a context diagram, a context data flow diagram or a Level 0 DFD) is a high-level picture that draws the boundary between a system and its environment. Wikipedia's system context diagram entry describes it as a diagram that "defines the boundary between the system, or part of a system, and its environment, showing the entities that interact with it." The requirements glossary from Karl Wiegers and Joy Beatty's Software Requirements puts it more bluntly: a context diagram "identifies objects outside the system that exchange data with the system, but it shows nothing about the system's internal structure or behavior."

Every context diagram has the same three building blocks:

  • The system in scope. Exactly one box or circle in the center. You do not show anything inside it.
  • External actors. The people (customers, staff, administrators) and the other systems (payment providers, identity providers, legacy back ends, hardware) that interact directly with your system.
  • Labeled arrows. One arrow per interaction, with a short label that says what is exchanged or what the relationship does.

Teams use context diagrams early in a project to agree on scope. Drawing the outside systems forces questions that text requirements often skip: does login use our own accounts or a company identity provider? Who owns the payment integration? Which data comes from a system we do not control? Once everyone agrees on the picture, you can zoom in, either into a Level 1 data flow diagram or into a C4 container diagram.

System Context Diagram Examples

The first four examples use the C4 model notation, which is what most software teams mean by "system context diagram" today. The fifth uses classic data flow notation, which is what many business analysis and systems analysis courses mean by "context diagram". Each one is a simplified, fictional system: copy the structure, not the details.

E-commerce system context diagram (online store)

System context diagram example for an online store: a Shopper and Store staff on the left use the Online store system in the center, which sends payments to a Payment provider, books shipments with a Shipping carrier and sends order emails through an Email service

An online store is the most common context diagram example because almost everyone understands it. The store is the system in scope. Shoppers and store staff are the two people who use it, and three outside services do work the store does not do itself.

What to notice:

  • Payment is a separate system. The store sends card payments to the payment provider and gets a result back. Drawing it outside the box makes clear that card data handling is shared with a third party.
  • There are two arrows between the store and the payment provider. Each arrow has one direction and one meaning, which is easier to read than a single double-headed arrow.
  • The email service delivers to the shopper. The dashed arrow shows an interaction that does not pass through the store but still matters to the shopper's experience.
  • There is no database. The product catalog and order tables are inside the store, so they are not on this diagram.

Mobile banking app context diagram

System context diagram example for a mobile banking app: a Bank customer and Support agent use the Mobile banking app, which reads and posts transactions to a Core banking system, sends transfers through a Payment network, verifies customers with an Identity verification provider and sends alerts through a Push notification service

In this example the system in scope is the banking app together with the back end the app team owns. The bank's core banking system is drawn outside the box because a different team owns it, even though it belongs to the same bank. C4 defines a software system as something a single team builds, owns and can see inside; systems you depend on but do not own sit outside the boundary (c4model.com).

What to notice:

  • "Same company" does not mean "inside the box". The core banking system, the identity verification provider and the payment network are all external dependencies of the app.
  • Labels are specific. "Reads accounts and posts transactions to" tells a reader much more than "uses".
  • Both kinds of people are shown. Customers and support agents need different things from the same system.

Hospital system context diagram

System context diagram example for a hospital patient administration system: a Patient, Front-desk staff and a Clinician use the system, which sends admissions to the Electronic health record, sends test orders to and receives results from a Laboratory information system, and checks eligibility and submits claims to an Insurance payer

Healthcare systems are a good test of a context diagram because there are many people and many neighboring systems. Here the system in scope handles registration, scheduling, admissions and billing. Clinical records, lab work and insurance claims live in other systems.

What to notice:

  • Three people, three roles. The patient, front-desk staff and clinician use the same system for different jobs, so each gets its own element.
  • Lab orders and results are two separate arrows. One goes out, one comes back.
  • The diagram makes scope decisions visible. If someone expects clinical notes to be written in this system, the picture shows that they belong to the EHR instead.

SaaS integration context diagram

System context diagram example for a project management SaaS app: a Team member and Workspace admin use the app, which signs users in through a Company identity provider, charges subscriptions through a Billing provider, posts updates to a Team chat app and receives commit and pull request events from a Code hosting service

For a SaaS product, the context diagram is mostly a map of integrations. This project management app depends on a customer's identity provider for single sign-on, a billing provider for subscriptions, and two tools it integrates with.

What to notice:

  • Arrow direction follows who starts the interaction. The code hosting service sends events to the app, so the arrow points at the app. The app posts updates to the chat tool, so that arrow points away.
  • The identity provider has two relationships. Signing users in and creating or removing their accounts are different flows, often owned by different people on the customer side.
  • No technologies on the arrows. Protocol names such as SAML, OIDC or webhooks belong on a C4 container diagram, not at this level.

ATM context diagram (Level 0 DFD style)

Context diagram example in Level 0 data flow diagram style for an ATM system: the ATM system is a single circle labeled 0, connected by noun-labeled data flows to a Bank customer, the Bank core system, a Card network and a Service technician

The ATM is the classic textbook example, and here it is drawn in Yourdon-DeMarco data flow notation: the system is one circle (process 0), external entities are rectangles, and each arrow is labeled with the data that moves, written as a noun.

What to notice:

  • Labels are nouns, not actions. "Card, PIN, withdrawal request" and "Approval or decline" describe data, which is the DFD convention.
  • The bank's core system is external. The ATM does not keep account balances itself; it asks the bank.
  • The technician is an actor too. Context diagrams often miss operations and maintenance roles, which is how refill and fault alert requirements get forgotten.

If you start from this style, the next step is to break the circle into processes and data stores. Our data flow diagram guide shows the same move from Level 0 to Level 1 with a worked example.

System context diagram symbols and rules

System context diagram symbols compared in C4 notation and data flow notation: the system in scope as a blue box or a numbered circle, people as person shapes or rectangles, other systems as grey boxes or rectangles, and relationships as arrows labeled with a verb phrase or a noun

The two styles use different shapes for the same four things. Pick one style for a set of diagrams and stay with it.

ElementC4 system contextContext DFD (Level 0)
System in scopeOne box, usually highlightedOne circle or rounded rectangle, numbered 0
PeoplePerson shapeRectangle (external entity)
Other systemsBox in a neutral color, marked externalRectangle (external entity)
RelationshipsOne-way arrow labeled with what it does ("Sends card payments to")Arrow labeled with the data that moves ("Payment request")
Not shownContainers, databases, technologiesData stores, sub-processes

Rules that apply to both:

  1. One system in scope per diagram. If you have two, you are drawing a landscape, not a context diagram.
  2. Only direct neighbors. Show a person or system only if it interacts directly with your system.
  3. Label every arrow. The C4 notation guide asks for every line to be labeled and to represent one direction, and recommends avoiding vague single-word labels such as "Uses" (c4model.com).
  4. No data stores or internal parts. Databases, queues and services inside your system belong on the next level down.
  5. Give each element a type and a short description. "[Software System] Authorizes and captures card payments" is easier to read than a bare name.
  6. Add a title and a key. C4 recommends a title that states the diagram type and scope, for example "System Context diagram for Online store", plus a key that explains your shapes, colors and line styles.

What is a C4 system context diagram?

The C4 model, created by Simon Brown, describes software architecture as four levels of zoom: system context, containers, components and code. The system context diagram is level 1, the most zoomed-out view. According to c4model.com:

  • Scope: a single software system.
  • Primary element: the software system in scope.
  • Supporting elements: the people and software systems directly connected to it, which you typically do not own.
  • Audience: everybody, technical and non-technical, inside and outside the development team.
  • Recommended: yes, for all software development teams.

The C4 site also says the focus should be on people and software systems "rather than technologies, protocols and other low-level details." That is the main difference from a Level 0 DFD in practice: C4 labels describe relationships, while DFD labels describe data.

Two related C4 diagrams are worth knowing:

  • Container diagram. Zooms into the box to show the applications and data stores inside it, with their technologies. See the C4 container diagram definition and our software architecture diagram guide for a worked example.
  • System landscape diagram. Shows all the systems in an organization. C4 calls it "really just a system context diagram without a specific focus on a particular software system" (c4model.com).

Context diagram vs. DFD, C4 container and use case diagrams

DiagramWhat it showsShows the inside of the system?Best for
Context diagram / C4 system contextThe system as one box, its users and neighboring systemsNoAgreeing on scope with everyone
Level 1 data flow diagramMain processes, data stores and data flows inside the systemYes, at process levelAnalysing how data moves
C4 container diagramApplications and data stores inside the system, with technologiesYes, at deployable-unit levelDevelopers and operations
Use case diagramActors and the goals they achieve with the systemNo, but lists functionsCapturing functional requirements
Sequence diagramMessages between parts over time for one scenarioOftenDesigning one interaction in detail

For the deeper levels, see our guides to data flow diagrams, UML sequence diagrams, pipeline diagrams and ER diagram tools for database design.

How to draw a system context diagram

These steps work on paper, on a whiteboard or in any diagramming tool.

  1. Name the system and its boundary. Write one sentence about what the system does and who owns it. Anything the owning team cannot change goes outside the box.
  2. List the people. Group users by role, not by individual: customers, staff, admins, support, operations.
  3. List the other systems. Go through payments, identity, email and notifications, data feeds, partner APIs, legacy systems and hardware. Check integration code, API keys and vendor contracts if you are documenting an existing system.
  4. Place the system in the center and the actors around it. Put people on one side and systems on the other; it keeps arrows from crossing.
  5. Draw one arrow per interaction. Decide the direction (who starts it), then write a specific label. In C4 style, use a verb phrase; in DFD style, use a noun.
  6. Remove anything internal. Databases, microservices, queues and technology names move to the next diagram.
  7. Add a title, a key and a date, then review it with someone outside the team. If they can explain the system back to you from the picture alone, the diagram works. The C4 diagram review checklist is a useful final pass.

You can also write the diagram as code. Mermaid and C4-PlantUML both have C4 syntax. This is the online store example in Mermaid's C4Context syntax:

C4Context
  title System Context diagram for an online store
  Person(shopper, "Shopper", "Buys products online")
  Person(staff, "Store staff", "Manages catalog, orders and refunds")
  System(store, "Online store", "Product catalog, cart, checkout and order tracking")
  System_Ext(pay, "Payment provider", "Authorizes and captures card payments")
  System_Ext(ship, "Shipping carrier", "Creates labels and tracking numbers")
  System_Ext(mail, "Email service", "Sends transactional email")
  Rel(shopper, store, "Browses products and places orders using")
  Rel(staff, store, "Manages products, stock and refunds using")
  Rel(store, pay, "Sends card payments to")
  Rel(pay, store, "Returns payment results to")
  Rel(store, ship, "Books shipments and gets tracking from")
  Rel(store, mail, "Sends order emails using")
  Rel(mail, shopper, "Delivers order confirmations to")

Drawing it on a whiteboard: an AFFiNE example

AFFiNE app in Edgeless whiteboard mode with a flowchart drawn from shapes and connectors next to a note card, with the whiteboard toolbar at the bottom
The AFFiNE Edgeless whiteboard in a demo workspace, with a sample diagram drawn from shapes and connectors. Screenshot taken November 7, 2026.

In AFFiNE, you draw a context diagram in Edgeless mode, the whiteboard view of a doc:

  1. Add a rectangle shape in the middle of the canvas for the system in scope and give it a distinct color.
  2. Add shapes for people and external systems around it, each with a name, a type and a one-line description.
  3. Draw connectors from shape to shape and type the label on each connector.
  4. Group the diagram in a frame, add the title and a small key, and keep the scope sentence and open questions in the same doc, so the diagram and its notes stay together.

AFFiNE AI can generate a mind map from a prompt, which is a quick way to brainstorm the list of actors, but it does not draw a context diagram for you; the layout and labels are manual. Other good options are draw.io, which has C4 shapes, Lucidchart and Miro for drag-and-drop diagrams, and Structurizr, C4-PlantUML or Mermaid if you want diagrams as code. The C4 site keeps a longer tooling list.

Common context diagram mistakes

  • Drawing the inside of the system. If you see a database or a microservice, you have started a container diagram or a Level 1 DFD.
  • Unlabeled or two-headed arrows. They hide what actually happens. Split them into one labeled arrow per direction.
  • Generic labels. "Uses" or "Data" says nothing. Name the action or the data.
  • Missing operational actors. Support, operations, finance and auditors often depend on the system too.
  • Indirect neighbors. A system that only talks to your payment provider does not belong on your diagram.
  • No title, key or date. A diagram that cannot be read without the author in the room will be misread later.

Templates to start from

AFFiNE does not have a dedicated context diagram template yet. These free templates are the closest starting points:

Frequently asked questions

What is a context diagram?

A context diagram is a high-level diagram that shows a system as a single shape, the people and external systems that interact with it, and the information or relationships between them. It defines the system's boundary and shows nothing about how the system works inside.

Is a context diagram the same as a Level 0 DFD?

Usually. Most sources treat the context diagram as Level 0, the top of a set of data flow diagrams where the whole system is one process. A few textbooks call the first breakdown into processes Level 0 and put the context diagram above it, so check which convention your team or course uses. In the C4 model, the system context diagram plays the same role but uses boxes and person shapes and labels relationships rather than data.

What is the difference between a context diagram and a DFD Level 1?

A context diagram shows the system as one process with external entities. A Level 1 DFD opens that process up into its main sub-processes and adds data stores, while keeping the same external entities and flows.

Should a context diagram show databases?

No. Databases and other data stores are inside the system, so they belong on a Level 1 DFD or a C4 container diagram. The exception is a database owned by another team or vendor that your system reads from directly; treat it as an external system.

What is a system context diagram in the C4 model?

It is level 1 of the C4 model: one software system in the center, surrounded by its users and the other software systems it interacts with. It leaves out technologies and protocols and is meant to be readable by technical and non-technical people.

Can a system have more than one context diagram?

Each context diagram has one system in scope. If you want to show several systems and how they connect, draw a system landscape diagram instead. You can also draw a separate context diagram for each major system.

What tool can I use to draw a context diagram?

Any tool with shapes and labeled connectors works: whiteboards such as AFFiNE or Miro, diagram tools such as draw.io or Lucidchart, or diagrams-as-code tools such as Structurizr, C4-PlantUML and Mermaid.

Sources

Checked on November 14, 2026: