When undertaking requirements verification, the stakeholders who will be using the requirements are best positioned to determine if they are of good quality. These stakeholders have the practical experience and understanding of their needs and the context in which the requirements will be used. Their feedback ensures that the requirements are relevant, complete, and feasible. Involving stakeholders in the verification process helps in aligning the requirements with actual business needs and ensures that the final solution will be effective and satisfactory.
References:
*Business Analysis.pdf, Section on "Requirements Validation," which discusses the role of stakeholders in verifying and validating requirements.

A definitional business rule prescribes how information may be derived, inferred, or calculated based on existing business data. These rules establish precise meaning and categorization of data, ensuring that terms and concepts are consistently understood and used within the organization.
Examples include:
Calculation rules (e.g., interest = principal × rate × time)
Classification rules (e.g., customers with purchases over $10,000/year are premium) In contrast, behavioral business rules govern constraints or conditions on how actions must be performed.
BABOK Reference:
Discussed under the Strategy Analysis and Requirements Analysis and Design Definition knowledge areas, definitional business rules are explained as fundamental to maintaining business consistency and logical integrity.

The foundation for guiding the elicitation effort in business analysis is supporting material. According to the BABOK Guide v3, before initiating elicitation activities, a business analyst must review and gather relevant background information, which includes existing documentation, enterprise environmental factors, and business rules. This supporting material provides the necessary context and guidance to determine what information needs to be elicited and from whom.
Supporting material includes:
Existing system documents
Business processes and models
Organizational policies and procedures
Historical data from previous initiatives
Stakeholder and user manuals
The use of supporting material ensures that the elicitation is purposeful, well-directed, and focused on identifying information gaps and opportunities for refinement.
BABOK Reference:
This is covered under the Elicitation and Collaboration knowledge area, particularly in the task "Prepare for Elicitation," which lists supporting materials as a key input to the planning of elicitation activities.

Derive: relationship between two requirements, used when a requirement is derived from another requirement. This type of relationship is appropriate to link the requirements on different levels of abstraction. For example, a solution requirement derived from a business or a stakeholder requirement.