IIBA CCBA Actual Questions

 According to the web search results, requirements envisioning is “a technique used in change-driven approaches to elicit and document a high-level overview of the scope and objectives of a project or initiative” 1. Requirements envisioning involves creating a list of high-level requirements that describe the features and capabilities of the desired solution, as well as the business value and benefits that it will deliver. Requirements envisioning helps to establish a common vision and understanding among stakeholders, as well as to prioritize and plan the requirements in short iterations. The other options are not correct because:

B. Requirements foundation is not a term used in change-driven approaches, but rather in plan-driven approaches. It refers to the “set of requirements that provide the basis for planning, managing, and delivering a project” 2.

C. Product scope is “the features and functions that characterize a product, service, or result” 3. It is not the same as the initial high-level listing of requirements, as it may include more detailed and specific information about the product specifications and quality attributes.

D. Project scope is “the work performed to deliver a product, service, or result with the specified features and functions” 3. It is not the same as the initial high-level listing of requirements, as it may include more detailed and specific information about the project activities, resources, and deliverables. References:

1: What Are High-Level Requirements in Project Management?, section “What are High-Level Requirements in Project Management?”

2: BABOK® Guide, p. 35

3: [A Guide to the Project Management Body of Knowledge (PMBOK® Guide)], p. 705

Comprehensive and Detailed Explanation:After discussing the scenario, the BA mustdocument the elicitation results and verify them through a formal review to ensure alignment with business needs.

BABOK® Guide (Chapter 3.3 - Confirm Elicitation Results)emphasizes the importance ofdocumenting and verifying requirements to ensure completeness and consistency.

Observation (Option B)is useful but not the primary action in this case.

Reviewing with stakeholders (Option C)is part of the process but does not replace verification.

Integrating the process model (Option D)comes after verification and validation.

Comprehensive and Detailed Explanation:Use cases and scenariosmodeluser interactions with a system, detailing how different roles will use the solution.

BABOK® Guide (Chapter 10.48 - Use Cases and Scenarios)states thatuse cases define user-system interactions, making them ideal for capturing roles, actions, and expected system behavior.

Sequence diagrams (Option A)show system interactions but do not define user roles.

Process models (Option C)describe workflows rather than user interactions.

Roles and permissions matrices (Option D)define access rights but not interactions.

Comprehensive and Detailed Explanation:ABusiness Model Canvasprovides avisual representation of how the company will deliver value in the new market, making it the best tool for presenting this opportunity. TheBABOK® Guide (Chapter 10.3 - Business Model Canvas)states that this tool is used todefine value propositions, revenue streams, customer segments, and key partners.