Use of Journey Maps and Personas in Software Requirements Elicitation

Abstract

Requirements elicitation is a fundamental step in a software development process since it is at this stage that the software begins to be designed. In some situations, the problems related to the failure of the software development project are due to an incomplete requirements elicitation, resulting in solutions that do not understand all the necessary functionalities or do not incorporate innovation. Despite the various techniques offered by Requirements Engineering, situations such as the growing application market and the need for innovation further increase the importance of understanding the user’s different needs. In this paper, we investigated how the journey map and personas techniques are being used in requirements elicitation in both the literature and the industry, along with the advantages, disadvantages and challenges of using these techniques. We conducted systematic literature review to identify the personas and journey map techniques used in requirements elicitation in the literature and industry. In addition, we conducted a survey with 52 practitioners (software developers, users and managers) to investigate their perceptions of the use of journey maps and personas techniques in the requirements elicitation phase. Twenty-four primary studies were identified that address journey map and personas techniques in software requirements elicitation. In addition, most respondents stated that using these techniques facilitates understanding the requirements, providing better integration, collaboration and leveling of knowledge among the members of the software development teams. Our findings allow us to conclude that most of the software developers, users and managers that participated in the survey consider that the journey map and personas techniques are effective in helping understand the software requirements to be developed by the development teams.