The software requirements get a deal with the needs of the stakeholders, the purpose of those is dealing the things that will be solved with the software.
In the requirements engineering, requirements elicitation is asking the requirements of the software and what happens if this or if that; and with those get answers. Following a good analysis of the requirements. For this reason, we need the stakeholders for getting responses and get a good job.
“discovering, extracting and learning needs of stakeholders, it includes a domain analysis that helps to identify problems and deficiencies in existing systems opportunities and general objectives. Scenarios are part of this activity ” (Christian R. Prause).
The specification of requirements is the description of the behavior of the software, this includes the way that this will develop, and have the interactions that the user will have, and also the functional and nonfunctional requirements.
“Requirements expressed in a more precise way, sometimes as a documentation of the external behavior of the system” (Christian R. Prause).
