CAPM Practice: Demonstrate an understanding of business analysis (BA) roles and responsibilities

A context diagram or use case diagram shows the system boundary and the external entities (users, systems, organizations) that interact with it. This helps define scope and ensures all integration points are captured in requirements.

**Why not A:** A work breakdown structure decomposes project deliverables into work packages for planning and scheduling. It does not visualize the external actors and systems that interact with the system boundary, which is what context and use case diagrams do.

**Why not B:** A stakeholder register lists stakeholder information, roles, and engagement strategies. While it identifies people involved, it does not visually depict how people and systems interact with the system under development or show the system boundary.

**Why not C:** A risk register documents identified risks, their probability, impact, and response strategies. It is a risk management tool, not a visualization of system interactions and external entities that interface with the solution.