CBAP Exam Dumps : Certified Business Analysis Professional

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?

A non-negotiable demand by a stakeholder during the requirements prioritization session is one that does not allow for any trade-offs, compromises, or alternatives. It is a demand that must be met regardless of the impact on other requirements, the feasibility of the solution, or the value to the organization. A stakeholder who insists that all requirements are ranked as high is making a non-negotiable demand, as this would prevent any meaningful prioritization and allocation of resources. Communication, cost-benefits ratio, and cost are not non-negotiable demands, as they can be negotiated, adjusted, or balanced with other factors during the requirements prioritization session. References: BABOK Guide v3, section 10.25 Requirements Prioritization; 1

 Quality control is not one of the reasons why trace requirements is useful, but a process that monitors and measures the quality of the project deliverables and outputs against the quality standards and criteria established in the quality management plan. Quality control is used to make certain that the project team members are completing the project work according to the project plan and meeting the stakeholder expectations. Quality control involves performing quality audits, inspections, tests, reviews, and validations to identify and correct any defects, errors, or deviations from the specifications1.

The other three options are valid reasons why trace requirements is useful. Trace requirements is a technique that involves establishing and documenting the relationships between requirements and other aspects of the product management process, such as design elements, test cases, releases, and incidents. Trace requirements is useful for the following purposes234:

Impact analysis: Trace requirements helps to evaluate the impact of a potential change or a problem on the requirements and the solution. By tracing the dependencies and links between requirements and other items, the business analyst can quickly and easily assess the scope, cost, time, and risk implications of the change or the problem, and plan the appropriate response actions.

Requirements coverage: Trace requirements helps to ensure that all the requirements are fulfilled by the solution and that all the solution components contribute to the requirements. By tracing the alignment and mapping between requirements and solution components, the business analyst can verify that the solution meets the stakeholder needs and expectations, and that there are no gaps or redundancies in the solution.

Requirements allocation: Trace requirements helps to assign requirements to solution components and to releases. By tracing the distribution and allocation of requirements to different parts of the solution and to different phases of the project, the business analyst can prioritize and schedule the requirements based on their value, risk, dependency, and complexity, and ensure that the solution is delivered incrementally and iteratively. References: 1: Project Quality Management: Processes & Tools | Villanova University5 2: Requirements Traceability - The What, Why and How | Netmind6 3: Requirements traceability – why and how to do it?7 4: Requirements traceability : What, why and how - Modern Analyst8