Editing System context diagram (section)

== Overview == 
System context diagrams show a system, as a whole and its [[Input/output|input]]s and [[Output (computing)|output]]s from/to external factors. According to Kossiakoff and Sweet (2011):<ref name="KoSw03">Alexander Kossiakoff, William N. Sweet (2011). ''Systems Engineering: Principles and Practices'' p. 266</ref> 
{{Quote|System Context Diagrams&nbsp;... represent all external entities that may interact with a system&nbsp;... Such a diagram pictures the system at the center, with no details of its interior structure, surrounded by all its interacting systems, environments and activities. The objective of the system context diagram is to focus attention on external factors and events that should be considered in developing a complete set of systems requirements and constraints.}}

System context diagrams are used early in a project to get agreement on the scope under investigation.<ref>Richard Wiener (1998) ''Journal of Object-oriented Programming''. Vol 11. p. 68</ref> Context diagrams are typically included in a requirements document. These diagrams must be read by all project stakeholders and thus should be written in plain language, so the stakeholders can understand items within the document.