To identify user groups and figure out their requirements, we first need to define the purpose of the application
A deep and clear analysis can figure out the type of information that needs to get from the investigation.
Survey can measure attitudes, awareness, intent, feedback….user experiences, characteristics of users and over-time comparisons from large user population, with less cost and same time. Thus, survey can be used for gathering the 'swallow' data.
The questions designed for the interview is based on the data collected from the survey.
Interview can be used for Initial exploration, requirements gathering, evaluation and subjective reactions. Thus, details for the data gathered in survey can be fulfilled.
Two types of data should be analyzed
The data from survey and interview is enough for me to understand what users want for a recipe application. So I stop here and start data analysis.
Different Requirement Representations
Usability / User experiences Requirements
The user requirements are categorized in 5 types and each should be evaluated separately. The importance of them depends on the purpose, people (users) and other factors. They can be valued in 4 standards : must have, should have, could have and want have.
Since the data I want to collect is about the user's attitudes, actual experiences, thoughts and feelings, intention of using applications, comparison between existing recipe applications and expectations for the app we are developing from a large amount of user population, I choose to use Survey and Interviews.
More Maps From User
Copy the code to embed this map into your article. The embeded map can even be zoomed in / out