Scribd
Upload
572 views

Context Diagram PDF

A System Context Diagram (SCD) is a high-level diagram used in systems design that shows a system surrounded by external entities or actors that interact with the system through inputs and outputs. An SCD focuses on the external factors to help define system requirements and constraints. It represents the system as a single process and shows the relationship between the system and external entities like other systems, organizations, or data stores. An SCD is also known as a Context-Level Data Flow Diagram or Level-0 Data Flow Diagram.

Uploaded by

Vpn
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
572 views

Context Diagram PDF

A System Context Diagram (SCD) is a high-level diagram used in systems design that shows a system surrounded by external entities or actors that interact with the system through inputs and outputs. An SCD focuses on the external factors to help define system requirements and constraints. It represents the system as a single process and shows the relationship between the system and external entities like other systems, organizations, or data stores. An SCD is also known as a Context-Level Data Flow Diagram or Level-0 Data Flow Diagram.

Uploaded by

Vpn
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

A System Context Diagram (SCD) in software engineering and systems engineering is a diagram that

represents the actors outside a system that could interact with that system. This diagram is the highest 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. A System Context Diagram (SCD) in software engineering and
systems engineering is a diagram that represents the actors outside a system that could interact with that system.
This diagram is the highest 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.

System Context Diagrams are diagrams used in systems design to represent the more important external factors
that interact with the system at hand. This type of diagram according to Kossiakoff (2003) usually "pictures the
system at the center, with no details of its interior structure, surrounded by all its interacting systems,
environment and activities. The objective of a system context diagram is to focus attention on external factors
and events that should be considered in developing a complete set of system requirements and constraints"

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
(Examples:, 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").

The Context Diagram shows the system under consideration as a single high-level process and then shows the
relationship that the system has with other external entities (systems, organizational groups, external data stores,
etc.).

Another name for a Context Diagram is a Context-Level Data-Flow Diagram or a Level-0 Data Flow Diagram.
Since a Context Diagram is a specialized version of Data-Flow Diagram, understanding a bit about Data-Flow
Diagrams can be helpful.
A Data-Flow Diagram (DFD) is a graphical visualization of the movement of data through an information
system. DFDs are one of the three essential components of the structured-systems analysis and design method
(SSADM). A DFD is process centric and depicts 4 main components.

• Processes (circle)
• External Entities (rectangle)
• Data Stores (two horizontal, parallel lines or sometimes and ellipse)
• Data Flows (curved or straight line with arrowhead indicating flow direction)

Each DFD may show a number of processes with data flowing into and out of each process. If there is a need to
show more detail within a particular process, the process is decomposed into a number of smaller processes in a
lower level DFD. In this way, the Content Diagram or Context-Level DFD is labeled a “Level-0 DFD” while
the next level of decomposition is labeled a “Level-1 DFD”, the next is labeled a “Level-2 DFD”, and so on.

Context Diagrams and Data-Flow Diagrams were created for systems analysis and design. But like many
analysis tools they have been leveraged for other purposes. For example, they can also be leveraged to capture
and communicate the interactions and flow of data between business processes. So, they don’t have to be
restricted to systems analysis.

A sample Context Diagram is shown here.

A Context Diagram (and a DFD for that matter) provides no information about the timing, sequencing, or
synchronization of processes such as which processes occur in sequence or in parallel. Therefore it should not
be confused with a flowchart or process flow which can show these things.

Some of the benefits of a Context Diagram are:

• Shows the scope and boundaries of a system at a glance including the other systems that interface with it
• No technical knowledge is assumed or required to understand the diagram
• Easy to draw and amend due to its limited notation
• Easy to expand by adding different levels of DFDs
• Can benefit a wide audience including stakeholders, business analyst, data analysts, developers

You might also like