Requirements at high levels of abstraction may be written with limited reference to specific solutions. Requirements that are represented in a general manner, without direct ties to a particular tool or organizational structure, tend to be more reusable.

In the context of Business Analysis, requirements should be initially prioritized based on the business benefits they are expected to deliver. This approach aligns with the principle of delivering the most value to the organization and ensuring that the most impactful requirements are addressed first. Prioritizing by business benefits helps in focusing on what is most important for achieving business objectives and delivering value to stakeholders.
References: The prioritization of requirements is a critical step in the requirements life cycle management, as outlined in the BABOK Guide. While the guide itself is not publicly accessible without membership, it is widely recognized that business benefits are a key factor in prioritization. This is supported by various resources and articles that discuss prioritization methods within the domain of Business Analysis.

In preparation for elicitation, a business analyst secures supporting material which is essential for the elicitation activities. This involves identifying and procuring all necessary information and resources that will be used during these activities. It includes gathering documents, systems information, historical data, and any other relevant materials that will support the elicitation process.
References: The BABOK Guide emphasizes the importance of securing supporting materials as part of the preparation for elicitation. This step ensures that the business analyst has all the necessary tools and information to effectively conduct elicitation activities1.