Context includes the external conditions, people, systems, and information that influence a system and its requirements.
In requirements engineering, the system context defines the relevant part of the environment. It includes users, external systems, devices, business processes, laws, and operational conditions.
First, teams define the system boundary. Next, they identify external actors and interfaces. Moreover, they document the data, messages, and events that cross the boundary. Therefore, stakeholders can distinguish system responsibilities from external responsibilities.
A context diagram can present this information visually. For example, it can show the system, its actors, neighboring systems, and their interactions.
Teams should review the defined scope regularly. New stakeholders, interfaces, or environmental conditions may appear during development. Consequently, teams must update the documentation when the environment changes.
A clear system context supports accurate requirements, precise interfaces, and a shared understanding of project scope.
« Back to Glossary Index