nerdexam
IIBA

CBAP · Question #265

You are the business analyst for THY Organization and you have gathered the requirements. You have presented the requirements to the stakeholders and they have approved your requirements. You are…

The correct answer is A. To help determine the sequence in which requirements are to be addressed. Recording dependencies and relationships between requirements allows a business analyst to understand which requirements depend on others, directly informing the order in which they must be addressed.

Requirements Life Cycle Management

Question

You are the business analyst for THY Organization and you have gathered the requirements. You have presented the requirements to the stakeholders and they have approved your requirements. You are now working with Francie on recording the dependencies and relationships for each of the requirements. Why would you want to record the dependencies and relationships for the requirements?

Options

  • ATo help determine the sequence in which requirements are to be addressed.
  • BTo help determine which requirements carry the most risk.
  • CTo help determine the total cost for the solution to be implemented.
  • DTo help determine the total time for the solution to be implemented.

How the community answered

(22 responses)
  • A
    73% (16)
  • B
    9% (2)
  • C
    5% (1)
  • D
    14% (3)

Why each option

Recording dependencies and relationships between requirements allows a business analyst to understand which requirements depend on others, directly informing the order in which they must be addressed.

ATo help determine the sequence in which requirements are to be addressed.Correct

Dependencies between requirements reveal prerequisite relationships - some requirements cannot be implemented until others are complete. Recording these relationships enables the team to sequence work in a logical, technically feasible order and avoid blockers during implementation.

BTo help determine which requirements carry the most risk.

Risk identification uses techniques such as risk matrices, brainstorming, or SWOT analysis, not dependency mapping between requirements.

CTo help determine the total cost for the solution to be implemented.

Total cost estimation is derived from scope definition, resource planning, and estimation techniques like analogous or parametric estimating, not from requirement relationship recording.

DTo help determine the total time for the solution to be implemented.

Total time estimation uses scheduling tools such as WBS decomposition and critical path analysis, not the recording of requirement dependencies alone.

Concept tested: Requirements dependency and relationship traceability

Source: https://www.iiba.org/standards-and-resources/babok/

Topics

#requirements dependencies#requirements relationships#requirements traceability#requirements organization

Community Discussion

No community discussion yet for this question.

Full CBAP Practice