IIBA Updated ECBA Exam Questions and Answers by samir

In use case diagrams, the relationships between use cases may include “include” and “extend.”

Include indicates that a use case incorporates another use case as part of its behavior.

Extend shows optional behavior that extends the base use case under certain conditions.

These relationships help modularize functionality and clarify dependencies.

BABOK® Reference – Technique: Use Cases and Scenarios (Section 10.49):

“Use cases can have relationships such as include or extend to indicate reuse or conditional behavior extensions.”

The correct answer is C. Analyzing the current state helps the business analyst understand why a need exists, what problems or opportunities are present, what capabilities are available, and what internal or external conditions influence the need for change. This task provides the foundation for understanding the business need before moving toward solutions. Option A is too broad; stakeholder engagement supports analysis but does not itself define the business need. Option B is only one elicitation technique and may contribute information, but it is not the task that produces a broader understanding. Option D comes later because the future state should be defined after understanding the current situation, the problem, and the drivers for change.

===============

When a stakeholder seeks to understand the logistics and scope of each elicitation activity, the Business Analyst should share the elicitation activity plan. This plan outlines the objectives, techniques, stakeholders involved, and the schedule for each elicitation activity, providing clarity and setting expectations.

Reference from BABOK® Guide v3:

" Prepare for Elicitation: describes the tasks that the business analyst performs to prepare for elicitation activities. It includes determining the types of activities, the techniques, and the logistics required. "

— BABOK® Guide v3, Section 4.1

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.