ECBA Entry Certificate in Business Analysis (ECBA) Questions and Answers

While assessing requirements changes, a business analyst (BA) determines the formality of the assessment process based on the governance approach. The governance approach provides the framework within which changes are evaluated and decisions are made regarding the approval or rejection of changes. This approach outlines the processes, roles, responsibilities, and standards that guide how changes are managed, ensuring that changes align with organizational policies and strategic objectives .

Video conferencing, electronic calendars, and electronic voting are all tools that facilitate collaboration among team members by allowing them to communicate and make decisions together, regardless of their physical location. These tools support the sharing of information and resources, coordination of activities, and collective decision-making, which are essential aspects of collaboration in business analysis.

Confirming elicitation results is a critical step in the business analysis process. It ensures that the information gathered during elicitation is not only accurate but also aligns with other information. This confirmation process involves reviewing the elicited information to identify any discrepancies, errors, omissions, or conflicts.  By doing so, business analysts can guarantee that the information used as input for further analysis and decision-making is reliable and consistent, which is essential for the success of any business initiative.  References : The importance of confirming elicitation results for accuracy and consistency is highlighted in the BABOK® Guide, which serves as a standard for the practice of business analysis 1 2 .

In the context of managing stakeholder engagement, business analysts (BAs) are particularly vigilant about the risk of scope creep. Scope creep refers to the uncontrolled expansion of project scope without adjustments to time, cost, and resources, which can occur when new requirements are added to the project without proper review. It is a common challenge in project management that can lead to project delays, budget overruns, and can compromise the quality of the final deliverable.

The correct answer is A . BABOK identifies Organizational Modelling as a technique used to understand the roles, responsibilities, and communications within an organization. It is also referenced in Plan Business Analysis Governance to help define a governance approach involving the appropriate stakeholders and decision-makers, which directly supports engagement and approvals.

Option B is incorrect because SWOT analysis is used to examine strengths, weaknesses, opportunities, and threats, not to map organizational roles and approval responsibilities.

Option C is incorrect because Benchmarking compares performance or practices with others, but it does not primarily identify internal roles, responsibilities, or decision-makers.

Option D is incorrect because Market analysis focuses on external market conditions and trends, not internal enterprise roles and governance relationships.

The correct answer is C . BABOK describes Lessons Learned as a technique used to identify changes to business analysis processes and deliverables, as well as successes that can be incorporated into future work . The purpose is to use experience from what happened before to improve current practice and influence future initiatives.

Option A is incorrect because getting consultant feedback may happen in some situations, but it is not the purpose of the lessons learned technique in BABOK. The focus is organizational learning and improvement.

Option B is incorrect because lessons learned are not meant to be kept confidential within only the BA team. Their value comes from sharing relevant insights so processes and outcomes can improve more broadly.

Option D is incorrect because lessons learned are meant to support improvement, not delay documentation unnecessarily. In many environments, especially iterative ones, learning is captured and applied continuously rather than postponed until the very end.

A cultural assessment is essential for a business analyst when analyzing the current state of an enterprise because it helps to determine if stakeholders comprehend the value delivered by the current state and whether they are satisfied with it or if a change is needed.  This understanding is crucial for ensuring that any proposed changes align with stakeholder expectations and the organizational culture.  References : The rationale for performing a cultural assessment is supported by resources that discuss the importance of understanding stakeholder satisfaction and the value delivered by the current state as part of the analysis of an enterprise 1 2 .

Considering both tangible and intangible costs and benefits provides a complete estimate of the solution’s value to the business. Tangible elements are directly measurable (e.g., cost savings, revenue), while intangible benefits (e.g., customer satisfaction, brand reputation) contribute to the strategic vision and long-term value.

Exact Extract from BABOK® Guide v3 – Section 7.6: Analyze Potential Value and Recommend Solution:

“Consideration should be given to both tangible and intangible value, including potential benefits and costs, to understand the overall impact of a proposed solution.”

The correct answer is C . BABOK says the purpose of Plan Business Analysis Approach is to define an appropriate method for conducting business analysis activities, and the Agile Extension explains that retrospectives are used for continuous improvement by reflecting on what went well, what could be improved, and how to improve the process. Because this initiative uses incremental monthly releases , the most appropriate first step is to review the latest retrospective from the previous release and use those learnings to select the approach for the next cycle. This is the strongest ECBA-aligned answer among the options.

Option A is incorrect because BABOK emphasizes selecting an approach that is appropriate to the current context , not simply reusing what worked at a different company. An approach must fit the initiative, stakeholders, and delivery environment.

Option B is weaker than C because team input can help, but the question asks for the first step , and the prior release retrospective provides concrete evidence from the same product and release model. In a monthly incremental environment, recent retrospective findings are more directly relevant than a general survey. This is an inference based on BABOK’s planning task and the Agile Extension’s use of retrospectives for continuous improvement.

Option D is incorrect because the scenario does not justify defaulting to a predictive approach. BABOK recognizes that the business analysis approach should be chosen based on context, and monthly incremental releases are typically more consistent with iterative or adaptive thinking than automatically choosing predictive just because the site is customer-facing.

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 C . BABOK’s Risk Analysis and Management technique states that each risk can be described in a risk register that supports the analysis of risks and plans for addressing them. In practice, a risk register is used to record risks and help evaluate and prioritize them based on factors such as likelihood and impact , so that response efforts can be directed appropriately.

Option A is incorrect because a risk register does not automatically eliminate any category of risk. Its purpose is to document, analyze, and support response planning for risks.

Option B is incorrect because the register is not intended to focus only on one type of risk, such as highly impactful but unlikely risks. It is meant to provide a structured basis for considering all relevant risks.

Option D is incorrect because risks are not categorized randomly. Business analysis relies on structured assessment so that risk decisions are based on meaningful criteria, especially probability and impact.

Business analysts use ‘Acceptance and Evaluation Criteria’ to measure the quality of requirements. This technique involves setting specific criteria that the requirements must meet to be accepted. These criteria are used to evaluate whether the requirements are well-defined, clear, and meet the necessary standards for successful project outcomes.  By establishing these criteria, BAs can ensure that the requirements are aligned with business objectives and can be tested against predefined standards.  References : The use of acceptance and evaluation criteria is a common practice in business analysis for ensuring requirement quality and is discussed in various business analysis resources, including the Business Analysis Body of Knowledge (BABOK) guide 1 .

The correct answer is C . The Agile Extension to BABOK includes the principle “Understand What Is Doable,” which focuses on identifying options that are realistic within the organization’s actual constraints and delivery context. In this scenario, the organization lacks the infrastructure for the ideal solution, so the business analysis professional should prioritize feasible solutions that can work within current limitations.

Option A is not the best answer because speed alone is not the defining factor of this principle. A quickly implemented option may still be unsuitable if it does not fit the organization’s constraints well.

Option B is incorrect because pushing an ideal solution despite clear infrastructure limitations conflicts with the principle of assessing what is actually doable in context.

Option D is weaker than C because a temporary workaround may sometimes be appropriate, but the principle is broader than choosing stopgap measures. The best answer is the one that explicitly focuses on feasible solutions within current constraints .

The correct answer is B . IIBA’s Business Analysis Standard states that an adaptive or iterative approach focuses on delivering value in small, prioritized increments . This is the clearest direct match to option B.

Option A is more characteristic of a predictive approach, where planning is done more extensively upfront and execution follows the established plan.

Option C is incorrect because adaptive approaches do not focus primarily on descriptive documents; they emphasize incremental value delivery and just-enough, just-in-time documentation.

Option D is also more aligned with predictive thinking, where progress is measured against a plan established in advance. Adaptive approaches continuously refine the work based on learning and priorities.

In examining relationships between requirements, the criterion of relevance ensures that each requirement is pertinent to the overall goals of the project. This means that all requirements should directly relate to the business needs and objectives, ensuring that they add value and are necessary for the project ' s success. When requirements are relevant, they help in maintaining focus on what is essential, avoiding unnecessary scope creep, and ensuring that resources are used efficiently.

The " pass around " technique involves multiple reviewers providing their feedback either verbally or in written form. This method allows various stakeholders and team members to review and comment on the requirements or other project documents. Each reviewer can build on the feedback from previous reviewers, providing a comprehensive review process. This technique helps in identifying issues, ensuring completeness, and improving the overall quality of the documents by incorporating diverse perspectives.

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 certification 1 .

When requirements express contractual obligations, acceptance criteria are necessary. These criteria ensure that the requirements meet the agreed-upon standards and conditions set forth in the contract. They provide a clear and measurable way to determine whether the requirements have been met satisfactorily.  Acceptance criteria are used to evaluate whether the solution fulfills the contract’s terms, and they form the basis for the formal acceptance of the project’s deliverables.  References : The BABOK Guide discusses the importance of acceptance criteria, especially when dealing with requirements that have contractual implications, ensuring that the deliverables meet the predefined standards and are accepted by the stakeholders 1 .

Existing solutions are considered a guideline or tool when defining design options . These can be internal systems or third-party offerings that provide baseline capabilities. Evaluating existing solutions helps the BA define viable design paths, often saving time and cost over custom-built options.

BABOK® Reference – Task: Define Design Options (Section 7.5, Inputs):

“Existing solutions may include purchased products, components of the current state, or other assets that may be leveraged when defining design options.”

 Changes to requirements can occur at any point during the project lifecycle. This is because projects are dynamic, and various factors such as evolving stakeholder needs, market trends, technological advancements, or regulatory changes can necessitate modifications to the requirements. Business Analysts must be prepared to handle these changes effectively, ensuring that the project remains aligned with its objectives while accommodating necessary adjustments.

The correct answer is D . According to BABOK, the purpose of Trace Requirements is to ensure that requirements and designs at different levels are aligned to one another and to manage the effects of change. IIBA’s task card also states that traceability identifies the lineage of requirements backwards and forwards and is used to help ensure alignment. This directly supports the idea that traceability is maintained to understand relationships and ensure alignment to the solution.

Option A is incorrect because BABOK does not limit traceability to only forward tracing. In fact, IIBA explicitly says traceability identifies the lineage of requirements backwards and forwards .

Option B is incorrect because the purpose of traceability is not to reduce granularity or complexity. Its purpose is to support impact analysis, coverage, allocation, and alignment among requirements, designs, and solution components.

Option C is also incorrect because BABOK does not restrict traceability to only backward tracing. Both backward and forward relationships are important in managing requirements across the lifecycle.

The Verify Requirements task ensures that requirements and designs meet quality standards and are usable for the purposes they are intended to serve. It focuses on confirming that the documentation is clear, correct, consistent, and testable.

Quality characteristics evaluated during this task include:

Clarity and unambiguity

Feasibility and relevance

Completeness and correctness

Consistency and traceability

This task is typically done before requirements validation (which ensures alignment with business goals and stakeholder needs).

BABOK® Guide v3 – Section 7.1: Verify Requirements:

“The purpose of Verify Requirements is to ensure that requirements and designs specifications and models meet quality standards and are usable for the purpose they serve.”

In planning an information management approach, a repository is the input element that indicates the current status of stored information. A repository provides a centralized location where information is stored, managed, and retrieved. It gives a clear picture of the current data landscape, including what data is available, how it is organized, and how it can be accessed. This is crucial for effective information management as it helps in assessing the completeness, accuracy, and relevance of the information stored.

In the context of business analysis, the term " stability " refers to the likelihood that a requirement will change due to the need for further analysis or because stakeholders have not reached a consensus. Stability is a critical attribute to assess as it impacts the prioritization, planning, and management of requirements. Requirements with low stability may require additional attention, analysis, or engagement with stakeholders to clarify, refine, and agree upon the needs to ensure they are well-understood and stable enough to be implemented effectively without significant changes in the future.

The correct answer is C . BABOK defines value as the worth, importance, or usefulness of something to a stakeholder, and that value can be assessed in financial terms when it is tangible. Measures such as cost savings, increased revenue, and return on investment (ROI) are objective and quantifiable, making them the most appropriate indicators of tangible value. ( iiba.org )

Option A is not the best answer because collaboration and communication efficiency may be beneficial, but they are often indirect or partially qualitative measures unless tied to specific financial outcomes. On their own, they do not represent the clearest measurement of tangible value. ( iiba.org )

Option B is incorrect because improvements in relationships and engagement are generally intangible benefits. They may be important, but they are not the most direct way to measure tangible value. ( iiba.org )

Option D is also incorrect because stakeholder satisfaction and NPS are largely perception-based and are better categorized as subjective or mixed indicators rather than strictly tangible financial measures. While useful, they are not the strongest ECBA-style answer for tangible value. ( iiba.org )

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 inputs required to prepare for elicitation are primarily focused on understanding the business needs and the stakeholder engagement approach. This involves recognizing the business requirements to define the scope and purpose of the elicitation activities and comprehending the stakeholders’ collaboration and communication needs to plan the elicitation activity effectively.

In process analysis , the BA evaluates a process to determine how efficiently and effectively it is achieving its goals. This involves analyzing process steps, identifying waste or redundancy, and seeking opportunities for optimization.

BABOK® Reference – Technique: Process Analysis (Section 10.33):

“Process analysis evaluates the efficiency and effectiveness of a process, identifying opportunities to improve performance.”

 Stakeholders often face challenges in prioritizing requirements due to different perceived values. This challenge arises because stakeholders may have varying opinions on what is most important, leading to conflicts and difficulties in reaching a consensus on priority. The diversity in stakeholders’ backgrounds, roles, and interests can result in a wide range of perspectives on which requirements should take precedence.

During the requirements life cycle management phase, one of the key activities is to trace requirements. This involves ensuring that requirements and designs at different levels are aligned with one another and managing the effects of changes to one level on related requirements and designs. Tracing requirements helps maintain the integrity of the requirements throughout the project’s life cycle, from inception to retirement.

Validate requirements ensures that a set of requirements or designs delivers business value and supports the organization ' s goals and objectives.

Requirements that are good candidates for reuse are those that are not tied to a specific tool, technology, or system. These requirements are generally applicable across various contexts and can be used in multiple projects without significant changes. They are typically high-level business requirements that describe what the business needs without prescribing how to achieve it. This makes them flexible and adaptable to different situations, which is essential for reuse.

The end user is best positioned to verify that prioritized requirements will deliver value from a customer perspective because they directly interact with the solution and experience its outcomes. Their feedback ensures that the requirements meet usability, functionality, and satisfaction expectations.

While other stakeholders like the sponsor or domain SME validate alignment with business goals, the end user focuses on practical, value-based utility.

BABOK® Reference:

Throughout the BABOK®, particularly in Requirements Life Cycle Management and Solution Evaluation , the role of the end user is emphasized for validation and feedback based on real-world use.

Matrices in modeling formats are used to describe complex but uniform structures. They are particularly useful for breaking down and organizing complex requirements into a structured and understandable format. By inputting simple requirements into a matrix, business analysts can model requirements that are complex in nature but uniform in structure, such as those found in data dictionaries, gap analysis, and requirements traceability.

Identify Improvement OpportunitiesWhen proposing design options, a number of opportunities to improve the operation of the business may occur and are compared.Some common examples of opportunities include:

Increase Efficiencies: automate or simplify the work people perform by re-engineering or sharing processes, changing responsibilities, or outsourcing. Automation may also increase consistency of behaviour, reducing the likelihood of different stakeholders performing the same function in distinctly different fashions.

Improve Access to Information: provide greater amounts of information to staff who interface directly or indirectly with customers, thereby reducing the need for specialists.

Identify Additional Capabilities: highlight capabilities that have the potential to provide future value and can be supported by the solution. These capabilities may not necessarily be of immediate value to the organization (for example, a software application with features the organization anticipates using in the future).

The foundation for guiding the elicitation effort in business analysis is supporting material . According to the BABOK® Guide v3, before initiating elicitation activities, a business analyst must review and gather relevant background information, which includes existing documentation, enterprise environmental factors, and business rules. This supporting material provides the necessary context and guidance to determine what information needs to be elicited and from whom.

Supporting material includes:

Existing system documents

Business processes and models

Organizational policies and procedures

Historical data from previous initiatives

Stakeholder and user manuals

The use of supporting material ensures that the elicitation is purposeful, well-directed, and focused on identifying information gaps and opportunities for refinement.

BABOK® Reference:

This is covered under the Elicitation and Collaboration knowledge area, particularly in the task " Prepare for Elicitation, " which lists supporting materials as a key input to the planning of elicitation activities.

The task that uses the " Elicitation Activity Plan " to draw out, explore, and identify information relevant to the change is " Conduct Elicitation. " This task involves direct interaction with stakeholders or independent research to understand stakeholder needs and identify potential solutions that may meet those needs. The Elicitation Activity Plan guides the business analyst through the planned elicitation activities, ensuring that the elicitation is focused, efficient, and aligned with the project objectives. This structured approach to elicitation helps in gathering relevant and accurate information, which is essential for the success of the change initiative .

The correct answer is B . In BABOK, stakeholder engagement planning includes identifying the appropriate stakeholders for a given situation and determining how and when to communicate with them. When an unexpected issue blocks progress, the business analyst should first understand the issue sufficiently and determine which stakeholders are relevant before initiating communication or meetings. This avoids unnecessary confusion and ensures the right people are involved in resolving the problem. ( iiba.org )

Option A is incorrect because sending a summary to all stakeholders may be premature and may include people who are not directly impacted or needed. BABOK emphasizes identifying stakeholder characteristics, responsibilities, and collaboration needs rather than communicating indiscriminately. ( iiba.org )

Option C is incorrect because delaying action until a complete solution is found can worsen the blockage. Business analysis supports timely collaboration and issue escalation when necessary; waiting too long can increase project risk and reduce responsiveness. (iiba.org)

Option D is also incorrect because immediately scheduling a meeting with all stakeholders is not always appropriate. The analyst should first determine the nature of the issue and who needs to be involved. BABOK encourages purposeful stakeholder engagement, not automatic involvement of everyone. ( iiba.org )

The main purpose of the “Approve Requirements” task in business analysis is to obtain agreement and approval on the requirements and designs from all stakeholders involved in the governance process.  This step ensures that there is a shared understanding and commitment to the requirements, which is essential for the successful implementation of the solution.  References : The information aligns with the standards and practices outlined in the Business Analysis Body of Knowledge (BABOK) and other learning resources provided by the International Institute of Business Analysis (IIBA) 1 2 3 .

The approach in which solution components are assembled, constructed, or developed by experts as a direct response to a set of requirements is referred to as “Create.” This involves the business analysts assessing the merits of the solution approaches for each design option, which includes creating solution components that are tailored to meet the specific requirements. This option also encompasses modifying an existing solution to better fit the requirements.

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.

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.”

The role of a business analyst is pivotal in discovering, synthesizing, and analyzing information from various sources within an enterprise. This includes gathering data from tools, processes, documentation, and stakeholders. Business analysts are tasked with eliciting the true needs of stakeholders, which often involves investigating and clarifying their expressed desires to determine underlying issues and causes. They play a crucial role in aligning the designed and delivered solutions with the needs of stakeholders, ensuring that the outcomes meet business objectives effectively.

 The task of planning stakeholder engagement is a crucial part of the business analysis planning and monitoring knowledge area. It involves identifying stakeholders, understanding their needs and expectations, and determining the best ways to engage them in the business analysis process.  Effective stakeholder engagement is essential for ensuring that the requirements and solutions developed align with stakeholder needs and contribute to project success.  References : The Business Analysis Planning and Monitoring knowledge area includes tasks such as planning the business analysis approach, stakeholder engagement, governance, information management, and identifying business analysis performance improvements 1 .

Traceability is a tool used in business analysis to track the life of a requirement from its origin through its development and specification, to its subsequent deployment and use, and through periods of ongoing refinement and iteration in any of these phases. It allows business analysts to determine the impact of changes in requirements by providing a clear path of how each requirement is connected to others, which is essential for assessing the consequences of changes.

Systems thinking is a crucial skill for business analysts as it enables them to view the enterprise in a holistic manner. This approach helps BAs understand the complex interactions between people, processes, and technology within an organization. It involves recognizing patterns and interrelationships and considering how different systems work together and influence one another within the whole.  By applying systems thinking, BAs can better comprehend the broader impacts of any changes to one part of the system on the entire organization.  References : The BABOK® Guide outlines the importance of systems thinking as a competency for business analysts, emphasizing its role in understanding the enterprise from a holistic perspective 1 2 .

The measure of significance in reporting business analysis performance refers to how well the value delivered by the BA work products justifies the effort and resources invested . It focuses on whether the deliverables contributed meaningful value to the organization and whether they supported decision-making, change enablement, or strategic goals.

BABOK® Reference – Task: Assess Business Analysis Performance (Section 3.5):

“Significance assesses the value delivered by the business analysis work and whether it justifies the resources expended.”

The correct answer is A . IIBA’s Business Analysis Standard and Agile business analysis principles emphasize thinking as a customer and analyzing to determine what is valuable . These ideas align directly with customer focus and value maximization , which are core drivers of effective business analysis work.

Option B is incorrect because although communication and planning matter, this combination does not reflect the central shared values highlighted by IIBA as the primary drivers of business analysis work.

Option C is incorrect because market assessment and management input may be useful in some contexts, but they are not presented by IIBA as the core shared values that broadly drive business analysis.

Option D is incorrect because courtesy and loss minimization are not the recognized IIBA shared values most associated with business analysis practice.

Good collaboration with stakeholders is characterized by regular, frequent, and bi-directional communication with all stakeholders involved in the initiative. This ensures that all voices are heard, and that information, ideas, and innovations are freely exchanged, contributing to a more inclusive and comprehensive understanding of the project requirements and objectives.

Impact analysis is a technique designed to identify the full consequences of a change within an organization. It provides a structured approach for examining a proposed change to identify as many of the negative impacts or consequences of the change as possible. This analysis is crucial for understanding the ripple effects of changes and preparing for them, ensuring that the organization can adapt smoothly and maintain its operations effectively.

In the context of business analysis, value is a critical factor that influences the prioritization of requirements. It reflects the benefit or outcome the requirement brings to the business, ensuring that the most beneficial requirements are addressed first to maximize the return on investment and meet the strategic goals of the organization.

In the context of business analysis, a requirements viewpoint refers to a perspective or lens through which requirements are formulated and understood. A use case is an example of a requirements viewpoint because it represents a sequence of actions, typically involving an actor and a system, to achieve a goal.  Use cases are used to capture functional requirements and describe how users will interact with a solution.  References : The BABOK Guide mentions use cases as a tool within the requirements analysis and design definition, which aligns with the concept of a requirements viewpoint 1 .

 In the context of collaborative games used in business analysis, the opening step is where participants are informed about the problem and the rules of the game. It is during this initial phase that they start generating ideas.  This step is crucial as it sets the stage for the exploration and iteration steps that follow, where ideas are further developed and refined.  References : The information is verified as per the Business Analysis Learning documents, which outline that during the opening step of a collaborative game,

A data flow diagram illustrates the movement and transformation of data between externals (entities) and processes. The output from one external or process is the input to another. The data flow diagram also illustrates the temporary or permanent repositories (referred to as data stores or terminators) where data is stored within a system or an organization. The data defined should be described in a data dictionary.

The correct answer is D . BABOK’s requirements classification schema defines business requirements as statements of goals, objectives, and outcomes that describe why a change has been initiated . This is the exact wording used by IIBA, so business requirements are the best and fully correct choice here.

Option A is incorrect because stakeholder requirements describe the needs of stakeholders that must be met to achieve the business requirements. They help bridge the gap between business requirements and more detailed solution requirements, but they do not primarily express why the change was initiated.

Option B is incorrect because solution requirements describe the capabilities and qualities a solution must have in order to meet stakeholder and business needs. They focus on what the solution must do or how well it must perform, not on the original reason for the change.

Option C is incorrect because transition requirements describe temporary capabilities needed to move from the current state to the future state, such as migration, training, or implementation support. They do not state the goals and objectives behind the change.