A Dynamic Stakeholder Classification and Prioritization Based on Hybrid Rough-fuzzy Method

Proposed framework for planning software releases using fuzzy rule‐based system

“…This occurs if the ratio of the complains given by the stakeholders who are classified as high power‐high interest or high power‐low interest to the total numbers of complains given by all stakeholders is greater than or equals a threshold (P1‐Thershold), and these stakeholders complain of one or both of the following cases: The existing software requires new requirements in which the criticality rank of these new requirements is very high or high. The bad services of current software release, and they ask for enhancements. The criticality rank of these enhancements is very high or high. Planning a new release after consultations: The project manager can take a decision for planning a new release but after consulting high‐powered stakeholders [17]. The total number of these stakeholders in the complaint file are greater than or equal a value threshold (≥V‐threshold) regardless of their classification and they are complaining of one or both of the following cases: The current software requires new requirements and ranks the criticality of these new requirements as very high or high.…”

“…According to this change, the framework updates itself with the new values and results may be modified due to this update. To simulate this, during the update faculty website case, stakeholder #11 and stakeholder #23 have received higher position degree (from a lecturer to Associate professor), so their weights will be changed according to the utilised model [17]. Although stakeholder #11 and stakeholder #23 received higher position degree and higher weights but by updating the proposed framework by the new weights, they gave the same solution for first release, second release, and postponed requirements.…”

“…The assignment of each requirement (based on the following release planning modelling factors) is considered the output of the FRBS. Stakeholder priorities: In order to solve the problem of software release planning, a diverse group of stakeholders must be involved and all these stakeholders are not equally important, and they must differ. For the proposed framework presented in this paper, all stakeholders are classified and prioritised according to the model presented in [17]. The output of that model is an accurate stakeholder prioritised list.…”

“…The project manager specifies two cases that may make him/her think of requiring planning a new release. These cases are either planning a new release without consultations or planning a new release after consultation. Planning a new release without consultations: The project manager can take a decision for planning a new release without consulting high‐powered stakeholders, according to Mendelow's power‐interest model; these are the people you must make the greatest efforts to satisfy [17]. This occurs if the ratio of the complains given by the stakeholders who are classified as high power‐high interest or high power‐low interest to the total numbers of complains given by all stakeholders is greater than or equals a threshold (P1‐Thershold), and these stakeholders complain of one or both of the following cases: The existing software requires new requirements in which the criticality rank of these new requirements is very high or high. The bad services of current software release, and they ask for enhancements.…”

“…Planning a new release after consultations: The project manager can take a decision for planning a new release but after consulting high‐powered stakeholders [17]. The total number of these stakeholders in the complaint file are greater than or equal a value threshold (≥V‐threshold) regardless of their classification and they are complaining of one or both of the following cases: The current software requires new requirements and ranks the criticality of these new requirements as very high or high.…”