Requirements elicitation is the action of listing all the specifications and requirements for a software before starting the development. The requirements can be set by the users, customers or even the engineers. This requirements list describe what must be done and what must not be done, also what are the functional and non-functional requirements of the system.
Software requirements specification is the description of the whole software. It not only includes the requirements elicitacion but also a number of possible cases or uses to the program.
Goals:
- Facilitating reviews
- Describing the scope of work
- Providing a reference to software designers (i.e. navigation aids, document structure)
- Providing a framework for testing primary and secondary use cases
- Including features to customer requirements
- Providing a platform for ongoing refinement (via incomplete specs or questions)
This is important to know because it set ups the negotiation between the customer and the developer. Also, it sets and specific and accurate path to follow during the development because it tells you what the customer wants and what are your posibilities or limitations. It can help to decide how to work and which frameworks or tools use. The whole desired model is described by the Software requirements specification. Even tough is not a guide to describe what you need, at least you know where to start and what to do.
Once more, here is another music video, enjoy:
sources:
https://en.wikipedia.org/wiki/Software_requirements_specification
https://en.wikipedia.org/wiki/Requirements_elicitation
