A: Assumptions and constraints are identified through a review of project requirements: This is an incorrect answer, as it implies that the assumptions and constraints are already known and documented in the project requirements. However, assumptions and constraints are factors that affect the project requirements, not the other way around. Therefore, they should be identified before or during the requirements analysis, not after.
B: Assumptions and constraints are identified through elicitation from stakeholders: This is a correct answer, as it describes one possible source of identifying assumptions and constraints.
Elicitation is the process of discovering, exploring, and communicating the needs and expectations of the stakeholders. During elicitation, the business analyst can ask the stakeholders about their assumptions and constraints regarding the project scope, schedule, budget, quality, risks, etc.
C: Assumptions and constraints are identified through risk identification and analysis: This is a correct answer, as it describes another possible source of identifying assumptions and constraints. Risk identification and analysis is the process of determining the potential threats and uncertainties that may affect the project's objectives, scope, schedule, cost, or quality. During risk identification and analysis, the business analyst can identify the assumptions and constraints that may introduce or increase the risks for the project.
D: Assumptions and constraints are identified through document analysis: This is a correct answer, as it describes yet another possible source of identifying assumptions and constraints. Document analysis is the process of reviewing and analyzing existing documentation, such as policies, procedures, standards, regulations, contracts, etc. During document analysis, the business analyst can identify the assumptions and constraints that are imposed by the organization or the external environment.