Jump to content

System context diagram

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by Nickmd1 (talk | contribs) at 12:26, 2 August 2013 (Clarified the definition to state that the diagram defines the boundary between the system and it's environment and the things that interact with it. Removed 'Actors' and stated that it is 'a' high-level view and not 'the' high level view). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Example of a System context diagram.[1]

A System Context Diagram (SCD) in software engineering and systems engineering is a diagram that defines the boundary between the system[2] (or part of a system) and its environment, showing the entities that interact with it. This diagram is a high level view of a system. It is similar to a Block diagram. SCDs show a system, often software-based, as a whole and its inputs and outputs from/to external factors.

Overview

System Context Diagrams are used early in a project to get agreement on the scope under investigation. 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.

Building blocks

Context diagrams can be developed with the use of two types of building blocks:

  • Entities (Actors): labeled boxes; one in the center representing the system, and around it multiple boxes for each external actor
  • Relationships: labeled lines between the entities and system

For example, "customer places order." Context diagrams can also use many different drawing types to represent external entities. They can use ovals, stick figures, pictures, clip art or any other representation to convey meaning. Decision trees and data storage are represented in system flow diagrams.

A context diagram can also list the classifications of the external entities as one of a set of simple categories[3] (Examples:[4]), which add clarity to the level of involvement of the entity with regards to the system. These categories include:

  • Active: Dynamic external entities which frequently initiate events to achieve some goal or purpose (Examples: "Article readers" or "customers").
  • Passive: Static external entities which infrequently interact with the system (Examples: "Article editors" or "database administrator").
  • Cooperative: Predictable external entities which are used by the system to bring about some desired outcome (Examples: "Internet service providers" or "shipping companies").
  • Autonomous (Independent): External entities which are separated from the system, but affect the system indirectly, by means of imposed constraints or similar influences (Examples: "regulatory committees" or "standards groups").

Alternatives

The best System Context Diagrams are used to display how system inter operates 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 system or systems and systems. Alternatives of the system context diagram are:

Example of an Architecture Interconnect Diagram.[5]
  • 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.
  • 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.
  • 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".[6]
  • 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.[5]
  • Problem Diagrams (Problem Frames): In addition to the kinds of things shown on a context diagram, a problem diagram shows requirements and requirements references.

Diagrams like these 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.[5]

See also

Wikimedia Commons has media related to Context diagrams.

References

  1. ^ NDE Project Management (NPOESS) Data Exploitation web site. 2008.
  2. ^ Alexander Kossiakoff, William N. Sweet (2003). Systems Engineering: Principles and Practices p. 413.
  3. ^ http://books.google.com/books?id=SN4WegDHVCcC&lpg=PT104&ots=aunyBGRdhz&dq=modeling%20adjacent%20entities%20requirements&pg=PA1#v=onepage&q&f=false
  4. ^ http://www.city.ac.uk/__data/assets/pdf_file/0006/81429/RESCUE_i_SD_tutorial.pdf
  5. ^ a b c US Department of Transportation, Office of Operations (2006)Regional ITS Architecture Guidance Document. July 2006
  6. ^ Graeme C. Simsion, Graham C. Witt (2005). Data Modeling Essentials. p. 512.
Retrieved from "https://en.wikipedia.org/enwiki/w/index.php?title=System_context_diagram&oldid=566847436"