Requirements analysis structures the output of the elicitation phase (“raw” requirements) into a coherent structure. This structure is a combination of textual descriptions accompanied by some requirements models like class models of use case models. Sometimes the textual descriptions are enriched with tables, matrices or lists.
The process of creating a coherent requirements structure could be split into a number of steps. Firstly BA checks whether requirements are among others consistent, clear and feasible. In order to check that BA can decide to use some additional requirements models. However the requirements analysis is performed by BA, he involves different stakeholders along the way to get more insight into unclear requirements or to resolve some conflict situations. In this step the requirements are organized in a kind of requirements document. Secondly requirements are prioritized. Knowing that the budget and timeline are limited, not all requirements can be implemented. Stakeholders have to indicate what requirements are the most important to them. BA facilitates this process. There are some requirements prioritization techniques, which BA can use, like:
- Kano analysis,
- Density dotting,
- MoSCoW (watch this seminar on usage of MoSCoW),
- Forced pair, or
- The dollar approach.
These techniques will be described in the subsequent sections.