Pass the IIBA Certified Business Analysis Professional CBAP Questions and answers with ExamsMirror

 Voting is a technique of requirements prioritization that involves asking the stakeholders to express their preferences for the requirements using various methods, such as ranking, rating, or allocating points or money. Voting helps to achieve consensus and alignment among the stakeholders and to identify the most important and valuable requirements. In this scenario, the business analyst is using a voting method that assigns play money to the requirements, which reflects the relative importance and benefit of each requirement. The requirements with the highest amount of play money are prioritized over the ones with lower amounts.

References:

BABOK® Guide, p. 55, 376-377

CBAP / CCBA Certified Business Analysis Study Guide, p. 165-166

Certified Business Analysis Professional™ (CBAP®) | Coursera, Course 2, Week 1, Video: “Requirements Prioritization”

According to the BABOK Guide, the business analyst must ensure that any information captured on a whiteboard or other temporary medium is transferred to a more permanent medium before it is lost or erased. This is part of the documentation and communication of the elicitation results. The other options are not required by the BABOK Guide, though they may be useful in some situations. References: BABOK Guide, Version 3, Section 4.4.6, p. 121; Certified Business Analysis Professional (CBAP) Handbook, p. 6.

The confirm elicitation results process is a technique to ensure that the information gathered during an elicitation session is accurate, consistent, and understood by all stakeholders. It involves checking the elicited information for errors, omissions, conflicts, or ambiguity, and resolving any discrepancies or gaps. The purpose of this process is to validate that the stated requirements expressed by the stakeholders match the stakeholders’ understanding of the problem and the stakeholders’ needs, not the solution, the project sponsor, or the project scope1. References: Confirm Elicitation Results - iiba.org

To compare the two solutions, we need to calculate the total cost of ownership (TCO) for each option over a given period of time. The TCO includes both the initial investment and the ongoing support costs. The formula for TCO is:

TCO=I+(S×T)

where I is the initial investment, S is the monthly support cost, and T is the number of months.

For the inhouse solution, the TCO is:

TCOinhouse​=65,000+(5,600×T)

For the vendor solution, the TCO is:

TCOvendor​=49,000+(6,100×T)

To find the breakeven point, we need to set the two TCOs equal to each other and solve for T:

65,000+(5,600×T)=49,000+(6,100×T)

Simplifying and rearranging, we get:

T=50016,000​=32

This means that the two solutions have the same TCO after 32 months. Therefore, the inhouse solution is cheaper if the solution is used for less than 32 months, and the vendor solution is cheaper if the solution is used for more than 32 months. Hence, the correct answer is A. References: BABOK® Guide, p. 97-98; Certified Business Analysis Professional™ (CBAP®) | Coursera, Course 2, Week 3, Video: “Financial Analysis Techniques”

 An assumption is a factor that is considered to be true, real, or certain for the purpose of planning, analysis, or evaluation, without having absolute proof or evidence. Assumptions are made when there is uncertainty or ambiguity about the future state of the organization or the solution. Assumptions can affect the feasibility, viability, and desirability of the solution, as well as the risks and benefits associated with it. The business analyst must document the assumptions and their characteristics and risks, in case they prove to be invalid or inaccurate, and impact the solution performance or outcome. References: BABOK Guide v3, page 36; CBAP / CCBA Certified Business Analysis Study Guide, page 74.

Quality is the degree to which a set of inherent characteristics fulfills requirements, according to the BABOK® Guide (p. 7). Quality is also defined as the extent to which a product or service meets the customer’s expectations and needs. Quality can be measured by various criteria, such as functionality, reliability, usability, efficiency, maintainability, and portability. Regulation, project phase, and scope are not related to the definition of quality. References:

BABOK® Guide, p. 7

CBAP / CCBA Certified Business Analysis Study Guide, p. 14

Certified Business Analysis Professional™ (CBAP®) | Coursera, Course 1, Week 1, Video: “Introduction to Business Analysis”

A class model is a technique to represent the structure and behavior of the entities within a solution domain. It shows the attributes, operations, and relationships of the classes that define the entities. A class is a category or type of entity that has common characteristics and can perform certain functions. A class model helps to identify the entities, their properties, their behaviors, and their interactions for a solution. Entity Relationship is a technique to represent the data and information requirements of a solution. It shows the entities, attributes, and relationships of the data and information. An entity is a thing or object of interest that can be uniquely identified and has attributes that describe its properties. An entity relationship model helps to identify the data and information, their characteristics, their associations, and their constraints for a solution. Data dictionary is a technique to define and document the data and information elements of a solution. It provides a detailed description of each data and information element, such as its name, definition, format, type, source, owner, and usage. A data dictionary helps to standardize and clarify the data and information, their meaning, their structure, and their quality for a solution. CRUD matrix is a technique to analyze the alignment of the data and information elements with the business processes or functions of a solution. It shows the data and information elements and the business processes or functions that create, read, update, or delete them. A CRUD matrix helps to identify the data and information, their lifecycle, their dependencies, and their gaps for a solution. References: Class Model - iiba.org, Entity Relationship - iiba.org, Data Dictionary - iiba.org, CRUD Matrix - iiba.org

Rough order of magnitude (ROM) cost estimating is a process of estimating the costs of the proposed solutions with a high level of uncertainty, usually in the range of -25% to +75%. ROM cost estimating is used to compare the feasibility and affordability of different solutions and to support decision making. ROM cost estimating is not a detailed or accurate process, but rather a quick and approximate way of assessing the costs of the solutions. References: CBAP / CCBA Certified Business Analysis Study Guide, Chapter 6: Requirements Analysis, page 202. Certified Business Analysis Professional (CBAP®) Handbook, page 6.

A change log is a tool that helps to manage and monitor the changes that affect the requirements, the solution, or the project. A change log tracks all characteristics and status of changes that have been received, such as the source, description, priority, impact, approval, and resolution of the changes. A change log can help to ensure that the changes are properly documented, communicated, and controlled, and that they are aligned with the stakeholder needs and expectations. References: BABOK Guide v3, page 54; CBAP / CCBA Certified Business Analysis Study Guide, page 161.

Assessing capability gaps is a task of enterprise analysis that involves analyzing the current state of the organization and comparing it with the desired future state. The purpose of this task is to identify the new capabilities that the organization needs to acquire or enhance in order to meet the business need and achieve the organizational goals and objectives. These new capabilities can be related to processes, systems, people, or resources. Assessing capability gaps can help to determine the scope and feasibility of the solution, as well as the risks and benefits associated with it. References: BABOK Guide v3, page 25; CBAP / CCBA Certified Business Analysis Study Guide, page 69.