CBAP Exam Dumps : Certified Business Analysis Professional

A RACI chart is a tool that helps to define and clarify the roles and responsibilities of different stakeholders in a project or a process. It stands for Responsible, Accountable, Consulted, and Informed, which are the four types of tasks or activities that stakeholders can be involved in. A RACI chart is a matrix that lists the tasks or activities in the left column and the stakeholders or roles in the top row. For each task or activity, the RACI chart indicates who is Responsible, Accountable, Consulted, or Informed by using the letters R, A, C, or I. A RACI chart can help to improve communication, collaboration, and accountability among stakeholders, and to avoid confusion, duplication, or conflict of roles. A RACI chart can be used as part of the stakeholder analysis process, which is the process of identifying, categorizing, and assessing the stakeholders of a project or a process, and understanding their needs, expectations, and interests.

References:

RACI Chart - a how to guide to using RACI, paragraph 1

How the RACI Matrix Streamlines Stakeholder Engagement, paragraph 1

Stakeholder Wrangling 101: The RACI Framework, paragraph 1

[A Guide to the Business Analysis Body of Knowledge (BABOK Guide)], version 3, page 30, section 2.51

 A repository is a centralized place where project requirements are stored and managed throughout the project lifecycle. A repository can be a physical or electronic system that allows business analysts to access, update, and track the status of the requirements. A repository can also facilitate the communication, collaboration, and verification of the requirements among the stakeholders. A repository is not the same as a change management system (A), a project scope statement ©, or a requirements register (D), which are different tools or documents that serve different purposes in project management. References:

IIBA BABOK Guide v3, p. 30, 176, 264

How to Write Project Requirements | Smartsheet, paragraph 3

What is Requirements Management? | IBM, paragraph 1

The relationship quality criterion that this represents is unambiguous, as it means that the requirements are clear, consistent, and have only one interpretation. Having unambiguous relationships among requirements helps to avoid confusion, conflicts, and errors in the requirements architecture. It also facilitates traceability, validation, and verification of the requirements. References: The answer can be verified from the following sources:

A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide) Version 3, Chapter 4: Requirements Analysis and Design Definition, p. 113-114; Chapter 6: Requirements Life Cycle Management, p. 205-206.

Business Analysis for Practitioners: A Practice Guide, Chapter 5: Requirements Analysis and Design Definition, p. 118-119.