CAPM Business Analysis Frameworks Practice Question
Which THREE of the following are techniques commonly used in business analysis frameworks to elicit requirements?
⚠ Common exam trap
It's easy for candidates to confuse strategic analysis tools (like SWOT) or project scheduling tools (like critical path method) with requirements elicitation techniques, which are specifically designed to gather information from stakeholders.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Prototyping
Prototyping (A) is a recognized elicitation technique in business analysis frameworks such as the IIBA BABOK, where a mock-up or working model is shown to stakeholders to draw out and refine requirements that are hard to articulate in the abstract. Interviews (B) are a core elicitation method in which the analyst asks stakeholders structured or unstructured questions to uncover needs, expectations, and constraints directly. Document analysis (E), also called document review, is an elicitation technique that examines existing business documents, policies, system specs, and reports to derive requirements and identify gaps. SWOT analysis (C) is a strategic planning tool for assessing strengths, weaknesses, opportunities, and threats, not a requirements elicitation technique. The critical path method (D) is a project scheduling technique used to determine the longest sequence of dependent tasks and float, so it does not elicit requirements.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Prototyping
Why this is correct
Prototyping builds a partial working model so stakeholders react to something concrete rather than abstract descriptions, surfacing requirements they cannot articulate verbally. This iterative feedback loop is a recognised elicitation technique in business analysis frameworks such as BABOK.
- ✓
Interviews
Why this is correct
Interviews are structured conversations with individual stakeholders that probe needs, expectations and constraints in depth. Their direct, two-way format lets the analyst clarify ambiguity immediately, making them a core elicitation technique in business analysis frameworks.
- ✗
SWOT analysis
Why it's wrong here
SWOT analysis assesses internal strengths and weaknesses against external opportunities and threats; it is a strategic planning tool, not a requirements elicitation technique. It tempts because it is a familiar business analysis artefact, but elicitation draws requirements from stakeholders via interviews, workshops and observation.
- ✗
Critical path method
Why it's wrong here
Critical path method schedules project activities and calculates float; it elicits no requirements. It tempts because it is a recognised project management technique, but business analysis elicitation uses interviews, workshops, observation and document analysis instead.
- ✓
Document analysis
Why this is correct
Document analysis examines existing artefacts — policies, procedures, contracts, system specifications — to extract requirements already implied or mandated. It reveals constraints stakeholders may overlook, making it a standard elicitation technique in business analysis frameworks.
Go deeper
Related to this question
About these practice questions
This CAPM question is part of Courseiva's 451-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This CAPM practice question is part of Courseiva's free PMI certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the CAPM exam.