CBAP Exam Dumps - IIBA Certified Business Analysis Professional Questions and Answers

 This question is based on a case study that compares two scenarios for Company C, a software development firm. In Scenario 1, Company C uses a traditional waterfall approach to develop a software product for a client. In Scenario 2, Company C uses an agile approach to develop the same product. The question asks for the increased cost in Scenario 2, which is the difference between the total cost of Scenario 2 and the total cost of Scenario 1. According to the case study, the total cost of Scenario 1 is $1,236,210 and the total cost of Scenario 2 is $1,444,000. Therefore, the increased cost in Scenario 2 is $1,444,000 - $1,236,210 = $207,790. References: The case study is available in the CBAP® Exam Sample Questions and Exam Blueprint document1. The answer is also verified by the CBAP® Exam Answer Key document2. Both documents are accessible from the IIBA® website3.

 A business analysis checklist is a technique that helps to ensure that all the required business analysis activities and deliverables are completed and verified. A business analysis checklist can include items such as the scope statement, the stakeholder list, the requirements documentation, the traceability matrix, the validation criteria, the change requests, and the approval signatures. A business analysis checklist can help to mitigate the concern of the project board by providing a clear and comprehensive overview of the business analysis work and its quality. A data model is a technique that helps to represent the data and information needs of an organization or a solution using graphical or textual symbols and relationships. A data model can help to define and analyze the data requirements, but it does not ensure that all the requirements are verified. A use case diagram is a technique that helps to depict the interactions between a system and its actors using graphical symbols and relationships. A use case diagram can help to define and analyze the functional requirements, but it does not ensure that all the requirements are verified. A risk register is a technique that helps to identify, analyze, and manage the uncertainties and threats that may affect the project or the solution. A risk register can help to mitigate the potential impacts of the risks, but it does not ensure that all the requirements are verified. References: BABOK Guide v3, Chapter 10: Techniques, Section 10.8: Business Analysis Checklist, p. 504-505; Section 10.18: Data Modelling, p. 522-524; Section 10.50: Use Case Diagram, p. 564-566; Section 10.51: Risk Analysis and Management, p. 567-569.

Plate architecture is a structural system consisting of plates, which are planar, two-dimensional components that only transfer forces in the direction of their level. Plate architecture can help the BAs ensure that the requirements collectively support one another and do not conflict, as it provides a clear and consistent representation of the relationships and dependencies among the requirements. Plate architecture can also help the BAs identify and resolve any gaps, overlaps, or inconsistencies in the requirements, as well as facilitate the communication and verification of the requirements with the stakeholders 12. References:

Plate (structure), Wikipedia

Top Architectural Plates: A Comprehensive Guide 2023, AMTHY

A data dictionary is a model that defines the name of the data, data aliases, and description of system data. A data dictionary is a collection of metadata that provides information about the data elements and structures in a system or a database. A data dictionary can include the following information for each data element: name, alias, description, data type, size, format, domain, constraints, default value, source, owner, and usage. A data dictionary can help the business analyst to understand the data requirements, design the data model, and ensure the data quality and consistency. A data dictionary is different from a class model, which is a model that defines the classes, attributes, operations, and relationships in an object-oriented system. A data dictionary is also different from an entity relationship model, which is a model that defines the entities, attributes, relationships, and cardinalities in a relational database. A data dictionary is not a CRUD matrix, which is a model that defines the create, read, update, and delete operations for each data element and user role in a system. References:

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 8: Requirements Analysis, page 288-289.

Data Dictionary - Tutorialspoint, paragraph 1-2

What is a Data Dictionary? | Definition and How To, paragraph 1-2

Data Dictionary - Project Management Knowledge, paragraph 1

The plan business analysis activities process involves defining the tasks and resources needed to perform the business analysis work. The inputs to this process are the business analysis approach, the organizational process assets, the stakeholder list, roles, and responsibilities, and the business analysis performance assessment. The list of identified risks is not an input to this process, but rather an output of the identify risks process, which is part of the business analysis planning and monitoring knowledge area. References: BABOK Guide v3, page 37; CBAP / CCBA Certified Business Analysis Study Guide, page 75.

A change request is not one of the three inputs the business analyst will use as he prepares for requirements elicitation. A change request is a document that proposes a modification to the project scope, schedule, budget, or quality after the project has been initiated. A change request is usually submitted by a stakeholder who wants to add, remove, or change a requirement or a feature of the project. A change request is not an input for preparing for requirements elicitation, but rather an output of the requirements management process12.

The other options are the three inputs the business analyst will use as he prepares for requirements elicitation. They are3:

Solution scope: The solution scope defines the boundaries and features of the solution that will address the business need. It helps the business analyst to focus on the relevant requirements and to avoid scope creep.

Business need: The business need is the problem or opportunity that the project aims to solve or exploit. It aligns with the strategic goals and vision of the organization. It helps the business analyst to understand the purpose and value of the project and to elicit the stakeholder needs and expectations.

Stakeholder list: The stakeholder list identifies and categorizes the people or groups who have an interest or influence in the project. It helps the business analyst to plan the appropriate elicitation techniques, communication methods, and stakeholder engagement strategies.

References:

Change Request - IIBA®

Change Request - PMI

Prepare for Elicitation - IIBA®

A collaborative approach is a type of elicitation approach that involves working with multiple stakeholders simultaneously to elicit, analyze, and validate requirements. A collaborative approach can help to complete requirements elicitation activities in a short period of time, as it can:

Reduce the number of individual meetings and interviews that need to be conducted

Increase the quality and quantity of information that can be gathered from different perspectives and sources

Enhance the communication and understanding among the stakeholders and the BA

Promote the consensus and agreement on the requirements and the solution scope

Identify and resolve any conflicts, issues, or gaps in the requirements

Some examples of collaborative elicitation techniques are:

Requirements workshops: A structured and facilitated session that brings together a group of stakeholders to elicit, analyze, and prioritize requirements

Brainstorming: A technique that generates a large number of ideas or solutions from a group of stakeholders in a creative and spontaneous manner

Focus groups: A technique that collects the opinions, preferences, and feedback of a group of stakeholders on a specific topic or issue

Prototyping: A technique that creates a simplified or partial version of the solution to elicit, demonstrate, and validate requirements

The other options are not correct because they are not types of elicitation approaches, but rather techniques that can be used within an elicitation approach. An experiment is a technique that tests a hypothesis or an assumption by observing the results of a controlled or simulated scenario. An estimation is a technique that approximates the size, cost, duration, or effort of a project or a solution. A research is a technique that collects and analyzes information from existing sources, such as documents, reports, databases, etc.

References:

[BABOK Guide v3], Section 4.2: Conduct Elicitation, p. 100-101

Types of Elicitation Techniques for the Business Analyst, Blog Post, September 2018

Elicitation Techniques Used by Business Analysts – Tips and Guidance, Blog Post, July 2023

 Success measures are the criteria that are used to evaluate the performance and value of a solution. They are derived from the business objectives and the expected benefits of the project. They help to determine whether the solution meets the needs and expectations of the stakeholders, and whether it delivers the desired outcomes and benefits. Success measures can be quantitative or qualitative, and they should be specific, measurable, achievable, relevant, and time-bound (SMART).

The other options are not correct because they are not the outputs of the initial analysis that the BA has been conducting. Business needs are the problems or opportunities that the organization wants to address with the project. Solution requirements are the capabilities and qualities that the solution must have to meet the business needs. Solution limitations are the constraints or risks that affect the solution’s performance or value. These aspects are more related to the scope and design of the solution, which are not yet defined at this point. References:

[A Guide to the Business Analysis Body of Knowledge (BABOK Guide), Version 3], Chapter 6: Strategy Analysis, pp. 134-135, 140-141; Chapter 7: Requirements Analysis and Design Definition, pp. 152-153, 158-159, 164-165; Chapter 8: Solution Evaluation, pp. 178-179, 184-185.

[Business Analysis for Practitioners: A Practice Guide], Chapter 3: Needs Assessment, pp. 46-47; Chapter 5: Requirements Analysis and Design Definition, pp. 123-124, 133-134, 140-141; Chapter 6: Solution Evaluation, pp. 157-158, 163-164.

 In the context of a parcel tracking solution, non-functional requirements are crucial as they define the system’s performance, security, usability, etc., ensuring that the solution adds value to both the business and its customers. These requirements ensure that the system is efficient, reliable, and secure and meets user expectations in terms of experience while aligning with legal and regulatory standards. References: The answer can be verified from the following sources:

A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide) Version 3, Chapter 4: Requirements Analysis and Design Definition, p. 115-116; Chapter 5: Requirements Classification Schema, p. 174-175.

Business Analysis for Practitioners: A Practice Guide, Chapter 5: Requirements Analysis and Design Definition, p. 120-121, 127-128.

The lead BA is trying to improve the business analysis practices by finding out the root causes of the problems and inefficiencies in the current state. By measuring the time spent on planned and unplanned activities, the lead BA can identify the typical missing or wasteful activities that are affecting the quality and timeliness of the deliverables. For example, the lead BA may discover that the BAs are spending too much time on rework, clarifications, or scope changes due to poor elicitation, validation, or prioritization techniques. The lead BA can then propose solutions to address these issues and enhance the business analysis performance and value. References:

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 2: Business Analysis Planning and Monitoring, page 57

Senior Business Analysis Certification CBAP® | IIBA®, Business Analysis Planning and Monitoring, page 5