CAPM domain - 27% of the exam

Business Analysis Frameworks

Business Analysis Frameworks is 27% of the CAPM exam. These are the objectives it covers, each with practice questions, with every answer explained.

The domain in numbers

81
Practice questions
4
Objectives
81
Medium

Where people go wrong

  • Reversing verification and validation

    The wrong answers swap verification and validation, or treat a clean test result as proof the work succeeded. Verification confirms the solution was built to its specification: functions behave as written and tests pass. Validation confirms the solution meets the business need and delivers the intended value. A feature can pass verification and still fail validation, as when users report that a screen matching its design does not fit their work. Passing one never substitutes for the other.

    See it in a sample question
  • Filing one-off cutover needs as ongoing requirements

    Data migration, staff training and retiring the old system get filed as stakeholder, functional, solution or business requirements. Each wrong option points to an ongoing need or goal. A transition requirement is different: it describes a temporary capability needed only to move from the current state to the future state, and it falls away once the new system is live. Ongoing capabilities and qualities of the running solution belong to the other types.

    See it in a sample question
  • Choosing a solution before defining the need

    The wrong answers jump to a solution: writing solution requirements or a functional specification, selecting a vendor, or building a schedule before the problem is defined. Each of these assumes a solution has already been justified. A needs assessment comes first. It analyses the current situation and the underlying causes, and defines the business need as a problem or opportunity linked to organisational goals, so that later choices rest on a real gap.

    See it in a sample question
  • Reading traceability in the wrong direction

    The wrong options name forward, horizontal or bidirectional tracing when the task runs upstream to a source. Forward traceability runs from a need or requirement toward downstream design, build and test artefacts, so it confirms coverage but does not answer why something exists. Backward traceability starts from a requirement or a delivered feature and follows it back to the originating business need. Horizontal tracing relates items at the same level, and bidirectional adds a forward path that a single backward lookup never uses.

    See it in a sample question
  • Swapping stakeholder analysis techniques

    The wrong answers treat distinct stakeholder tools as interchangeable. A power/interest grid plots stakeholders by authority and interest to set engagement effort. A RACI matrix assigns responsible, accountable, consulted and informed roles to activities, so it does not position people by influence. The salience model adds legitimacy and urgency to power, which suits stakeholders whose importance shifts. Cost-benefit analysis and a work breakdown structure do not classify stakeholders at all.

    See it in a sample question

Objectives in this domain

Sample questions from this domain

Free sampleBusiness Analysis Frameworksmedium

On the Fenwick portal project, testers confirm every function behaves exactly as the technical specification describes, and no defects remain against those documented requirements. At user acceptance, however, several stakeholders say the working solution does not actually support how they process orders day to day. What has most likely happened?

  • AThe solution passed validation but failed verification, because it did not conform to its written specification
  • BThe solution was rejected only because acceptance criteria were never written for any of its features
  • CThe solution passed both validation and verification, so the stakeholder objections fall outside evaluation
  • DThe solution passed verification but failed validation, because it does not meet the real business need in use Correct
A solution can meet its specification, passing verification, yet fail to meet the business need, failing validation. Verification confirms the solution was built to specification, which the testing established. Validation confirms it meets the business need in real use, which the stakeholder feedback shows it did not. Passing one does not guarantee the other, which is why both are performed.

Why A is wrong: This reverses the terms: conforming to the written specification is exactly what verification confirmed, so the solution passed verification, making this description inconsistent with the facts.

Why B is wrong: Missing acceptance criteria can cause disputes, but the scenario says testing was thorough against documented requirements, so the gap is a validation shortfall against the real need, not simply absent criteria.

Why C is wrong: It is tempting to treat clean testing as full success, but stakeholders reporting the solution does not fit their work is a validation failure, so it cannot have passed validation.

Why D is correct: Conforming to the specification is verification, which passed, while failing to support the stakeholders' actual work is a validation failure, which is the precise pattern the scenario describes.

Free sampleBusiness Analysis Frameworksmedium

On the Summit HR upgrade, the business analyst has elicited this requirement: "Existing employee records must be migrated from the old system into the new system before go-live." The analyst is classifying the requirement so the team plans it correctly. Which requirement type does this statement represent?

  • AA stakeholder requirement, because it states a need of the HR team that will use the new system day to day
  • BA business requirement, because it expresses the organisation's overall reason for replacing the HR system
  • CA transition requirement, because it defines a capability needed only to move from the old system to the new one Correct
  • DA non-functional requirement, because it constrains how well the new system must handle the employee data
A one-time capability needed only to move from the old solution to the new one, such as data migration, is a transition requirement. Transition requirements describe temporary capabilities needed only during the move to the new solution, such as data migration or user training, and they cease to apply once cutover is complete, which distinguishes them from ongoing solution, stakeholder, and business requirements.

Why A is wrong: Stakeholder requirements express what a particular group needs from the solution in ongoing use, but a one-off data migration performed before go-live is a temporary changeover need, not an ongoing HR-team requirement.

Why B is wrong: Business requirements state the higher-level goal, such as improving HR efficiency, whereas migrating records is a specific capability needed only to move to the new system, so it sits well below the business-goal level.

Why C is correct: A one-time need such as migrating records that exists solely to move from the old solution to the new one, and is no longer needed after cutover, is by definition a transition requirement.

Why D is wrong: Non-functional requirements constrain qualities such as performance or security of the ongoing solution, but migrating records is a temporary changeover activity rather than a quality constraint on the running system.

Free sampleBusiness Analysis Frameworksmedium

During the Northwind billing-portal initiative, a sponsor asks the business analyst to begin the needs assessment. The team is eager to start listing features for a new self-service payment screen. What should the needs assessment establish first?

  • AThe detailed functional specification for the self-service payment screen the team wants to build
  • BThe vendor short-list and pricing for the payment platform that will host the new screen
  • CThe project schedule and milestone dates for delivering the self-service payment screen
  • DThe underlying business need and the problem or opportunity driving the request, tied to organisational goals Correct
A needs assessment first defines the underlying business need and its link to organisational goals, not a solution. The needs assessment exists to understand the current state and articulate the business need behind a request, so that any later solution can be traced back to a real problem or opportunity aligned with strategy rather than a pre-chosen feature.

Why A is wrong: Tempting because the team is keen to design features, but a functional specification is a solution-level output produced much later; the needs assessment precedes any decision about what to build.

Why B is wrong: Procurement and vendor selection are solution-delivery activities that depend on an approved need and business case, so choosing vendors before the underlying problem is defined puts the cart before the horse.

Why C is wrong: Scheduling is a planning activity that assumes a solution has already been justified; producing dates before the need is understood commits the project to a solution that may not address the real problem.

Why D is correct: Correct: a needs assessment defines the business need by analysing the current state, the problem or opportunity, and its link to organisational goals before any solution is proposed.

Free sampleBusiness Analysis Frameworksmedium

During a review on the Meridian onboarding project, a business analyst wants to confirm that each requirement in the traceability matrix can be justified by a documented business need or objective, so that no requirement exists without a valid reason. Which form of traceability is the analyst applying?

  • AForward traceability, linking each requirement ahead to the design, build, and test artefacts that satisfy it
  • BHorizontal traceability, linking each requirement to peer requirements at the same level of detail
  • CValue traceability, ranking each requirement by the financial benefit it is expected to return
  • DBackward traceability, linking each requirement back to its originating business need or objective Correct
Distinguish backward traceability, which links a requirement to its origin, from forward traceability, which links it to deliverables. Confirming that a requirement traces to a documented business need means following it upstream to its source, which is the definition of backward traceability; forward traceability instead follows requirements downstream to the artefacts that implement them.

Why A is wrong: Forward traceability is a real direction, but it maps requirements to downstream deliverables rather than back to the originating need the analyst is checking.

Why B is wrong: This describes relationships among requirements of similar type; it sounds plausible but does not connect a requirement to its originating business objective.

Why C is wrong: Prioritising by benefit is a legitimate activity, but it is not a recognised traceability direction and does not verify that a requirement has a documented source.

Why D is correct: Backward traceability follows a requirement to its source, which is exactly how the analyst confirms every requirement is justified by a documented need.

Free sampleBusiness Analysis Frameworksmedium

Early in the Beacon patient-records project, the business analyst lists everyone who could affect or be affected by the work and wants to plot each stakeholder by how much authority they hold and how interested they are, so engagement effort can be targeted. Which stakeholder analysis technique fits this purpose?

  • AA responsibility assignment matrix that maps each activity to who is responsible, accountable, consulted, and informed
  • BA work breakdown structure that decomposes the project scope into progressively smaller deliverables
  • CA power and interest grid that positions each stakeholder by their level of authority and their level of interest Correct
  • DA cost-benefit analysis that compares the expected financial return against the expected expenditure
A power and interest grid classifies stakeholders by authority and interest to target engagement effort. Grouping stakeholders by their authority and their interest lets the analyst tailor how closely each is managed, which is why the power and interest grid is the technique suited to targeting engagement rather than a role or scope tool.

Why A is wrong: A RACI matrix is a real stakeholder technique, but it assigns roles to tasks rather than positioning stakeholders by authority and interest, so it does not answer how much attention each stakeholder needs.

Why B is wrong: A work breakdown structure organises deliverables and scope, not people, so it offers nothing about a stakeholder's authority or interest and is the wrong tool for this analysis.

Why C is correct: Correct: a power and interest grid plots stakeholders on authority against interest, which is exactly how the analyst decides where to focus engagement effort.

Why D is wrong: Cost-benefit analysis supports the funding decision by weighing money, not by classifying stakeholders, so it cannot guide who to engage and how closely.

Other domains in this exam

See also the CAPM cert hub, the study guide, and the cheat sheet.

Examworthy is not affiliated with or endorsed by PMI. Original, blueprint-aligned practice material only.