This repository contains the supplementary material for the "Perception of developers and users on the use of journey map in software requirements elicitation" article. Abstract: Context: 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 or failure, 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 market for applications and the need for innovation further increase the importance of understanding the user's different needs. Objective: In this paper, we investigated how the personas and journey map techniques are being used in requirements elicitation in both the literature and the industry, along with the positive and negative points of using these techniques. Method: We conducted systematic literature reviews to identify the personas and journey map techniques used in requirements elicitation in the literature and industry. In addition, we conducted semi-structured interviews with 27 software developers to investigate their perception of the use of journeys map and personas techniques in the requirements elicitation phase. Results: Twenty-three 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. Conclusions: Our findings allow us to conclude that most software developers, users, and managers, consider that the journey map and personas techniques are effective in understanding the software requirements to be developed by the development teams.