Defining the requirements that will increase the satisfaction of stakeholders from the system being created is crucial for the process of acquiring requirements. Implementation of too many functionalities will make the application less intuitive and more difficult to use.
During the process of acquiring requirements, you should choose those requirements that will be crucial for achieving the satisfaction of stakeholders. To determine how the implementation of a given functionality will affect the satisfaction of stakeholders, it is worth using the Kano model.
According to the assumptions of the Kano model, requirements can be divided into three categories determining customer satisfaction:
- Basic requirements
- Desirable requirements
- Exciting requirements
It should be kept in mind that as time goes by, as the user becomes accustomed to the solutions causing excitement, they will change into desirable and basic solutions.
During the acquisition of requirements, all three above-mentioned requirements categories must be considered.
The basic (subconscious) requirements must always be met. Meeting these requirements will not increase the satisfaction of stakeholders from the system being created, but will allow to avoid mass dissatisfaction with this system. The main source of basic requirements are usually operating systems. Acquisition techniques and document-focused techniques can be used to acquire the requirements.
Desirable (conscious) requirements are requirements known and desirable by stakeholders. Implementation of these requirements results in satisfying the users of the system being created, while omitting their implementation may result in the system not being accepted. Any failure to meet this requirement reduces the satisfaction of stakeholders. The research techniques are used to acquire the desired requirements.
Requirements causing excitement
Requirements that cause excitement (unconscious) are requirements that are discovered by stakeholders while working in the system or prototype that is being created, as well as those proposed by the requirements engineer. The best techniques for acquiring the requirements that cause excitement are creative techniques.
NOTE: Exciting requirements are a source of increasing the functional scope of the system. The requirements engineer should identify with stakeholders whether these new requirements affect the project schedule and budget.