Gamification Strategies for Eliciting Software Requirements

Gasca‐Hurtado, Gloria Piedad; Zepeda, Vianca Vega; Machuca-Villegas, Liliana

doi:10.1007/978-3-030-72660-7_44

Cited by 2 publications

(3 citation statements)

References 29 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Another challenge in the literature review study is that end-users identified for the requirements-related activities do not participate more often when they interact or collaborate to complete certain activities. For this purpose, the gamification approach can improve the overall quality of software applications by efficiently and accurately identifying stakeholders needs and requirements by improving communications, collaboration, participation, and commitment and minimizing conflicts between the stakeholders [149]. Additionally, it is mandatory to assess and evaluate the stakeholders identified for the requirements elicitation activities to ensure that best suited and relevant stakeholders have been shortlisted for the software application to achieve user satisfaction and improve software quality.…”

Section: Discussionmentioning

confidence: 99%

A Comparative Systematic Analysis of Stakeholder’s Identification Methods in Requirements Elicitation

Khan

Assam

et al. 2022

IEEE Access

View full text Add to dashboard Cite

Context and Motivation]Before eliciting and gathering requirements for a software project, it is considered pivotal to know about concerned stakeholders. It becomes hard to elicit the actual system requirements without identifying relevant stakeholders, leading the software project to failure. Despite the paramount importance of stakeholder identification in requirement elicitation, it has been given less attention in the software engineering literature.[Method] For this purpose, we conducted a thorough Systematic Literature Review (SLR) on stakeholder identification (SI) and its methods in requirement elicitation. However, previously, a literature study on SI in the requirement elicitation was conducted. We found that no one has proposed any standard or baseline research method for stakeholder identification, stakeholder assessment, and stakeholder interaction up to date according to our knowledge. It provides an opportunity to update the current SLR on SI in requirements elicitation from 2011 till 2021 to search for a baseline methodology for the SI. For this purpose, we explored the existing literature research that involves the SI methods in requirements elicitation. [Principle Ideas/Results] Furthermore, we identify and capture seventeen research methodologies for SI, eight key stakeholders interaction methods, and ten stakeholders assessment methods in requirement elicitation. To further enhance the stakeholder identification process, we additionally identify pivotal information such as different potential stakeholder categories, stakeholder assessments methods, and stakeholder interaction methods. Also, based on the proposed SLR, we find out the existing gaps and new opportunities for SI methods in the requirement elicitation. [Contribution] These SI methodologies help requirements engineers and practitioners identify key stakeholders and efficiently improve the requirements quality. Moreover, this research study helps identify the effective practices used for the traditional and CrowdRE SI, recover consequences that can affect the effectiveness of SI, and recommend advisable SI practices to be employed in the future. This research study would help the software researchers and developers efficiently and accurately identify correct and concerned stakeholders to improve end-user satisfaction instead of considering it a self-evident task. INDEX TERMS Stakeholder Identification, stakeholder methods, Requirement Elicitation, SLR.

show abstract

Section: Discussionmentioning

confidence: 99%

A Comparative Systematic Analysis of Stakeholder’s Identification Methods in Requirements Elicitation

Khan

Assam

et al. 2022

IEEE Access

View full text Add to dashboard Cite

show abstract

“…Yet in spite of such important significance, there still has been a lack of cooperation among stakeholders. 3 It can be associated with a lack of communication and increased cultural diversity among software stakeholders, and it often leads to inadequate requirements gathering during the software development project. A lack of requirements gathering may result in the implementation of ineffective or wrong features, which would ultimately lead to the failure of the requirements elicitation process.…”

Section: Introductionmentioning

confidence: 99%

“…Requirements lie at the heart of any information system because requirements determine how a system operates. Yet in spite of such important significance, there still has been a lack of cooperation among stakeholders 3 . It can be associated with a lack of communication and increased cultural diversity among software stakeholders, and it often leads to inadequate requirements gathering during the software development project.…”

Section: Introductionmentioning

confidence: 99%

Gamifying requirements: An empirical analysis of game‐based technique for novices

Yasin,

Fatima,

JiangBin

et al. 2023

J Software Evolu Process

View full text Add to dashboard Cite

Requirements elicitation is a process that involves gathering requirements for a given project. Several studies have been published suggesting strategies to improve the requirements gathering process. Using game‐based and crowd‐based approaches, researchers are extracting requirements that are useful for product development today. This study follows the same line of research. This research study aims to improve the understanding of the requirements gathering process by novices or students through different activities: (I) knowledge of requirements gathering method and (II) techniques or activities viable for software requirements (education). Important methods used to address the above objectives are as follows: (I) a comprehensive review of the literature to understand requirements gathering; (II) designing an activity to embed RE challenges and RE sub‐activities; and (III) experiment, survey, and observation to collect data and to assess the proposed methods' effectiveness. The suggested activity for requirement gathering is based on the game tic‐tac‐toe. The participants suggest that the design of the activity is helpful in brainstorming and is also valuable for identifying requirements; moreover, a post questionnaire has been designed to determine the learning of the participants regarding the proposed activity. We can observe simply from the coefficients that both skills and challenges (as perceived by the participants) have positive impacts on engagement, immersion, and perceived learning. The proposed activity helps novices or students gain (basic) knowledge of the requirements gathering process/technique; the outlined activity can be a way of learning requirements and gathering knowledge (basic). From this study, we conclude that the proposed activity has positive results and is helpful for participants to get a better understanding of the requirements engineering method(s).

show abstract

Gamification Strategies for Eliciting Software Requirements

Cited by 2 publications

References 29 publications

A Comparative Systematic Analysis of Stakeholder’s Identification Methods in Requirements Elicitation

A Comparative Systematic Analysis of Stakeholder’s Identification Methods in Requirements Elicitation

Gamifying requirements: An empirical analysis of game‐based technique for novices

Contact Info

Product

Resources

About