Free Practice Questions for IIBA ECBA Exam

When the focus of specifying and modeling is on how a solution will meet requirements, the output is referred to as a design. According to the BABOK® Guide v3, design is the usable representation of a solution. It describes the solution components and how they interact to fulfill business needs. This is distinct from requirements, which describe the " what " rather than the " how. "

Requirements = What the solution must do

Design = How the solution will do it

BABOK® Reference:

Requirements Analysis and Design Definition knowledge area explains that specifying and modeling can result in either requirements or designs depending on the focus of the activity.

The task Trace Requirements ensures that requirements and designs across different levels (business, stakeholder, solution) are consistently aligned with one another. This alignment supports scope management, impact analysis, verification and validation efforts, and change control.

Requirement tracing also:

Clarifies relationships between business needs and solution features.

Enables efficient scope monitoring and helps avoid scope creep.

Supports linking requirements to their source and derived components.

BABOK® Guide v3 – Section 5.1: Trace Requirements:

“The purpose of Trace Requirements is to ensure that requirements and designs at different levels are aligned to one another and to support change analysis, coverage, and allocation.”

The correct answer is D. The structure of a monitoring and evaluation system defines how performance information will be collected, organized, governed, and used. This includes the data collection procedure, timing, responsibilities, sources, and access methods. Indicators identify what will be observed or measured, but they do not define the collection procedure itself. Metrics provide quantifiable measures, but again they do not describe the operating procedure for collecting data. Reporting focuses on how results are communicated to stakeholders after the data has been collected and analyzed. Therefore, the element that most directly addresses the procedure for data collection is structure, because it establishes the practical framework for gathering and managing evaluation information.

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

Defining stakeholder assumptions helps in identifying and managing risks. Assumptions are beliefs held by stakeholders that influence decisions and requirements. By explicitly documenting and validating these assumptions, BAs can uncover potential gaps or incorrect expectations that may lead to project failure if left unchecked.

BABOK® Reference – Task: Plan Business Analysis Approach (Section 3.1):

“Assumptions should be identified and managed to reduce risk and clarify project constraints.”

After elicitation activities are performed, the purpose of comparing the results is to ensure consistency and accuracy across information gathered from various stakeholders or techniques. This comparison helps in identifying discrepancies, resolving conflicting inputs, and validating that stakeholder perspectives are properly reflected.

BABOK® Reference – Task: Confirm Elicitation Results (Section 4.3):

“The purpose of Confirm Elicitation Results is to check the information gathered during elicitation for accuracy and consistency with other information.”

The correct answer is B. A scope model is used to define the boundaries of an initiative, solution, or change. It clarifies what is included, what is excluded, and how stakeholders should understand the limits of the work. This is important because unclear boundaries create scope creep, conflicting expectations, and unmanaged assumptions. Option A is incorrect because technical specifications describe how a solution may be built, not the overall scope boundary. Option C is incorrect because risks and issues are handled through risk analysis, issue management, or related planning activities. Option D is incorrect because roles and responsibilities are better addressed through stakeholder analysis, organizational modelling, or a RACI matrix, not a scope model.

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

The input to the ‘prepare for elicitation’ task is ‘Needs’. This involves understanding the business needs which define the scope and purpose of the elicitation activities. It is crucial for the business analyst to comprehend these needs to ensure that the elicitation efforts are aligned with the business objectives and that the right stakeholders are engaged in the process.

The ‘prepare for elicitation’ task and its inputs are discussed within the Business Analysis Body of Knowledge (BABOK) guide, which serves as a standard for the practice of business analysis. The guide outlines the necessary inputs and techniques for effective elicitation123.

" Needs " is an input to the " Prepare for Elicitation " task. This guides the preparation in terms of the scope and purpose of elicitation activities. Even if the specific needs have not been fully elicited or understood, there must be some initial recognition of needs to commence the elicitation process. Understanding these needs helps in planning the elicitation approach, selecting appropriate techniques, and ensuring that the elicitation activities are aligned with addressing these needs effectively .

In the Elicitation and Collaboration knowledge area, the task " Prepare for Elicitation " takes " needs " and " stakeholder engagement approach " as key inputs. The purpose of this task is to understand the scope, identify stakeholders, choose elicitation techniques, and prepare the logistics to ensure a productive elicitation session.

Needs define the business problem or opportunity prompting the elicitation.

Stakeholder engagement approach outlines how stakeholders will be involved, influencing techniques and planning.

BABOK® Guide v3 – Section 4.1: Prepare for Elicitation:

Inputs: " Needs " and " Stakeholder Engagement Approach "

“The purpose of Prepare for Elicitation is to understand the scope of the elicitation activity, select appropriate techniques, and plan for the elicitation.”

The integrated output that correctly reflects captured information agreed upon by business analysts and other stakeholders is the “Confirmed elicitation results.” This output is the culmination of the elicitation process where the information gathered is validated and agreed to be accurate and relevant, serving as a foundation for further analysis and decision-making. References: This answer is verified by the information found in the Business Analysis Body of Knowledge (BABOK) and discussions on the topic from credible sources related to the IIBA ECBA certification1.

Prototyping is a requirements elicitation technique that involves creating a preliminary version of a system or product to validate and refine the stakeholders’ needs. It is an iterative process that helps in discovering requirements by providing a tangible representation of the product that stakeholders can interact with. This interaction allows stakeholders to give immediate feedback, which is then used to refine the prototype in subsequent iterations. Prototyping is particularly useful when stakeholders find it difficult to articulate their needs or when the requirements are not well understood.

The use of prototyping as a technique for iteratively validating stakeholder needs is supported by the Business Analysis Body of Knowledge (BABOK) guide, which is a standard for the practice of business analysis123.