Prioritization of requirements is not a one-time activity but a continuous process that occurs throughout the initiative. This approach allows for adjustments as new information is discovered, priorities shift, and the project evolves. It ensures that the most current and relevant requirements are being addressed at any given time, aligning with the changing needs and values of the business and stakeholders.

There are two commonly used relationships between use cases:

Extend: allows for the insertion of additional behavior into a use case. The use case that is being extended must be completely functional in its own right and must not depend on the extending use case for its successful execution. This relationship may be used to show that an alternate flow has been added to an existing use case (representing new requirements).

Include: allows for the use case to make use of functionality present in another use case. The included use case does not need to be a complete use case in its own right if it is not directly triggered by an actor. This relationship is most often used either when some shared functionality is required by several use cases or to abstract out a complex piece of logic.

An atomic requirement is one that is self-contained and can be understood independently of other requirements or designs. It encapsulates a single piece of functionality or a single need without reference to other requirements. This characteristic ensures that the requirement can be considered, implemented, and tested on its own merits. Atomic requirements are essential for clear communication, effective analysis, and traceability throughout the project lifecycle.

Business analysis information can be stored in many ways. Storage decisions depend on many factors such as who must access the information, how often they need to access it, and what conditions must be present for access. Organizational standards and tool availability also influence storage and access decisions. The business analysis approach defines how various tools will be used on the initiative and how the information will be captured and stored within those tools. Tools may shape the selection of business analysis techniques, notations to be used, and the way that information is organized.

The task that uses the 'Elicitation Activity Plan' to draw out, explore, and identify information relevant to the change is 'Conduct Elicitation.' This task involves direct interaction with stakeholders or independent research to understand stakeholder needs and identify potential solutions that may meet those needs. The Elicitation Activity Plan guides the business analyst through the planned elicitation activities, ensuring that the elicitation is focused, efficient, and aligned with the project objectives. This structured approach to elicitation helps in gathering relevant and accurate information, which is essential for the success of the change initiative .