2022
DOI: 10.1109/access.2022.3152073
|View full text |Cite
|
Sign up to set email alerts
|

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

Abstract: 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 System… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
6
0

Year Published

2022
2022
2025
2025

Publication Types

Select...
6

Relationship

2
4

Authors

Journals

citations
Cited by 9 publications
(6 citation statements)
references
References 134 publications
0
6
0
Order By: Relevance
“…Such automated approaches help to significantly minimize and reduce the cost associated with the rationale identification, capturing, retrieving, and managing, hence improving the stakeholder's involvement in the application development. 77 The finding of the proposed CrowdRE-VArg approach shows that the Reddit forum can be used as a rich source for requirements opinions elicitation and rationale mining. It supports requirements elicitation activity by identifying new features or issues.…”
Section: Discussionmentioning
confidence: 98%
See 1 more Smart Citation
“…Such automated approaches help to significantly minimize and reduce the cost associated with the rationale identification, capturing, retrieving, and managing, hence improving the stakeholder's involvement in the application development. 77 The finding of the proposed CrowdRE-VArg approach shows that the Reddit forum can be used as a rich source for requirements opinions elicitation and rationale mining. It supports requirements elicitation activity by identifying new features or issues.…”
Section: Discussionmentioning
confidence: 98%
“…Recently, software engineering researchers have focused on automated mining of rationale information from software artifacts and social media platforms to capture rationale knowledge from textual documents. Such automated approaches help to significantly minimize and reduce the cost associated with the rationale identification, capturing, retrieving, and managing, hence improving the stakeholder's involvement in the application development 77 …”
Section: Discussionmentioning
confidence: 99%
“…In the future, we aim to conduct exploratory research studies on the trusted facet ensured by the software vendors and developers through the end‐user feedback collected from these social media platforms. Another future direction is to identify critical stakeholders 41 in the Google Play Store and prioritize or group 42,43 them based on their severe deceptive review contributions to provide remedies in either blocking, limiting, or restricting them to enhance end‐user trust in the software applications 20 . Another possible future direction is to employ the extended proposed approach in the Internet of Medical Things (IoMTs) to identify the malware that seriously threatens medical software assets, such as abusing critical information, sensitive patient data, and so forth 44–48 .…”
Section: Discussionmentioning
confidence: 99%
“…In the broader context, ISO/IEC 27000 and NIST-CSF play a fundamental role in cybersecurity by offering structured approaches to risk management. These standards are relevant to the wider theme by providing organizations with the necessary tools to identify, assess, and manage cybersecurity risks, contributing to a more secure digital environment [27].…”
Section: Figure 4 Nist Cybersecurity Frameworkmentioning
confidence: 99%
“…Both approaches utilize a security implementation strategy based on risk management and recommendations. Security controls and safeguards are implemented only when identified risks are considered unacceptable, serving as a reference for monitoring ongoing progress [27].…”
Section: Figure 5 Nist-csf and Iso/iec 27001 Similaritiesmentioning
confidence: 99%