A context model shows a system, its environment, and the interactions between them.
It includes external users, devices, organizations, processes, and neighboring systems. Moreover, it shows the data, messages, or signals that cross the system boundary.
Teams use the model early in requirements engineering. First, they define the system boundary. Next, they identify relevant actors and external systems. Then, they document inputs, outputs, and interfaces. Therefore, they can find important sources of requirements.
Different notations can represent this information. For example, data flow diagrams emphasize information flows. In contrast, use case diagrams emphasize actors and system services. SysML diagrams can also support complex technical systems.
A context model does not describe internal system details. Instead, it focuses on the environment and external relationships. As a result, it supports scope definition, interface analysis, and stakeholder communication.
Clear context models reveal missing interfaces, unclear responsibilities, and relevant environmental influences.
« Back to Glossary Index