System Context
Template Library
System Context Template
Define the system boundary, actors, external systems, trust boundaries, operating context, and external obligations.
ES-104
Context
System Boundary
Template purpose
Use this template to define the system in context.
A system context model clarifies what is inside the system boundary, what is outside it, who interacts with it, what external systems it depends on, where trust boundaries exist, and what controls are needed at those boundaries.
Project
<Project name>
Document control
| Field |
Value |
| Artifact owner |
<owner> |
| Primary reviewers |
<reviewers> |
| Status |
<draft / in review / accepted / revised> |
| Last updated |
<YYYY-MM-DD> |
| Related Engineering Stage |
ES-104 — Architecture and Technical Approach |
| Project workspace target |
docs/project-workspace/architecture/system_context.md |
System boundary
<Describe what is inside and outside the system boundary.>
Context diagram placeholder
<Optional text diagram, Mermaid diagram, image reference, or note about where the diagram is stored.>
Actors
| Actor |
Role |
Interaction with System |
Trust / Access Concern |
<actor> |
<role> |
<interaction> |
<concern> |
External systems
| External System |
Relationship |
Data / Control Flow |
Constraint |
Owner / Contact |
<system> |
<relationship> |
<flow> |
<constraint> |
<owner> |
In-boundary responsibilities
| Responsibility |
Component or Area |
Evidence Expected Later |
<responsibility> |
<component or area> |
<evidence> |
Out-of-boundary responsibilities
| Responsibility |
External Owner |
Assumption or Constraint |
<responsibility> |
<owner> |
<assumption or constraint> |
Trust boundaries
| Boundary |
Description |
Risk |
Control |
<boundary> |
<description> |
<risk> |
<control> |
Data boundaries
| Boundary |
Data Involved |
Protection / Control |
<boundary> |
<data> |
<control> |
AI boundaries
Use this section if AI is part of the system or adjacent to the system.
| Boundary |
AI Role |
Human Control |
Evidence Required |
<boundary> |
<AI role or not applicable> |
<review, approval, override, escalation> |
<evidence> |
Operational context
| Area |
Context |
| Users / environment |
<context> |
| Support model |
<context> |
| Monitoring expectations |
<context> |
| Escalation expectations |
<context> |
| Release or deployment context |
<context> |
Context notes
Review checklist
- [ ] System boundary is clear.
- [ ] Actors are identified.
- [ ] External systems are identified.
- [ ] In-boundary and out-of-boundary responsibilities are distinguished.
- [ ] Trust boundaries are identified.
- [ ] Data and AI boundaries are considered.
- [ ] Operational context is visible.
- [ ] Context questions are recorded.
Continue to Component Model
Define major components, responsibilities, interfaces, and non-responsibilities.
Open Component Model →