IIBA Updated CBAP Exam Questions and Answers by beatriz

According to the BABOK Guide, textual requirements are one of the forms of specifying and modeling requirements. Textual requirements are written statements that describe the characteristics of the solution in a clear, concise, and consistent manner. Textual requirements typically consist of three components: the capability of the solution, the condition under which the requirement is applicable, and the constraint that may limit the solution. The capability describes what the solution must or should do, the condition describes the situation or scenario in which the requirement is relevant, and the constraint describes the restriction or limitation that may affect the solution’s ability to meet the requirement. For example, a textual requirement for a banking system could be:

The system shall allow customers to withdraw cash from any ATM machine (capability) within the network (condition) up to a maximum of $500 per day (constraint).

References:

• [A Guide to the Business Analysis Body of Knowledge (BABOK Guide)], version 3, page 402, section 10.31.2.11
• Textual Requirement Artifacts - Blueprint Online Help - HelpDocs, paragraph 1
• How to Model Textual Requirements - Formal Mind GmbH, paragraph 2

 A baseline schedule is derived from a schedule model to meet the project execution plan and achieve management approval for use as a baseline. A schedule model is a representation of the project activities, durations, dependencies, and resources that shows how the project will be executed over time. A baseline schedule is a specific version of the schedule model that is approved and frozen as a reference point for measuring and controlling the project progress and performance. A baseline schedule reflects the agreed-upon scope, cost, and schedule of the project and serves as a basis for comparison and change management. References: CBAP / CCBA Certified Business Analysis Study Guide, chapter 6, page 234; CBAP Sample Questions, question 252.

A tornado diagram is a type of bar chart that shows the effect of varying different input parameters on an output variable. It is often used in sensitivity analysis to compare the relative importance of different factors or uncertainties that affect the outcome of a decision, project, or model. A tornado diagram typically has a horizontal baseline that represents the base case value of the output variable, and vertical bars that extend to the left and right of the baseline to show how the output changes when each input parameter is varied from its minimum to maximum value, while holding all other parameters constant. The bars are usually sorted by their length, creating a shape similar to a tornado. The longer the bar, the more sensitive the output is to that input parameter. A tornado diagram can help identify the key drivers of the output variable, as well as the parameters that have little or no impact. 

The scope management plan defines how the project scope should be created, executed, monitored and controlled, and then validated. The scope management plan is a document that describes the processes and procedures for defining, managing, and controlling the project scope throughout the project life cycle. The scope management plan also defines the roles and responsibilities of the stakeholders involved in the scope management, the scope change control system, the scope verification and validation methods, and the scope baseline. The scope management plan is a component of the project management plan, which also includes other subsidiary plans, such as the schedule management plan, the cost management plan, and the quality management plan. References: [IIBA BABOK Guide v3], section 5.1.2, page 162; [CBAP / CCBA Certified Business Analysis Study Guide], chapter 6, page 233; Free CBAP CBAP® Exam Questions - IIBA CBAP Exam - Study4Exam, question 255.