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

Scope modeling makes the solution boundary explicit and visual. Context diagrams show system interfaces; feature lists enumerate included capabilities; scope statements define exclusions. Visual scope models enable stakeholders to see and agree on scope more effectively than textual descriptions alone.

**Why not A:** Scope modeling defines the boundaries and features of what a project will deliver, not the financial aspects of a project. Financial modeling involves cost estimation, budgeting, and return-on-investment analysis, which are separate disciplines from defining and visualizing the scope of deliverables.

**Why not B:** While scope feeds into scheduling, scope modeling itself does not involve sequencing or timing activities. Scheduling scope activities is a project management planning function that occurs after the scope has been defined. Scope modeling focuses on what will be delivered, not when or in what order.

**Why not C:** Creating 3D product models is a physical design or engineering activity, not a business analysis technique. Scope modeling uses diagrams like context diagrams, feature trees, or scope matrices to define project boundaries. Confusing it with physical prototyping or CAD modeling conflates BA deliverables with engineering outputs.