Changed CBAP Exam Questions

The BA should use the Allocate Requirements technique to assign requirements to the various solution components to ensure all objectives are met. This technique involves distributing stakeholder and solution requirements among solution components and releases in order to maximize the possible business value given the options and alternatives generated by the design team. The BA should consider the dependencies, constraints, priorities, and risks of each requirement and component, and ensure that the allocation is traceable, verifiable, and consistent with the project scope and objectives. References:

IIBA BABOK Guide, Section 7.2, Allocate Requirements

Oh Where, Oh Where Does This Requirement Belong? (BABOK 7.2), Bridging the Gap

Requirements Allocation, AcqNotes

According to the BABOK® Guide1, the business analysis approach is the set of processes, tools, deliverables, techniques, and standards that will be used to perform business analysis work on a project. The approach can be either plan-driven, adaptive, or a hybrid of both. A plan-driven approach is more suitable for projects that have stable and well-defined requirements, low levels of change, and clear acceptance criteria. An adaptive approach is more suitable for projects that have uncertain or evolving requirements, high levels of change, and emergent outcomes. Therefore, one of the factors that would drive the decision towards an adaptive approach is the organization’s tolerance for uncertainty, which means the degree to which the organization is willing to accept ambiguity and risk in the project. An organization with a high tolerance for uncertainty can benefit from an adaptive approach that allows for frequent feedback, experimentation, and learning. References:

A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide), Version 3, Chapter 3: Business Analysis Planning and Monitoring, Section 3.2: Plan Business Analysis Approach, p. 57-59

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 3: Business Analysis Planning and Monitoring, Section 3.2: Plan Business Analysis Approach, p. 89-91

 The requirement ‘’Ability to view policies created in the legacy system for a period of 6 months’’ is a transition requirement. A transition requirement is a temporary requirement that specifies the capabilities or conditions that the solution must have or meet during the transition from the current state to the future state. Transition requirements are typically related to data conversion, training, migration, or decommissioning. In this case, the requirement is needed to ensure that the policies created in the legacy system are still accessible for a limited time after the system is decommissioned, until the new system is fully operational and stable. References:

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 2: Business Analysis Key Concepts, Section 2.4: Requirements Classification Schema, p. 66-67

A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide), Version 3, Chapter 2: Business Analysis Key Concepts, Section 2.4: Requirements Classification Schema, p. 34-35

A data model is a graphical or textual representation of the data and their relationships within a domain or a solution. It can help to understand the data and accurately reflect a set of requirements by showing the entities, attributes, keys, constraints, and associations that define the data structure and meaning. A data model can also help to prioritize the requirements by identifying the critical and dependent data elements and their impacts on the solution. The other options are not the best modeling formats for this purpose, as they either do not show the data relationships, or do not support prioritization. References:

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 6: Requirements Analysis and Design Definition, Section 6.4: Model and Validate Requirements, p. 261-262

A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide), Version 3, Chapter 6: Requirements Analysis and Design Definition, Section 6.4: Model Requirements, p. 157-158