[Context] Although Requirements Engineering (RE) is recognized as a critical factor for the success of software and systems development projects, RE related issues are still in the top ten root causes of partial or complete project failures. There are multiple reasons why RE is often neglected or poorly conducted: poor knowledge of the RE methods, techniques and tools, entanglement of problems, practitioners having poor soft skills, stakeholders' e ectiveness and engagement decreasing rapidly, just to name a few.[Relevance] We need more attractive and motivational ways to make stakeholders skilled and properly engaged for e ciently achieving all RE activities. The research community indicated that gami cation would be an e ective tool to increase performance, creativity and improve the quality of software products in current organizations. [Research Project] This paper describes a gami ed approach to make RE' methods, tools and activities more attractive and easier to be learned and used, and that based on games' concepts and logic. [Contribution] The research will provides an approach that o ers more games for all RE' activities, and evaluates rigorously their e ectiveness to improve RE' training and RE' application. [Research method] We follow a design science approach to produce RE games. To experiment with the introduction of these games in the academic and industrial elds, the design, evaluation and validation of the methodology will follow three stages : 1) Design a series of RE games, each game tackles a speci c problem and/or activity related to RE; 2) Test each game with BSc or/and MSc students at universities, and experts from real software production organisations; 3) Evaluate the e ectiveness of these games through interviews. [Progress] In a early stage of research (from the begening of 2019), a series of RE games (13 games) are collected, we plan also to perform interviews with RE experts to better adapt and evaluate these games to t their needs, then invent new games that tackles the other RE' activities.
Various de nitions have been assigned to the term Gami cation such as, Deterding et .al \The use of game elements in non-game contexts" [det2011]. Kapp et .al \gami cation is using game-based mechanics, aesthetics and game thinking to engage people, motivate action, promote learning, and solve problems" [Kapp2012]. Gami cation is increasingly used for training. Indeed, games are recognized as an e ective mechanism to achieve deep learning and help students retain information [Alexander2008]. This approach has considerable attention by research and industrial communities in di erent areas such as Health [Lister2014], Automation [Marasco] and many more. In Software Engineering, gami cation has been used for increasing the engagement of developers and improve their results [Pedreira2015]; Allowing organizations to adapt their processes evolution by proposing a business process modeling method based on a simulation role-playing game tool [Santorum2011]; and Creating a more productive developers teams using rewards as a game element by analysing changes introduced by each developer [de2014]. According to the results of these works, we see that gami cation can be a powerful tool to deal with shortcomings and problems of RE. Although RE is a 30 years old science, we still know very little on the most e cient ways to educate, train and motivate RE practitioners during their practice, and our theory is that games have the power to improve that. The goal of this work is to present an approach to increase the employment of gami cation in requirements engineering in order to make its methods, tools and activities more attractive, e cient and easy to use.
The article is organized as follow: Section 2 highlights our research motivations. A short literature overview of requirements engineering games focusing on teaching, training and activities is presented in Section 3. An overview of our proposal is given in section 4. Finally, we discusses our work agenda in order to reach the nal goal in Section 5. 2
The starting point is twofold, from literature review and current practices. The idea of applying gami cation in requirements engineering is still quite young, we still need to make stakeholders more involved in requirement engineering activities. Furthermore, the proposed games presented in Section 3 for gamifying some aspects of requirements engineering is a good starting point, but is not enough. Experiments of these games have indicated that they will not solve all problems of RE. On one side a lot of RE' activities not yet gami ed, the proposed games focus more on requirements elicitation, while there is other RE' activities that could be gami ed such as: analyse, speci cation, validation, etc. In the other side there are some shortcomings in current evaluation practices such as : (1) the lack of evaluation in some primary studies (4 out of 13 games not evaluated), (2) Low number of qualitative and quantitative studies [dos2018]; and (3) the lack a proper technological support, for controlled studies demonstrating reliable positive or negative results of using speci c games in particular educational contexts [Lombriser2016]. Also to achieve better RE practices there are few other important aspects that need to be tackled using games, among those we can list:
Comprehension: The RE knowledge is still not being transmitted e ectively and organizations seem unfamiliar with techniques [Juristo2002], experts need to master (project leaders, functional architects, business analysts, etc) during their missions.
Soft skills: Most requirements engineers and their project managers are not (or not enough) aware of the need for soft skills [Penzenstadler2009], Requirements Analysts need to have a combination of technical and soft skills such as empathy, creativity, listening, analytical thinking, con dence, ability to convince, con ict resolution, perseverance, quality of expression to conduct e ective requirements elicitation interviews [Bano2018]. We need more dynamic and motivational ways to assist the teaching of these kind of skills which are not well mastered, in current organizations .
Requirements Documentation: Current techniques used for requirements documentation (e.g. textual representation) are very hard to be communicated, understood or used for the detection and the resolution of con icts [Pinto2014].
Inculture: Many stakeholders actually have a very limited culture on RE and more broadly, software engineering, project management, innovation. \Many recent studies have demonstrated that the traditional methods used in teaching software requirements elicitation are ine ective because they frequently produce unskilled graduates who are inappropriately trained to apply their practical knowledge in the workplace. This is due to ine ectiveness of teaching methods that produces unskilled graduates who are inappropriately trained to apply their practical knowledge in the workplace" [Garcia2019]. We need more attractive ways to improve stakeholder' culture in these domains.
Traceability and communication: Requirements engineering activities especially elicitation has been taught by means of traditional methods they don't focus enough on the most important skills during requirements gathering which are communication and tracability [Zapata2010].
Our vision intends to contribute in reducing these limitations. 3
The use of gami cation to improve stakeholder experience, satisfaction and awareness in requirements engineering has recently received some attention from the research community. Based on an ad-hoc literature review, Figure 1 lists the works we could identify on the topic. As the Figure 1 shows , 2 approaches can be distinguished: (1) Games to improve requirements engineering training and education, and (2) games to increase the engagement of stakeholders in front of requirements engineering practices and activities. For Training and education, a number of games are mainly constructed for (i) academic training, and tested in universities during requirements engineering courses. The goal to make the teaching of RE with more fun and more natural. Among these games : ReGo inspired from the Bingo game that is used to assess students' knowledge about the course topics at the beginning of the course [Alexander2008] ; Q&A&Q (Question, Answer, Question) game where a player answers a question then another player guesses what is the question starting from this answer in a iterative process. This game is used by teachers during requirements elicitation course to help students recognize the di erences and similarities among three primary requirements elicitation methods. It shows how they might disagree on seemingly simple concepts, by providing an opportunity to see how those concepts di er and overlap [Alexander2008]; Biyubi game is role-based game to facilitate the learning of requirements elicitation activities on an undergraduate software engineering course [Garcia2019]; Guess what we want game, that helps requirement`s engineers better understand the importance and impact of their work. In this game players guess a design of the solution starting from requirements that are not well detailed. The real message behind the game is to help students understand following points: (1) the di erent levels of the requirements hierarchy, (2) why detailed requirements are necessary for successful projects, (3) what happens when detailed requirements are not provided to system designers; Communication and traceability game [Zapata2010] is role-based game that aims to reinforce communication and traceability skills used for requirements elicitation process ; In Software Quantums [Knauss2008] game, requirements called quantums that are represented using colored balls and classi ed using bags. It is a simulation game to teach students how to build the right system within the available time .
While these games were designed for university students, another set of games are speci c for experts can be identi ed: the best example is Re-o-Poly game derived from the famous game `monopoly', the goal was to use this game to introduce requirements engineering best practices to novice organisations via managing projects in the game [Smith2007]; also Customized card game for social engineering security that introduced security awareness to di erent employees in order to face security threats [Beckers2016]. Experiments of these games demonstrated that they can contribute to improve the education and the leaning of learners in requirements engineering. Few works tackle requirements engineering activities (elicitation, analyse, prioritization) with the goal to increase the engagement of users doing this activities, and that based on di erent games concepts such as points, badges, levels, stages, etc. As an example CaRuso platform is based on points and levels as a game elements to motivate stakeholders (in particular external users) to contribute to the requirements prioritization process [Kolpondinos2017]; Re ne platform aims at enlarging participation in RE by involving a crowd of both internal and external stakeholders, badges, feedback and points have been used to increase motivation and users' engagement [Snijders2015]; Ithink is designed to stimulate parallel thinking and increase group discussion [Fernandes2012]; JigSaw Puzzle game used during stakeholders' meetings to analyze con icts in the presented requirements. The ultimate goal being to handle these con icts [Pinto2014]. The Planning poker game is currently used in agile projects for requirements prioritization [Haugen2006]. 4
Games could be an e ective tool for (1) engagement: game elements and concepts such as points, badges, chances, fun, etc, may be employed on any system or activity in order to increase the engagement of stakeholders. (2) Culture, questions games or dictionary games could be invented especially as culture games to teach the main concepts of requirements engineering. In addition Games provides playful aspects that could be used to better communicate, understand and resolve con icts in requirements expression for such system [Pinto2014], and for that requirements documentation could be a target using games' artefacts like puzzles or cards. Social game could be invented to develop stakeholders' (4) soft skills, these games would be used for experts during training days. Games also could be used to increase RE (5) comprehension, so gamifying RE methods, techniques and tools should also improve their understanding [Salinesi2015]. For (6) traceability and communication, games could be used to teach social and managerial skills related to these issues that are used for requirements elicitation.
In our approach we aim to follow an iterative process, in a rst step we'll conduct interviews to have a better understanding of the kind of games to use among our games toolbox. We will then collect these games, and invent new ones tackling other activities to increase the prevalence of gami cation in requirements engineering. These games will be tested in their early stages with BSc or/And MSc students within Paris 1 University, then in a controlled environments simulating software production organizations. To achieve more rigorous evaluation we will rely on two methods: (1) feedbacks of players will be measured basing on questionnaires that will be formulated based on some criteria such as real-world relevance, fun factor, participants involvement, intellectual stimulation, knowledge (not chance), etc; (2) GREM [Lombriser2016] model will be used as a rigorous controlled experiment, that is based on a speci c variables and algorithms for accurately measuring some artefacts such as: motivation, emotions, cognition, etc.
The research presented in this paper is based on a number of important underlying assumptions that are formulated starting from the related research studies:
Assumption 1: \Games are used both for the RE activities, but also for related activities such as RE training, or some other activities (business analysis, project management, etc) that require to have RE skills". Assumption 2: \Any activity of RE can be gami ed (elicitation, speci cation, negotiation); as well as any transversal activity of the RE (validation, planning, testing, management,)".
Assumption 3: \Games can be invented especially for RE (such as poker planning), or we can adapt existing games (such as Re-o-Poly, Puzzle)".
The major goal of our research is to construct a generic toolbox that collects the set of games we have found and a few more that we are inventing to improve results of RE phases, get better productivity and engage stakeholders better, this toolbox would be used for (1) requirements engineering education training, and (2) during the practice of requirements engineering activities in industry.
The idea of the project is discussed with many experts in both industrial and academic elds with an encouraging feedbacks. Industrials express the need of these kind of solutions to develop several skills for their employees on one hand, and on the other hand making theme more engaged to realize such activities especially during meetings. In the academic eld, RE' Professors express the importance to adopt this solution in order to increase the motivation and ability of students to RE courses which are abstract and di cult to understand. As mentioned in Section 4, following a design science approach, our initial goal is to understand how we could motivate students and/or experts to achieve better RE training and/or practices using games, we think that interviews will be a good starting point to realize that. This kind of initial discussion will help us to get a more clear idea about the games to use among our toolbox. These games will be tested in their early stages with BSc or/And MSc students within Paris 1 University, then in a controlled environments simulating software production organizations. Finally, to survey the e ectiveness of our solution, more rigorous techniques will be used such as: (1) more qualitative and quantitative studies; (2) rigorous formulated questionnaires ;(3) GREM model. The obtained results will help us to improve these games. Once the e ectiveness of the invented games is evaluated, this toolbox will be delivered to be used in the industry, to improve RE practices and training for experts in software products organization. [Garcia2019] Garcia, Ivan and Pacheco, Carla and Leon, Andres and Calvo-Manzano, Jose A Experiences of using a game for improving learning in software requirements elicitation Computer Applications in Engineering Education, 2019, Wiley Online Library, [Santorum2011] Santorum, Marco Oswaldo and Rieu, Dominique and Mandran, Nadine and others Approche de gestion des processus basee sur les jeux Revue des Sciences et Technologies de l'Information-Serie ISI: Ingenierie des Systemes d'Information, 33{59, 2011, [Haugen2006] Haugen, Nils Christian An empirical study of using planning poker for user story estimation
AGILE 2006 (AGILE'06), 9{pp, 2006, IEEE. [Lombriser2016] Lombriser, Philipp and Dalpiaz, Fabiano and Lucassen, Garm and Brinkkemper, Sjaak International Working Conference on Requirements Engineering: Foundation for Software Quality , 171{187, 2016, Springer.