Exam CBAP All QuestionsBrowse all questions from this exam
Go to Exam
Question 254

A large company has thousands of geographically dispersed employees and dozens of IT systems. Multiple business analysts (BAs) work in parallel on various requirements with different stakeholders. When considered in isolation, the requirements look meaningful and valuable to those who approved them. However, when it comes to implementation, some of the requirements appear to be contradicting each other. A lead BA recognizes that adding some traceability information would help uncover such conflicts early in the process.

To what should the BA trace the requirements?

    Correct Answer: B

    To uncover conflicts between requirements early in the process, the Business Analyst should trace the requirements back to the business needs. This ensures that all requirements are aligned with the overarching goals and objectives of the organization. Tracing requirements to business needs helps identify contradictions and inconsistencies before moving forward to design and implementation, thereby preventing potential issues down the line.

Discussion
OlivierPaudexOption: B

Answer B (Business Needs) The requirements should first be traced (linked) to the business needs (BABOK 5.1.2). Specially if there are thousand of different companies.

[Removed]Option: D

On further analysis D seems to be correct

[Removed]Option: B

Tracing the requirements back to the business needs ensures that the proposed solutions are aligned with the goals. By doing so, conflicts and contradictions between different requirements can be identified early on. Tracing requirements to solution components means focusing on the technical aspects of how a solution will be built.

SRK2023Option: B

There are conflicting requirements (there is no mention of any solution components even built or designed yet) and if traced back to business needs, the conflicts can be discovered early on. The statement '...early in the process' also gives us a clue that this is referring to Business needs (first thing defined in the requirements process) as Solution Components come in the picture much later. I believe B is the most befitting answer to the question.

AtzewineOption: D

Traceability is used to help ensure that the solution conforms to requirements... page 79 Babok v3. Requirements: may be traced to other requirements (including goals, objectives, business requirements, stakeholder requirements, solution requirements, and transition requirements), solution components, visuals, business rules, and other work products. • Designs: may be traced to other requirements, solution components, and other work products. page 80

Atzewine

In traceability, you have two type of relationship. --Between requirements (Derive and depends) --Between requirements and work product (Satisfy and validate).

SVK2310Option: D

Ans:D- Inputs to Trace Requirements , page 80 on BABOK V.3

Dillon91Option: B

Answer is B: requirements traceability: The ability for tracking the relationships between sets of requirements and designs from the original stakeholder need to the actual implemented solution. Traceability supports change control by ensuring that the source of a requirement or design can be identified and other related requirements and designs potentially affected by a change are known

timojeagaOption: D

ANS IS D: - Traceability is the ability to look at a requirement and others to which it is related, linking business requirements to stakeholder and solution requirements, to artifacts and to solution components.

ccie_cbapOption: D

ANS: D • Requirements (traced): have clearly defined relationships to other requirements, solution components, or releases, phases, or iterations, within a solution scope, such that coverage and the effects of change are clearly identifiable.

rupakarthik

Pg-83. Requirements traced

RabbitsfootOption: D

keywords: "when it comes to implementation, some of the requirements appear to be contradicting each other." In this case, considering the specific stage of the process and the nature of the conflicts being encountered, leads us to the most appropriate option, which is tracing requirements to solution components.

Jules_CmrfrdOption: B

it's no need to trace requirements to solution components, the team will still have the conflicts. The BA should check on the business needs, and they will find the contradictions on the requirements

Adaobi_OteksOption: D

D - Since requirements were fine with the stakeholders that approved, it means that Business needs or requirements were traced successfully. But now at implementation, requirements are not matching with solution components to give the full solution scope.

IvyIOption: B

babok v3 5.1.8 Requirement (traced): have clearly defined relation to other requirements,solution components or releases,phases or iterations within the solution scope, such that coverage and the effect of change is clearly identifiable.

SavvyBAOption: B

BABOK v2 Figure 5.1.2 gives the answer, with the hint in the question being "IT"

NickMane

D also

[Removed]Option: B

I feel it's B. Business Needs Pg. 79 Traceability also supports both requirements allocation and release planning by providing a direct line of sight from requirement to expressed need.