2022 2nd International Conference on Computing and Information Technology (ICCIT)
Jan. 25 - 27, 2022/ FCIT/UT/KSA
Stakeholder Identification Overview and Challenges
in Requirements Engineering Prospective
Duha Awad Elneel Abdul Sahli Fakharudin
Faculty of Computing, Universiti Faculty of Computing, Universiti
Malaysia Pahang, Kuantan, 26300, Malaysia Pahang, Kuantan, 26300,
Malaysia
duha76@gmail.com sahli@ump.edu.my
Hasan Kahtan
Department of Software Engineering, Faculty of Computer
2022 2nd International Conference on Computing and Information Technology (ICCIT) | 978-1-6654-3605-2/22/$31.00 ©2022 IEEE | DOI: 10.1109/ICCIT52419.2022.9711653
Science and Information Technology, Universiti Malaya, 50603
Kuala Lumpur, Malaysia
hasankahtan@um.edu.my
Abstract—Stakeholder identification (SI) illustrates a
critical part of the requirements elicitation activity. It helps
software analysts gather accurate system requirements to
ensure high quality and avoid system failure. Stakeholder
identification considered one of the earliest stages of project
development. The main problem related to project success and
failure is identifying the real stakeholders and selecting the right
one. The lack of stakeholder identification methodologies and
the shortage of previous research in identifying the stakeholders
for different systems, encourage the research to propose a
guideline framework, assist analysts in building the convenient
methodology for identifying real stakeholders. Stakeholders are
defined based on different projects and the various services they
provide. This difference leads to the fact that a particular and
systematic technique must be used to identify stakeholders
based on the project’s types. The exploration of stakeholder
identification matters and the guideline framework is a baseline
for future research in requirements engineering.
Keywords—Stakeholder Identification, Stakeholder
Identification Methodology, Requirements Engineering.
I. INTRODUCTION
Requirement Engineering (RE) is a group of activities
which consists of gathering, analysis, specification,
validation, and management to extract the right requirements
[1] It is a fundamental process in software development life
cycle [2]. Requirements are the basis of the system
development; thus, RE illustrates the most significant aspect
in the system development life cycle [3].
The fineness of requirements is considered one of the most
critical and fundamental parts of software development
success [4]. Requirements engineering is considered a highly
complicated aspect due to its association with software
development decisions and identification [5].
Requirements elicitation is the essential and challenging
activity of RE; this considerable challenge is associated with
requirements engineering process because the system depends
entirely on the collected, analyzed and realized requirements
at this stage [6] and [7]. Requirement Elicitation is known as
the initial process of requirements engineering and crucially
influential in software development. Gathering real and
accurate requirements from the right stakeholders is the
fundament of this process [8] and [9]. Requirements elicitation
978-1-6654-3605-2/22/$31.00 ©2022 IEEE
Authorized licensed use limited to: Lorenzo Reyes-Chamorro. Downloaded on March 20,2023 at 21:02:15 UTC from IEEE Xplore. Restrictions apply.
Elsadig Musa Ahmed
Faculty of Business, Multimedia
University, Melaka, Malaysia
Malaysia elsadig1965@gmail.com
Mansoor Abdullateef
KNOWBIS SOLUTIONS & CONSULTANCY,
Selangor, Malaysia
hakmansoor@gmail.com
is the capability to labor concurrently with stakeholders to
collect the system requirements and achieve the objectives of
the project to be developed [10].
Stakeholder Identifying is one of the substance processes
of the elicitation phase. Stakeholders are determined based on
their activities in the system [4]. Identifying stakeholders is
challenging and requires considerable focusing [11]. This
significant process requires a delicate study to categorize and
classify the right project stakeholders. The system's effective
development depends on successfully determining the
requirements needed for this system [9]. The right
requirements rely on accurate stakeholders' identification in
the requirements engineering process [12]. Defining incorrect
stakeholders is one of the main factors that lead to system
failures [13]. Stakeholder identification is a process on which
some important and influential activities depend on
requirement prioritization [14] and [15]. Requirements
engineering and elicitation approach still require further
attention and research to identify the importance of identifying
the right stakeholders in the early stage of the project.
The paper is structured as follows. The following section
explores the related work of stakeholder identification.
Section 3 clarifies the methodology applied in this study. In
Section 4, the results of an analysis of the literature are
discussed. The last part of the paper presents the study's
limitations and prospective future research areas. Figure 1
illustrates the stakeholder identification as an essential part of
requirements engineering and requirements elicitation
processes.
Stakeholder
Identification
Requirements
Elicitation
Requirements
Engineering
Fig 1. Stakeholder Identification Overview
314
 2022 2nd International Conference on Computing and Information Technology (ICCIT)
Jan. 25 - 27, 2022/ FCIT/UT/KSA

II. RELATED WORK TABLE I. RESEARCH QUESTIONS RELATED PAST STUDIES

This section aims to give an in-depth review of the Research Questions

Ref
stakeholder identification processes. The paper presents some RQ1 RQ2 RQ3 RQ4 RQ5
questions about stakeholder identification and how they have [19] Y Y Y Y Y
been clarified and answered in several previous research
[3] Y Y Y Y Y
types. Table I summarized the related work and clarified the
research questions. The answer to each question can be yes or [4] Y Y Y Y N
no, which were appointed ‘Y’ for inclusion in the study and
[11] Y Y N Y Y
‘N’ for not implicitly included.
[25] Y Y Y N Y
A. What is stakeholder and stakeholder identification? [20] Y Y Y N N
A stakeholder is a person that affect the system directly or
[24] Y Y Y N N
indirectly through the involvement in the core activities of the
system [11], [16], [17] and [18].[15]. A stakeholder is the [6] Y Y Y Y Y
main source of development process feedback [19], it is
[13] Y Y Y Y N
significant factors that affect system sustainability [3].
Stakeholder appears as an individual or group interest in the [22] Y Y Y Y N
system; they can also be internal or external [4] and [13]
[15] Y Y Y Y Y
classifies it as primary and secondary. Stakeholders work as
partners in requirements elicitation to detect project [26] Y Y Y Y Y
requirements and realize the objectives [20]. There is [21] Y Y Y Y Y
considerable variation of stakeholders from project to another.
Wherefore, an ongoing evaluation of their compatibility with [16] Y Y Y Y Y
the particular project should be undertaken [21]. [23] Y Y Y Y Y
It is fundamental to identify stakeholder in requirements [12] Y Y Y Y Y
elicitation to increase the efficiency and compatibility of
system requirements [11], [16]. Identifying stakeholder is one [27] Y N Y N Y
of the substance processes of the elicitation phase. [18] Y Y Y N N
Stakeholders are determined based on their activities in the
system [4]. Stakeholder identification is a continuous process [34] Y Y Y Y N
because stakeholders change from time to time during system [17] Y Y N Y N
development and require specific skills and management [22].
The stakeholder identification activity turns into complexity if
the stakeholders are located in a different place and have
C. What is the problem of stakeholder identification in RE??
various activities [15]. A project manager is responsible for
determining the real stakeholders by identifying influential The limitation of involving stakeholders in early
and influenced by the system [6]. The stakeholder development stages is system failure; the stakeholder must
identification process for the requirements elicitation is participate during the whole software process [3]. Delaying
unorganized and ambiguous [23]. the identification of stakeholders and missing main
stakeholders is a key factor leading to system failure [6], [13]
B. What is the impact of stakeholders in the RE? and [23]. The major issue that may influence the elicitation
process is incompatibility amongst stakeholders [4]. Variation
Stakeholder aspect is an essential factor that influences the thoughts and practices of stakeholders and requirements
requirements elicitation process [20]. Stakeholders have not a engineers are making a disagreement in the system. Little
similar weight and effect; thus, it is important to identify their experience is the basis of many mistakes [1]. Defining
appropriateness in the project [24]. Actually, appropriate unsuitable stakeholders leads to gathering conflict
stakeholder identification is a challenging activity that impact requirements that obstruct achieving the system’s goals [18].
system requirements quality [6], [13], [21] and [12]. Divergence of stakeholders in the work area and cultures leads
Stakeholder identification and participation are critical aspects to extract and understand different requirements and interpret
to discover specific system perspectives [25]. The need for needs differently, creating incorrect decisions [12]. Different
stakeholder identification is the most significant for defining stakeholders' characteristics lead to specific conflict
accurate requirements [19] and [3]. More participation of requirements [15] and [18]. Many stakeholders increase the
stakeholders in the elicitation process is remarkable for incompatibility and inconsistency of system requirements
increasing the requirements quality [4]. Proper stakeholder [22]. The delay in selecting stakeholder’s identification
identification in the early stage impacts the requirements methods will postpone stakeholder participation in the
elicitation process enhancement[11]. Omitted critical requirement elicitation process [16]. Using an incorrect
information or identifying improper stakeholders may lead to method to identify stakeholders can lead to inconsistency in
the unsustainable system [1]. Stakeholder identification different aspects[19]. Although its significance, stakeholder
becomes imperative for the customer and the perfect and identification took a little attention in the software system [6]
comprehensive project [15]. Identifying stakeholders with and [26]. The inconsistency in researchers' theoretical
proper factors like stakeholders' functions, awareness, and methods has made the stakeholder identification process
interaction skills strongly impact the requirements elicitation complex and unclear [27].
phase [23] [17].

315

Authorized licensed use limited to: Lorenzo Reyes-Chamorro. Downloaded on March 20,2023 at 21:02:15 UTC from IEEE Xplore. Restrictions apply.
 2022 2nd International Conference on Computing and Information Technology (ICCIT)
Jan. 25 - 27, 2022/ FCIT/UT/KSA

D. How to involve the stakeholders in the RE? III. METHODOLOGY

Constant communication with stakeholders is the This study aims to determine the significance of the
dominant method to remove the interaction gap. Stakeholders stakeholder identification process and propose a guideline
and developers must be existing in the same place to improve framework helping analysts create a proper methodology. A
system activities[19]. The elicitation technique helps identify focused literature review was conducted using Google Scholar
stakeholder [3] and [4]. The project manager and developing academic search engine as a searchable database of scholarly,
team are responsible for using certain criteria or techniques to IEEE explore, ACM, Springer, Elsevier and some open access
identify real stakeholders [22] and [15]. Using an effective journals and books. The investigation starts with selecting the
technique for identifying the right stakeholders is proper [6]. topic, analyzing, interpreting and coming out with the research
Table II discusses some existing methodologies for gap. After the deep analysis, the researchers used the SPIDER
stakeholder identification and compares them for further focus tool (sample-phenomenon of interest design-evaluation-
and additional work support where 'Y' explains the research type) to formulate the open-end qualitative research
methodology's limitations. questions [35]. The research questions construction also
followed the FINER criteria (Feasible, Interesting, Novel,
TABLE II. STUDY OF SOME STAKEHOLDER IDENTIFICATION Ethical, Relevant), which give an important aid to write real
METHODOLOGIES questions with effective guidance [36]. After arguing the
questions and consecutively answering them, the research's
Ref Type of Validation Application Limitation
methodology method integrated picture was formed..
[28] Framework Case study Early phases Y
of projects 1) What is stakeholder and stakeholder identification?
[29] SIQ Case study Value-Based Y 2) What is the impact of stakeholder identification in the RE?
framework Software and 3) What is the problem of stakeholder identification in the
generically in
the industry
RE?
[30] Matrix tool Case study Smart cities Y 4) How to involve the stakeholders in the RE?
5) What are the future sets of stakeholder identification?
[31] Stakeholder Surveys Higher Y
map education
institutions, The criteria used to select the articles for the literature
business review depending on the previous research questions. The
companies common types of review criteria which have been used are
and the public inclusion and exclusion. The research selected (20) studies of
sector
[32] Method Case study All types of Y
stakeholder identification published between 2012-2020 and
organization (8) SI past methodologies published between 2014-2018. The
[23] Model Survey Useful for Y research was based only on studies written in English. Studies
project included one of the following terms: Stakeholder
managers identification, Stakeholder identification methodologies
[33] Supply Case study Governments, Y (framework, model, process, method, map, matrix).
chain-
businesses,
oriented
process researchers,
and non-
governmental
organizations

E. What are the future sets of stakeholder identification?

Still, there are challenges in the area of stakeholder
identification that researchers need to concern [15] and [27].
Future research is needed to propose a stakeholder
involvement model in agile software development [3].
Traditional RE practices can be combined with agile methods
for preferable achievement[19]. There is a need for exploring
how to propose stakeholder identification standards and
approach measuring techniques to evaluate stakeholders' skills
and knowledge [6]. A systematic review is required to back in
conducting a proper stakeholder’s identification activity [26].
Additional effort is needed to propose a technique or
framework supporting stakeholder identification in the RE
area [21]. More relevant studies should be undertaken to Fig 2. Research Methodology
determine other related factors that facilitate selecting
requirements elicitation techniques [11]. Practitioners can The type of research that suits the research problem is
research how AI techniques can be used in several qualitative research as it usually allows answers to research
requirements elicitation processes [25]. questions like what, how, when and where [37]. To answer the
research questions, the study follows the integrative review

316

Authorized licensed use limited to: Lorenzo Reyes-Chamorro. Downloaded on March 20,2023 at 21:02:15 UTC from IEEE Xplore. Restrictions apply.
 2022 2nd International Conference on Computing and Information Technology (ICCIT)
Jan. 25 - 27, 2022/ FCIT/UT/KSA

methodology that expands stakeholder identification be ensured that all real stakeholders are included. Table III
knowledge. The data analysis of integrative review is not strict represents the major quality attributes affected by the real
with the specific standard [38]. The research utilized the stakeholder identification.
Qualitative Comparison Analysis (QCA) method in Table II,
which is considered an integrative review approach. QCA As shown in RQ3 related work, most of the researchers
works out the previous research and compares the results and touched upon the main problems facing identifying
evaluates their knowledge [39]. QCA supports the in-depth stakeholder that will greatly affect the development and
review by analyzing and comparing the previous stakeholder continuity of the system. This can be summarized in Figure 3.
identification methodologies using some variables such as Many methods can be followed to include stakeholders
type of methodology, steps, application and limitation, which from the first stages in gathering the requirements, as
prom ote to come out with the proposed guideline framework. explained in the RQ4 through some research papers.
Based on [38] study of literature review methodologies Figure Nevertheless, choosing the appropriate method depends on
2 explains the integrative review approach. several factors such as project definition, stakeholder type,
stakeholder role, stakeholder knowledge and interest.
IV. RESULTS AND DISCUSSION
Returning to Table I, the stakeholder identification
This paper discusses the imperative of identifying methodologies are selected according to the type of project
stakeholders, which plays a key role in system success and and its characteristics. It does not matter if the analyst selects
sustainability. Researchers and practitioners certainly need any identification methodology (model, framework, method,
considerable attention because they did not find enough process) as long as it performs the required objective.
interest in previous studies. By referring to the RQ1, the Regarding the steps that are followed to define the
researchers concluded that most of researches define the stakeholder, each method differs according to the project
stakeholder as the person who influences and is affected by scope and requirements. There are many methods for
the specific system. It is the main source of gathering the real evaluating methodologies to ensure that the accurate results
requirements that make it the fundamental factor in building a are achieved, and the selection of the method depends on the
reliable project, achieving the objectives, and ensuring the type of project. There are many limitations related to each
system's continuity and stability. The different projects tasks method, which helps the upcoming researchers avoid this
fully confirm the different stakeholders, and this means that shortage and improve it.
each project has a specific way of identifying its own TABLE III. QUAIITY ELEMENTS AFFECTED BY STAKEHOLDER
stakeholders. Stakeholders are not fixed in a particular project. IDENTIFICATION
Others are joining the system at different stages; therefore,
Elements The influence of stakeholder
identifying the stakeholder process should be reviewed identification
periodically and integrated into the system. Requirements quality Reliable, available, consistent
and reusable requirements will
be gathered.
System functionality There will be a suitable product,
compliance and accurate
results.
System reliability The system function will
perform properly with high
integrity and recoverability.
System Performance There will be interconnection
and sequence between the
system's functions, and the
system will perform its
functions perfectly in the
required time.
System Usability The system will be easy to use,
confident and flexible.
System sustainability The three dimensions of
sustainable development will be
achieved: economic
Sustainability, environmental
sustainability, social
Fig 3. Stakeholder Identification Problem sustainability.
The different projects tasks fully confirm the different
stakeholders, and this means that each project has a specific After answering all the research questions and discussing the
way of identifying its own stakeholders. Stakeholders are not previous methodologies, the guidance steps were formed to
fixed in a particular project. Others are joining the system at solve some problems of specifying and developing adequate
different stages; therefore, identifying the stakeholder process techniques to identify the stakeholders. Fig 4 states the eight
should be reviewed periodically and integrated into the guidance steps.
system. The findings of RQ2 display that all researchers agree Finally, the stakeholder identification process is not
that defining the real stakeholder leads to developing a system conducted easily or randomly. There is an urgent need to
with high efficiency and stability, which is the main goal of identify stakeholders in an orderly manner that ensures the
developing all systems. Delay in identifying some of the system's continuity, quality, and sustainability. The Q5
stakeholders or missing some of them would delay the system clarifies the researchers' future recommendations regarding
development plan and change cost and time. Therefore, it must identifying stakeholders and the techniques that may be

317

Authorized licensed use limited to: Lorenzo Reyes-Chamorro. Downloaded on March 20,2023 at 21:02:15 UTC from IEEE Xplore. Restrictions apply.
 2022 2nd International Conference on Computing and Information Technology (ICCIT)
followed in the future. Further research on this topic will
enable us to find the perfect methodologies to solve this
problem.
Fig 4. Guideline Framework for Developing Stakeholder Identification
Methodology
V. CONCLUSION AND IMPLICATIONS
Stakeholder identification is a substantial aspect that
affects the requirements engineering process. There are
several reasons why software projects fail so commonly. One
of the major reasons is inappropriate stakeholder identification
and selecting techniques during the requirements elicitation
phase. This paper focused on exploring related research using
previous studies. According to the comprehensive
investigation, this study concluded several important steps. It
formulated them into a guideline framework to be considered
by analysts and researchers when constructing an accurate
method for defining the appropriate stakeholder for any
project.
This paper opens new prospects for additional studies in
stakeholder identification in agile requirement engineering.
The variation of studies can be considered to investigate
stakeholder identification's impact on system quality and
continuity. There is a possibility of considering how to map
the stakeholder identification criteria with specific techniques
in future work. Moreover, specific dealings to evaluate
stakeholders' knowledge and communication skills may also
need to keep in mind. Since this research depends on the part
of research sources, there is a little limitation in the probability
of incomplete research. However, researchers and
practitioners can still rely on other relevant research.
REFERENCES
[1] Burnay, C., Jureta, I.J., and Faulkner, S.: “What stakeholders will or
will not say: A theoretical and empirical study of topic importance in
Requirements Engineering elicitation interviews,” Information
Systems, Vol. 46, pp. 61-81, 2014.
318
Authorized licensed use limited to: Lorenzo Reyes-Chamorro. Downloaded on March 20,2023 at 21:02:15 UTC from IEEE Xplore. Restrictions apply.
Jan. 25 - 27, 2022/ FCIT/UT/KSA
[2] Okesola, O.J., Okokpujie, K.O., Goddy-Worlu, R., Ogunbanwo, A.,
and Olamma, I.: “Qualitative Comparisons of Elicitation Techniques
in Requirement Engineering,” QUALITATIVE COMPARISONS OF
ELICITATION TECHNIQUES IN REQUIREMENT
ENGINEERING, Vol. 14, no. 2, pp. 565-570, 2019.
[3] Schön, E.-M., Thomaschewski, J., and Escalona, M.J.: “Agile
Requirements Engineering: A systematic literature review,”
Computer Standards & Interfaces, Vol. 49, pp. 79-91, 2017.
[4] Bani-Salameh, H.: “Towards a comprehensive survey of the
requirements elicitation process improvements,” in Editor (Ed.) ^
(Eds.): ‘Book Towards a comprehensive survey of the requirements
elicitation process improvements’ (ACM, 2015, edn.), pp. 1-6, 2015.
[5] Pacheco, C., García, I., and Reyes, M.: “Requirement elicitation
techniques: a systematic literature review based on the maturity of the
techniques,” IET Software, Vol. 12, no. 4, pp. 365-378, 2018.
[6] Anwar, F., and Razali, R.: “A practical guideline of selecting
stakeholders for requirements elicitation-an empirical study,” in Proc.
Int. J. Softw. Eng. Appl, Vol. 9, no. 2, pp. 95-106, 2015.
[7] Rafiq, U., Bajwa, S.S., Wang, X., and Lunesu, I.: “Requirement
elicitation techniques applied in software startups,” in Editor (Ed.) ^
(Eds.): ‘Book Requirements elicitation techniques applied in software
startups’ pp. 141-144, 2017.
[8] Khan, S., Dulloo, A.B., and Verma, M.: “Systematic review of
requirement elicitation techniques,” India, 2014.
[9] Konaté, J., Sahraoui, A.E.K., and Kolfschoten, G.L.: “Collaborative
requirements elicitation: A process centred approach,” Group
Decision and Negotiation, Vol. 23, no. 4, pp. 847-877, 2014,
[10] Wong, L.R., Mauricio, D.S., and Rodriguez, G.D.: “A systematic
literature review about software requirements elicitation,” J Eng Sci
Technol, Vol. 12, no. 2, pp. 296-317, 2017.
[11] E. Joseph, “Survey on Requirement Elicitation Techniques: It’s Effect
on Software Engineering,” in Proc. International Journal of Innovative
Research in Computer and Communication Engineering, Vol. 5, no.5,
pp. 9201- 9215, 2017.
[12] Babar, M.I., Ghazali, M., and Jawawi, D.N.: ‘A Bi-metric and Fuzzy
c-means Based Intelligent Stakeholder Quantification System for
Value-based Software,” in New Trends in software methodologies,
tools & Technique, pp. 295-309, 2014.
[13] Anwar, F., and Razali, R.: “A systematic stakeholders and techniques
selection framework for software requirements elicitations,” Journal
of Theoretical and Applied Information Technology, Vol. 96, no. 16,
pp. 5458-5472, 2018.
[14] Hujainah, F., Bakar, R.B.A., Abdulgabber, M.A., and Zamli, K.Z.:
“Software Requirements Prioritisation: A Systematic Literature
Review on Significance, Stakeholders, Techniques and Challenges,”
IEEE Access, Vol. 6, pp. 71497-71523, 2018.
[15] Suganya, S.A. Mary, “Requirements Prioritization–Stakeholder
Identification and Participation,” International Journal of Applied
Engineering Research, Vol. 10, no. 344, pp. 27230-27233, 2015.
[16] Burnay, C., Jureta, I., and Faulkner, S.: ‘How Stakeholders'
Commitment May Affect the Success of Requirements Elicitation,” in
Proc. 27th International Conference on Software Engineering and
Knowledge Engineering, pp. 336-341, 2015.
[17] Dick, J., Hull, E., and Jackson, K.: ‘Requirements engineering’
(Springer, 2017. 2017).
[18] Koelsch, G.: ‘How to Collect Requirements’: “Requirements Writing
for System Engineering,” pp. 211-243, 2016.
[19] Inayat, I., Salim, S.S., Marczak, S., Daneva, M., and Shamshirband,
S.: “A systematic literature review on agile requirements engineering
practices and challenges,” Computers in human behavior, Vol. 51, pp.
915-929, 2015.
[20] Wong, L., and Mauricio, D.: “New Factors That Affect the Activities
of the Requirements Elicitation Process,” Journal of Engineering
Science and Technology, Vol. 13, no.7, pp. 1992-2015, 2018.
 2022 2nd International Conference on Computing and Information Technology (ICCIT)
Jan. 25 - 27, 2022/ FCIT/UT/KSA

[21] Pacheco, C., and Garcia, I.: “A systematic literature review of [39] Thomann, E., and Maggetti, M.: “Designing research with qualitative
stakeholder identification methods in requirements elicitation,” comparative analysis (QCA): Approaches, challenges, and tools,”
Journal of Systems and Software, Vol. 85, no.9, pp. 2171-2181, 2012. Sociological Methods & Research, Vol. 49, no. 2, pp. 356-386, 2020.
[22] Rahman, M.M., Ali, M., Malik, N., Ahmad, M.S., and Asmi, F.:
“Essential Skills for Project Stakeholders Identification:
Sustainability Perspective,” International Journal of Business and
Social Research, Vol. 7, no.8, pp. 43- 55, 2017.
[23] Anwar, F., and Razali, R. “Stakeholder selection model for software
requirements elicitation,” American Journal of Applied Sciences, Vol.
13, no.6, pp. 726-738, 2016
[24] Bormane, L., Gržibovska, J., Bērziša, S., and Grabis, J, “Impact of
requirements elicitation processes on success of information system
development projects,” Information Technology and Management
Science, Vol. 19, no. 1, pp. 57-64, 2016
[25] Sharma, S., and Pandey, S.K.: “Requirement elicitation: Issues and
challenges,” in Proc. International Conference on Computing for
Sustainable Global development, pp. 151-155, 2014.
[26] Majumdar, S.I., Rahman, M.S., and Rahman, M.M.: “Thorny issues
of stakeholder identification and prioritization in requirement
engineering process,” IOSR J. Comput. Eng., Vol. 15, no. 5, pp. 73-
78, 2013.
[27] Bui, V.Q.: “Stakeholder identification in Vietnamese private higher
education institutions,” International Journal of Learning and
Teaching, Vol. 3, no. 1, pp. 57-62, 2017.
[28] Aapaoja, A., and Haapasalo, H.: “A framework for stakeholder
identification and classification in construction projects,” Open
Journal of Business and Management, Vol. 2, no. 1, pp. 43-55.
[29] Babar, M.I., Ghazali, M., Jawawi, D.N., and Zaheer, K.B.:
“StakeMeter: Value-Based stakeholder identification and
quantification framework for value-based software systems,” PloS
one, Vol. 10, no. 3, pp. e0121344, 2015.
[30] Ielite, I., Olevsky, G., and Safiulins, T.: “Identification and
prioritization of stakeholders in the planning process of sustainable
development of the smart city,” in Proc. IEEE 7th International
Conference on Intelligent Computing and Information Systems
(ICICIS), pp. 251-257, 2016.
[31] Kettunen, J.: “Stakeholder relationships in higher education,” Tertiary
Education and Management, Vol. 21, no.1, pp. 56-65, 2015.
[32] Wang, W., Liu, W., and Mingers, J.: “A systemic method for
organisational stakeholder identification and analysis using Soft
Systems Methodology (SSM),” European Journal of Operational
Research, Vol.246, no. 2, pp. 562- 574, 2015.
[33] Fritz, M.M., Rauter, R., Baumgartner, R.J., and Dentchev, N.: “A
supply chain perspective of stakeholder identification as a tool for
responsible policy and decision-making,” Environmental science &
policy, Vol. 81, pp. 63-76, 2018.
[34] Lane, S., O’Raghallaigh, P., and Sammon, D.: “Requirements
gathering: the journey,” Journal of Decision systems, Vol. 25, (sup1),
pp. 302-312, 2016.
[35] Korstjens, I., and Moser, A.: “Series: Practical guidance to qualitative
research. Part 2: Context, research questions and designs,” European
Journal of General Practice, Vol. 23, no. 1, pp. 274-279, 2017.
[36] Harrison, H., Birks, M., Franklin, R., and Mills, J.: “Case study
research: Foundations and methodological orientations,” in Forum
Qualitative Sozial for schung, Vol. 18, no. 1, 2017.
[37] Basias, N., and Pollalis, Y.: “Quantitative and qualitative research in
business & technology: Justifying a suitable research methodology,”
Review of Integrative Business and Economics Research, Vol. 7, pp.
91-105, 2018.
[38] Snyder, H.: “Literature review as a research methodology: An
overview and guidelines,” Journal of Business Research, Vol. 104, pp.
333-339, 2019.

319

Authorized licensed use limited to: Lorenzo Reyes-Chamorro. Downloaded on March 20,2023 at 21:02:15 UTC from IEEE Xplore. Restrictions apply.