Learn system context diagram vocabulary: system boundary, external actors, data flows, integration points, scope — the language for reading and presenting C4-level context diagrams in technical discussions.
0 / 5 completed
1 / 5
The architect points to the diagram and says: 'Everything inside this rectangle is within the system boundary.' What does 'system boundary' mean?
The system boundary is the conceptual line that defines what is 'inside' the system under discussion and what is 'outside'. In a C4 context diagram (Level 1), the system boundary separates your system from external actors (users, third-party services, other systems). It is fundamental for defining scope and responsibilities.
2 / 5
During a diagram walkthrough, the engineer says: 'The external actors are the mobile app, the payment gateway, and the accounting system.' What is an 'external actor' in a system context diagram?
An external actor (also called an external entity or user) is anything outside the system boundary that sends data to or receives data from the system. External actors include human users, external APIs, third-party services, and other internal systems outside the scope of the diagram. They help define what the system must interface with.
3 / 5
The architect says: 'This is out of scope for our system — it belongs to the payment provider.' What does 'out of scope' mean in this context?
'Out of scope' means the functionality or concern is outside the system boundary — it belongs to an external actor or system. This is an important phrase in architecture discussions because it clarifies ownership and prevents teams from building functionality that is the responsibility of another system.
4 / 5
A colleague says: 'Let's draw the data flows between our system and the external actors.' What do 'data flows' show in a system context diagram?
Data flows in a system context diagram show what information moves between the system and its external actors, and in which direction. For example, 'user sends login credentials → system returns authentication token'. Data flows help stakeholders understand the system's inputs, outputs, and dependencies at a high level.
5 / 5
The architect explains: 'The integration points are the payment API, the SMS gateway, and the identity provider.' What is an 'integration point'?
An integration point is a specific connection where your system interfaces with an external system or service. Identifying integration points is critical in architecture work because each one represents a dependency, a potential failure mode, and a contract to maintain. Integration points appear as edges (lines) between your system and external actors in context diagrams.