System context
Show who talks to whom so the trust boundary is visible.
Related: Reference architecture
When to use
Use as the first architecture slide. Do not use for internal module graphs (that is reference architecture). Do not use consulting tables of integrations.
Guidelines
A handful of named actors and one sentence about the boundary. Generic boxes only.
Example
Harbor context
Partners never talk to the warehouse DB; they talk to Harbor API.
Partner portal
Harbor API
Harbor app
Warehouse DB
Trust boundary: API is the only partner entry
Partner → API → app → DB. Steal the boundary sentence, not a logo orchard.
Rules
- Family is Cloud architecture.
- Every box has a human-readable name. No vendor logos.
- The title states the boundary or the forbidden path.
- Five or fewer actors on this slide.
- No unlabeled arrows.
User recipe
Pick family: Cloud architecture first.
Insert objects:
- Text: title stating the boundary or forbidden path, kicker, source line
- Panel (optional): for trust-boundary grouping
- Junction: for each actor or system
- Connector: arrows showing relationships
Assemble:
- Five or fewer junctions
- Label every junction with a human-readable name
- No vendor logos
- Every connector must be clear (labeled or obviously showing relationship)
Anti-patterns
- Internal queues on the context slide.
- AWS/Azure product icons.