Editing System context diagram (section)

== Alternatives ==
The best system context diagrams are used to display how a system interoperates at a very high level, or how systems operate and interact logically. The system context diagram is a necessary tool in developing a baseline interaction between systems and actors; actors and a system or systems and systems. Alternatives to the system context diagram are:

[[File:Greater Yellowstone Rural ITS Architecture Interconnect Diagram.jpg|thumb|360px|Example of an Architecture Interconnect Diagram.<ref name="USDT06"/>]]
* ''Architecture Interconnect Diagram'': The figure gives an example of an Architecture Interconnect Diagram: A representation of the Albuquerque regional ITS architecture interconnects for the Albuquerque Police Department that was generated using the Turbo Architecture tool is shown in the figure. Each block represents an ITS inventory element, including the name of the stakeholder in the top shaded portion. The interconnect lines between elements are solid or dashed, indicating existing or planned connections.<ref name="USDT06"/>
* ''[[Business Model Canvas]]'', a strategic management template for developing new or documenting existing business models. It is a visual chart with elements describing a firm's value proposition, infrastructure, customers, and finances.[1] It assists firms in aligning their activities by illustrating potential trade-offs.
* ''[[Enterprise data model]]'': this type of [[data model]] according to Simsion (2005) can contain up to 50 to 200 entity classes, which results from specific "high level of generalization in [[data modeling]]".<ref>[[Graeme Simsion|Graeme C. Simsion]], Graham C. Witt (2005). ''Data Modeling Essentials''. p. 512.</ref>
* ''IDEF0 Top Level Context Diagram'': The [[IDEF0]] process starts with the identification of the prime function to be decomposed. This function is identified on a "Top Level Context Diagram" that defines the scope of the particular IDEF0 analysis.
* ''[[Problem Frames Approach#Problem diagrams|Problem Diagrams (Problem Frames)]]'': In addition to the kinds of things shown on a context diagram, a problem diagram shows requirements and requirements references.
* ''[[Use case diagram]]'': One of the [[Unified Modeling Language]] diagrams. They also represent the scope of the project at a similar level of abstraction. - Use Cases, however, tend to focus more on the goals of 'actors' who interact with the system, and do not specify any solution. Use Case diagrams represent a set of Use Cases, which are textual descriptions of how an actor achieves the goal of a use case. for Example Customer Places Order.
* ''[[ArchiMate]]'': ArchiMate is an open and independent enterprise architecture modeling language to support the description, analysis and visualization of architecture within and across business domains in an unambiguous way.

Most of these diagrams work well as long as a limited number of interconnects will be shown. Where twenty or more interconnects must be displayed, the diagrams become quite complex and can be difficult to read.<ref name="USDT06">US Department of Transportation, Office of Operations (2006)[https://ops.fhwa.dot.gov/publications/regitsarchguide/5defineint.htm Regional ITS Architecture Guidance Document]. July 2006</ref>