Business Analysis Flashcards
7 cards from real CAPM practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.
Read the first 7 Business Analysis flashcards as text
A business analyst is asked to identify and document the needs of stakeholders before a solution is defined. This activity is best described as:
Answer: Requirements elicitation
Requirements elicitation is the process of identifying and documenting stakeholder needs prior to defining a solution.
Which technique involves asking stakeholders to sort requirements into categories such as 'must have,' 'should have,' 'could have,' and 'won't have'?
Answer: MoSCoW prioritization
MoSCoW prioritization uses Must, Should, Could, and Won't categories to rank requirements by importance.
A project sponsor wants to understand the financial return of a proposed project relative to its cost. Which business analysis output best addresses this?
Answer: Cost-benefit analysis
A cost-benefit analysis compares the expected costs of a project against the projected financial benefits.
During business analysis, a model that shows the flow of data between processes, data stores, and external entities is called a:
Answer: Data flow diagram
A data flow diagram (DFD) visually depicts how data moves through a system between processes and external entities.
Which of the following best defines a 'business requirement'?
Answer: A high-level statement of the business need or goal
Business requirements are high-level statements describing why a project is needed and what business goal it must achieve.
A team is using prototyping during elicitation. What is the primary benefit of this technique?
Answer: It allows stakeholders to provide feedback on a tangible model early
Prototyping lets stakeholders interact with a working model early, which surfaces needs and issues before full development.
When a business analyst documents what a system must do—describing system behavior without specifying how—these are called:
Answer: Functional requirements
Functional requirements define the specific behaviors or functions a system must perform without prescribing implementation.