Stakeholder identification method in goal oriented requirements elicitation process

Abstract

In any software project, different stakeholders participate in requirements elicitation process to identify the requirements of software. Stakeholder Identification (SI) is an important part of requirements elicitation process. Despite its importance, SI methods have received less attention by goal oriented requirements engineering (GORE) community. Goals are high level objective of an organization; and are the basis of GORE. In literature, we identify that goal oriented requirements elicitation process (GOREP) like knowledge acquisition for automated specification (KAOS), attributed goal oriented requirements analysis (AGORA), and goal oriented idea generation (GOIG) etc. do not support SI methods. Therefore, to address this issue, we present a method for SI in GOREP which includes the following steps: specify stakeholder types, specify stakeholder roles, selecting and classifying stakeholders using fuzzy based approach, and stakeholder's analysis. Finally, the utilization of the proposed method is demonstrated with the help of an example.

On Fuzzy Qualitative and Quantitative Softgoal Interdependency Graph

“…Primary stakeholders include those who are central to any project initiative, i.e., beneficiaries, financial, politicians, sponsors, and decision maker. Secondary stakeholders include developers, experts, operators etc [19].…”

Prioritizing interdependent software requirements using tensor and fuzzy graphs

“…Several studies investigated requirements prioritization [6,16,17] and focused on several issues such as dependency, scalability, and rank update that scholars face during the process of techniques to tackle requirements prioritization. Furthermore, types of dependencies have been classified as refinement, contribution, and conflict relations in GORE and i* [18,19] by Pohl [4] and Dahlstedt and Persson [20]. Zhang et al [21] divided dependencies into "increase/decrease" value and cost along with business-related relations such as "precedence and concurrence dependencies".…”

Identification of Requirements using Goal Oriented Requirements Elicitation Process

“…On the other hand side, in OR decomposition, the achievement of at least one sub goals or requirements leads to the achievement of its parent goal [18]. The proposed method is presented as follows [1]: (a) Identify stakeholders [18], (b) Identify high level objective of the primary stakeholder using any requirements elicitation technique (See Fig. 1 …”

“…Cognitive technique includes task analysis, protocol analysis, and knowledge acquisition technique etc. Collaborative techniques are used for different activities like selection and prioritization of software requirements [18], detection of discordances among stakeholders etc. In Contextual technique, requirements are identified at the work place of the customer.…”