CBAP Exam Dumps : Certified Business Analysis Professional

Business rules analysis is a business analysis technique that involves identifying, analyzing, and documenting the rules that govern how an organization operates and makes decisions. Business rules analysis can help an organization to adapt to the change economy, new technologies, and an increase in competition by ensuring that the rules are aligned with the organizational goals and objectives, and that they are consistent, transparent, and flexible. Business rules analysis can also help to identify any gaps, conflicts, or redundancies in the existing rules, and to propose new or revised rules that can improve the organizational performance and efficiency. References: BABOK Guide v3, page 142; CBAP / CCBA Certified Business Analysis Study Guide, page 191.

 Problem tracking is a document elicitation technique that can help in this scenario. Problem tracking is the process of identifying, documenting, and resolving issues that arise during the business analysis process. Problem tracking helps to ensure the quality and validity of the requirements and the solutions. Problem tracking also provides an opportunity for stakeholders to rank the importance of issues affecting them. Problem tracking can be done using various tools, such as spreadsheets, databases, or software applications. Problem tracking can help the business analyst to monitor the status of the issues, communicate the progress and outcomes to the stakeholders, and improve the business analysis performance and practices. The other options are not document elicitation techniques, but rather information elicitation techniques. Brainstorming is a technique that involves generating new ideas and finding solutions for a specific problem. Observation is a technique that involves watching how people perform their tasks or interact with a system. Interviews are a technique that involves asking questions and documenting the responses from a single person or a group of people. References:

Problem/Issue Tracking Technique — Business Analyst Learnings, paragraph 1

Elicitation Methods | SpringerLink, paragraph 1

Understanding the Document Analysis Technique - Business Analyst Learnings, paragraph 1

Change requests are more likely to occur in the early stages of a project, when the requirements are being elicited, analyzed, and validated. During this time, stakeholders may discover new needs, identify gaps, or revise their expectations. Change requests may also arise due to changes in the business environment, such as new regulations, market trends, or competitor actions. Change requests are less frequent in the later stages of a project, when the requirements are more stable and the solution is being designed, developed, and tested. References:

A Guide to the Business Analysis Body of Knowledge (BABOK Guide), Version 3, Chapter 4: Requirements Life Cycle Management, Section 4.5: Manage Changes1

CBAP Certification Study Guide v3.0, Chapter 4: Requirements Life Cycle Management, Section 4.5: Manage Changes2