Explanation/Reference:
Requirements allocation typically begins early in the project lifecycle (as soon as the solution approach is determined) and will continue to be performed until all valid requirements are allocated. Allocation typically continues through design and construction of a solution.
C is incorrect. Requirements allocation doesn't have to wait until the project has been chartered.
B is incorrect. Approval of the requirements is good, but the solution scope for the requirements
needs to be created to begin allocating the requirements.
A is incorrect. The budget creation isn't linked to the requirements allocation process.

Explanation
The business analyst must understand how the organization operates and the objectives of business analysis duties. Without a clear understanding of what the expected outcomes are to be of the business analysis duties, the business analyst cannot adequately plan for the business analysis duties.
Answer B is incorrect. It's important for the business analyst to identify and categorize stakeholders, but this
isn't the best answer for this question.
Answer D is incorrect. The purpose of the proposed solution is valid only if the initiative is to solve a
problem. Business analysis can also occur to detail an opportunity, not just to create solutions to identified problems.
Answer C is incorrect. This isn't the best answer for this question.

Explanation/Reference:
Explanation:
The only input to the task of defining assumptions and constraints is stakeholder concern.
C is incorrect. Requirements aren't inputs to the task of defining assumptions and constraints.
B is incorrect. Prioritized requirements aren't inputs to the task of defining assumptions and
constraints.
A is incorrect. The business case isn't an input to the task of defining assumptions and
constraints.

Explanation
Plan driven approaches to business analysis practices most often use the formal type of communications. This means the communication of the actual requirements is in writing, and often uses pre-defined forms requiring signatory approvals. All project documentation is normally archived as part of the project history. Face-to-face is an effective communication method, but for plan-driven approaches, formal communication is preferred in regard to requirements. Ad hoc describes the sudden, quick conversations. This is an informal approach to communication and isn't appropriate for a plan-driven business analysis approach.