A context diagram shows a system, its environment, and the interactions across its boundary.
The system appears as one central element. Meanwhile, external actors, devices, and neighboring systems surround it. Arrows show the exchange of data, messages, or signals.
The diagram defines the system boundary and clarifies the project scope. Therefore, stakeholders can identify what belongs to the system and what remains external. Moreover, they can recognize important interfaces and responsibilities.
For example, a banking diagram may show a customer, an application portal, and external banking systems. The arrows may represent application data, verification results, and account information.
The model stays at a high level. It does not show internal processes or technical details. However, it may use data flow notation, SysML, UML, or another suitable format.
Teams should label every external element and interaction clearly. In addition, they should update the model when the scope or environment changes.
A clear context diagram supports scope definition, interface analysis, requirements elicitation, and stakeholder communication.
« Back to Glossary Index