HKSM
Context Diagrams
A high-level diagram that defines product scope by showing a business system (e.g., a process, device, or software) and how external people and other systems (actors) interact with it.
Key Points
- Depicts the system boundary and the external actors that interact with the system.
- Shows inputs and outputs or interfaces across the boundary; internal details are not included.
- Used early to confirm scope, requirements, and stakeholder expectations on a single page.
- Helps identify integration points, dependencies, and potential interface risks.
Example
For an online ordering system, a context diagram would place the ordering application at the center and show external actors such as Customer, Payment Gateway, Warehouse System, Shipping Carrier, and Customer Support. Arrows would indicate information flows like order requests, payment authorization, inventory checks, and shipment updates.
PMP Example Question
A project manager needs a single-page artifact to clarify the scope boundary of a new claims processing application and show how customers, partner systems, and regulators connect to it. Which tool should the PM use?
- Context diagram
- Work breakdown structure (WBS)
- Project schedule network diagram
- RACI matrix
Correct Answer: A — Context diagram
Explanation: A context diagram illustrates the system boundary and interactions with external actors, which is exactly what is needed here.
