Decision making is a type of analytical thinking competency that involves clearly validating assumptions and measuring alternatives to arrive at optimal solutions. It supports the evaluation of trade-offs and selection among multiple options based on data, goals, constraints, and stakeholder input.
Key skills include:
Identifying decision criteria
Analyzing alternatives
Understanding impacts and risks
This competency is critical for business analysts as they often guide stakeholders through structured decision-making processes during requirements prioritization, solution assessment, and risk analysis.
BABOK Reference:
Outlined in the Underlying Competencies section of the BABOK Guide, under "Analytical Thinking and Problem Solving," where decision making is emphasized for its importance in selecting the best course of action.

In the context of business analysis, a requirements viewpoint refers to a perspective or lens through which requirements are formulated and understood. A use case is an example of a requirements viewpoint because it represents a sequence of actions, typically involving an actor and a system, to achieve a goal. Use cases are used to capture functional requirements and describe how users will interact with a solution. References: The BABOK Guide mentions use cases as a tool within the requirements analysis and design definition, which aligns with the concept of a requirements viewpoint1.

Requirements allocation is the process of assigning requirements to solution components and releases to ensure that the objectives are met effectively. It involves determining which requirements will be addressed in which components of the solution and in which release they will be delivered. This process helps in managing the scope of the project, ensuring that all requirements are accounted for and appropriately assigned for implementation.
The information aligns with the practices described in the Business Analysis Body of Knowledge (BABOK) Guide, which is the standard for the practice of business analysis and guides professionals within the six core knowledge areas, describing the skills, deliverables, and techniques that business analysis professionals require to achieve better business outcomes1.

The correct answer is B. Clearly defined and managed business rules help separate policy logic from process flow. This separation makes it easier to update policies, decisions, eligibility conditions, constraints, or calculations without unnecessarily redesigning the entire process. Business rules express operational knowledge and guide or constrain behavior. When they are clearly documented and managed, organizations can adapt to regulatory, strategic, or operational changes more efficiently. Option A reverses the stronger principle; process changes may still require policy review. Option C is incorrect because business rules must still be validated for accuracy and consistency. Option D is incorrect because rules are not merely informal guidelines; many business rules are mandatory constraints that must be followed.

In the Elicitation and Collaboration knowledge area, the task " Prepare for Elicitation " takes " needs " and " stakeholder engagement approach " as key inputs. The purpose of this task is to understand the scope, identify stakeholders, choose elicitation techniques, and prepare the logistics to ensure a productive elicitation session.
* Needs define the business problem or opportunity prompting the elicitation.
* Stakeholder engagement approach outlines how stakeholders will be involved, influencing techniques and planning.
BABOK Guide v3 - Section 4.1: Prepare for Elicitation:
Inputs: " Needs " and " Stakeholder Engagement Approach "
"The purpose of Prepare for Elicitation is to understand the scope of the elicitation activity, select appropriate techniques, and plan for the elicitation."