Learning about the environment in which the new product will be used.

Understanding the relative importance of quality attributes.

Negotiating implementation priorities.

Decomposing high-level RQs into an appropriate level of detail.

Working with individuals who represent each user class to understand their functionality needs and their quality expectations.

Translating the collected user needs into written requirements and diagrams suitable for comprehension, review, and use by their intended audiences.

Deriving functional RQs from other requirements information.

Identifying gaps in RQs or unnecessary RQs as they relate to the defined scope.

Understanding user tasks and goals and the business objectives with which those tasks align.

Identifying the product’s expected user classes and other stakeholders.

Allocating RQs to software components defined in the system architecture.

Analyzing users' information to distinguish task goals from functional RQs, quality expectations, business rules, suggested solutions, and other information.