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

As-is analysis documents the current state — existing processes, systems, and pain points. To-be analysis defines the desired future state. The gap between them defines what the project must deliver to transform the business.

**Why not A:** Referring to current software versions versus planned upgrades describes software version management, not as-is and to-be analysis. As-is and to-be analysis examines business processes and their desired transformations, not software release versions.

**Why not B:** Describing completed versus pending requirements confuses documentation status tracking with process state analysis. As-is and to-be analysis models the current and future states of business processes, not the completion status of requirements in a tracking system.

**Why not D:** Describing what competitors offer versus our future product is competitive analysis or market positioning, not as-is and to-be analysis. As-is and to-be analysis focuses on the organization's own processes, documenting their current state and designing the desired future state after solution implementation.