IIBA Updated CBAP Exam Questions and Answers by jaxxon

The future value of the requirements is not a factor that will help with the decision analysis approach to the requirements prioritization process. The future value of the requirements is the expected benefit or return that the requirements will provide in the longterm, which may depend on various assumptions and uncertainties. The future value of the requirements is not a reliable or objective criterion for comparing and selecting the best decision for the requirements outcome.

The other three factors are essential for the decision analysis approach to the requirements prioritization process. The values, goals, and objectives that are relevant to the requirements are the desired outcomes and criteria that the stakeholders want to achieve or satisfy with the solution. The consequences of each possible decision are the impacts and risks that each option will have on the organization and its stakeholders. The nature of the decision that must be made is the type and complexity of the decision, such as whether it is strategic, operational, or tactical, and whether it involves multiple alternatives, trade-offs, or uncertainties. These factors help the business analyst to evaluate and compare the options and to select the best one that maximizes the value and minimizes the risk of the solution. References:

• BABOK® Guide, p. 66-67
• CBAP / CCBA Certified Business Analysis Study Guide, p. 133
• Certified Business Analysis Professional™ (CBAP®) | Coursera, Course 1, Week 2, Video: “Business Analysis Planning and Monitoring”

Brainstorming is a technique to generate a large number of ideas or options for a problem or opportunity in a short time. It involves a group of stakeholders who share their thoughts and suggestions without criticism or evaluation. Brainstorming helps to identify options, factors, delays, and ideas for a solution by encouraging creativity, diversity, and collaboration. Benchmarking is a technique to compare the current state of a process, product, or service with a desired or best practice state. It involves identifying the performance indicators, standards, and targets for improvement. Benchmarking helps to identify gaps, opportunities, and best practices for a solution by providing a reference point or a baseline. Data flow diagrams are a technique to model the flow of data and information through a system or process. They involve identifying the sources, destinations, processes, and stores of data and information, and the relationships among them. Data flow diagrams help to identify inputs, outputs, transformations, and storage of data and information for a solution by providing a visual representation of the system or process. Business rules analysis is a technique to identify, express, validate, refine, and organize the rules that shape day-to-day business behavior and guide operational business decision making. Business rules are specific, actionable, testable directives that support a business policy. Business rules analysis helps to identify rules, policies, decisions, and constraints for a solution by providing a clear, consistent, and separated expression of the business logic. References: 9 Elicitation Techniques Used by Business Analysts – Tips and Guidance, CBAP® Handbook, Requirements Elicitation - Where to start as a Business Analyst?

 Decision analysis is a business analysis technique that involves evaluating the feasibility, benefits, risks, and impacts of various options and selecting the best one based on predefined criteria and stakeholder preferences. In this scenario, the business analyst is considering using decision analysis to rate the available methodologies against the organizational needs and objectives, and to choose the most suitable one for the business analysis approach. Decision analysis can help the business analyst to align the business analysis activities with the project and enterprise goals, and to optimize the value delivery of the solution. References:

• BABOK® Guide, p. 66-67
• CBAP / CCBA Certified Business Analysis Study Guide, p. 133
• Certified Business Analysis Professional™ (CBAP®) | Coursera, Course 1, Week 2, Video: “Business Analysis Planning and Monitoring”

 Document analysis is a requirements elicitation technique that examines the available information, documentation, records, and history of a solution, organization, or cause to identify relevant information to the current business analysis duties. Document analysis helps the business analyst to understand the existing processes, policies, standards, regulations, and systems that may affect the project or the solution. Document analysis also helps to discover the implicit, hidden, or undocumented requirements that may not be easily obtained from other sources. Document analysis can be done using various types of documents, such as business plans, contracts, manuals, reports, diagrams, models, or logs. Document analysis is different from benchmarking, which is a technique that compares the performance or practices of an organization or a solution with those of other organizations or solutions. Document analysis is also different from dataflow diagrams, which are graphical models that show how data moves through a system or a process. Document analysis is not requirements elicitation, which is a general term for the process of gathering and discovering the requirements from various sources and stakeholders. References:

• CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 4: Elicitation and Collaboration, page 181-182.
• [Requirements Elicitation in Software Engineering Complete Guide …, paragraph 3
• Elicitation Technique Guide | Info-Tech Research Group, paragraph 1
• Requirements elicitation techniques: a systematic literature review …, paragraph 1