IIBA ECBA - Entry Certificate in Business Analysis (ECBA)

 The RACI Matrix is a tool used in business analysis to classify stakeholders according to their responsibility in a project. RACI stands for Responsible, Accountable, Consulted, and Informed. Each letter represents a level of task responsibility. The RACI Matrix clarifies the roles and responsibilities of stakeholders in a project, ensuring that everyone knows what is expected of them. This helps in avoiding confusion and overlapping of duties among stakeholders.

The use of the RACI Matrix as a tool for classifying stakeholders according to responsibility is supported by various resources on stakeholder analysis and business analysis best practices123. While the BABOK® Guide itself is a proprietary resource of the IIBA and not publicly accessible without membership, it is recognized in the business analysis community that the RACI Matrix is a standard tool for stakeholder classification4.

The task that provides stakeholders with business analysis information after the collated results are confirmed is " Communicate Business Analysis Information " , which falls under the Elicitation and Collaboration knowledge area. This task ensures that stakeholders have a shared understanding of the business analysis information, facilitating informed decision-making.

Reference from BABOK® Guide v3:

" Communicate Business Analysis Information: provides stakeholders with the business analysis information after the collated results are confirmed. "

— BABOK® Guide v3, Section 4.4

A checklist is a quality control tool used to ensure that requirements and designs meet specific criteria before they are finalized. It helps analysts systematically verify completeness, correctness, clarity, feasibility, and testability of requirements or design elements. Checklists serve as a structured way to reduce omissions and improve quality during the verification process.

Used during:

Requirements validation

Design reviews

Peer and stakeholder reviews

BABOK® Reference:

Located in the Requirements and Design Definition knowledge area, specifically under “Verify Requirements,” where checklists are mentioned as a technique for ensuring quality and completeness.

When examining requirements relationships, " unambiguous " is a key quality criterion. It ensures that the nature of the relationship between two or more requirements is clearly understood and not open to multiple interpretations. This clarity is critical for supporting impact analysis, traceability, requirement decomposition, and requirement allocation.

Poorly defined or ambiguous relationships can result in incorrect assumptions about dependencies or sequencing, potentially leading to implementation errors.

Additional Criteria Related to Requirement Relationships (from BABOK® Guide v3, Section 5.1 – Trace Requirements):

Necessity: The relationship exists because one requirement depends on another.

Correctness: The relationship accurately represents the dependency.

Consistency: The relationship does not conflict with other requirement links.

Unambiguity: All stakeholders interpret the relationship in the same way.

There are two commonly used relationships between use cases:

Extend: allows for the insertion of additional behavior into a use case. The use case that is being extended must be completely functional in its own right and must not depend on the extending use case for its successful execution. This relationship may be used to show that an alternate flow has been added to an existing use case (representing new requirements).

Include: allows for the use case to make use of functionality present in another use case. The included use case does not need to be a complete use case in its own right if it is not directly triggered by an actor. This relationship is most often used either when some shared functionality is required by several use cases or to abstract out a complex piece of logic.

 A logical data model is used to abstract a ‘conceptual data model’ by incorporating normalization rules to manage data integrity and relationships. It serves as an abstraction layer that defines the relationships between different data elements, entities, and attributes, focusing on the business concepts and rules that govern the data. This model helps in organizing data to reduce redundancy and improve data integrity, ensuring that the data structure is optimized for both business understanding and database design.

The role and benefits of a logical data model in business analysis are discussed in resources like “What is a Logical Data Model? Definition and Examples” and “The logical data model explained” which detail how logical data models serve as blueprints for structuring enterprise knowledge and ensuring data integrity12.

To ensure high-quality relationships between requirements, the criteria are that they should be consistent (logically aligned without contradictions) and correct (accurately represent the intended relationships and dependencies).

Exact Extract from BABOK® Guide v3 – Section 5.1: Trace Requirements:

“Relationships between requirements should be clearly defined, consistent, and correct to support impact analysis and traceability.”

The correct answer is C. In ECBA/BABOK, Confirm Elicitation Results is performed to ensure that the information gathered during elicitation is accurate and consistent with stakeholder understanding, and interviews are one of the techniques that can be used to communicate individually with stakeholders for that purpose. That makes the main objective here verifying that the requirements truly reflect the interviewees’ needs and expectations.

Option A is too narrow because usability and interface design feedback may be discussed in some interviews, but the question is specifically about confirming elicitation results, which is broader than UI feedback.

Option B is incorrect because ensuring that the CRM system meets all technical specifications is more related to solution design, verification, or testing activities, not the primary purpose of interviews used to confirm elicitation results.

Option D is incorrect because budget and resource allocation are not the main focus of this elicitation confirmation activity. The emphasis is on validating the captured needs and expectations with stakeholders.

 The task of defining design options involves identifying, exploring, and describing different ways of meeting the business need. This includes defining the solution approach, identifying opportunities to improve the business, allocating requirements across solution components, and representing design options that achieve the desired future state. It is about considering various possibilities that could be created (building), purchased (buying), or a combination of both, to satisfy the business need. References: The information is based on the BABOK® Guide, specifically the section on ‘Define Design Options’ which outlines the purpose and activities involved in this task12.

Transition requirements are the only category of requirements that are temporary in nature. They define the capabilities that a solution must have to facilitate the transition from the current state to the future state, but they are not needed once the transition is complete. These include data conversion, training, and deployment needs.

They support the implementation but are not part of the long-term functioning solution. This distinguishes them from business, stakeholder, and solution requirements, which are ongoing or permanent once implemented.

BABOK® Guide v3 – Section 2.3.4: Transition Requirements:

“Transition requirements describe the capabilities that the solution must have to facilitate transition from the current state to the future state, but that will not be needed once that transition is complete.”