...

Expectations of the stakeholders (expressed in any way) are identified. Typically, they are further elaborated and detailed by domain experts and representative users, but it is important not to take their supposed solution or solution method for problem description. Perceived needs are used to identify real needs, which are then clearly expressed, prioritised and selected and real, retained and achievable needs.

Analysis of requirements and their dependencies

The expectations and needs are transformed into requirements while by considering the context, their objectives and feasibility. Requirements are analysed with respect to their relationships and inter-dependencies and whether they truly reflect the specified needs. As people seldom know what they want until they get what they ask for, it may require the use of various information, idea and requirements gathering techniques and even creation of models or prototypes [https://www.sebokwiki.org/wiki/Stakeholder_Needs_and_Requirements].

Traceability of requirements

There is a process for tracking dependencies from the needs to the requirements and among the requirements.

Validation of requirements

Requirements are validated by stakeholders whether to verify if they properly reflect their the needs and expectations.

Design and implementation

...