Thorny Issues of Stakeholder Identification and Prioritization in Requirement Engineering Process

Identifying the stakeholder in requirement engineering process is one of the critical issues. It performs a remarkable part for successful project completion. The software project largely depends on several stakeholders. Stakeholder identification and prioritization is still a challenging part in the software development life cycle. Most of the time, the stakeholders are treated with less importance during the software deployment. Additionally, there is a lack of attempt to think about the right project stakeholder by the development team. In maximum cases, the stakeholder identification technique is performed incorrectly and there is a lack of attempt to mark out them with priority. Besides, there are so many limitations on the existing processes which are used for identifying stakeholders and setting their priority. These limitations pose a negative impact on the development of software project, which should be pointed out by giving deep concern on it. We are aiming to focus on this typical fact, so that we can figure out the actual problem and current work on identifying stakeholders and setting their priority.

[1]  J. McManus,et al.  A stakeholder perspective within software engineering projects , 2004, 2004 IEEE International Engineering Management Conference (IEEE Cat. No.04CH37574).

[2]  Genevieve Bell,et al.  Techniques for researching and designing global products in an unstable world: a case study , 2004, CHI EA '04.

[3]  Jacob L. Cybulski,et al.  Consensus Making in Requirements Negotiation: the communication perspective , 2005, Australas. J. Inf. Syst..

[4]  Rozilawati Razali,et al.  SELECTING THE RIGHT STAKEHOLDERS FOR REQUIREMENTS ELICITATION: A SYSTEMATIC APPROACH , 2011 .

[5]  Linda A. Macaulay Requirements capture as a cooperative activity , 1993, [1993] Proceedings of the IEEE International Symposium on Requirements Engineering.

[6]  Pete Sawyer,et al.  Requirements Engineering: A Good Practice Guide , 1997 .

[7]  R. Freeman Strategic Management: A Stakeholder Approach , 2010 .

[8]  T. Saaty,et al.  The Analytic Hierarchy Process , 1985 .

[9]  Alain Wegmann,et al.  Stakeholder discovery and classification based on systems science principles , 2001, Proceedings Second Asia-Pacific Conference on Quality Software.

[10]  Mark Lycett,et al.  Communication issues in requirements elicitation: a content analysis of stakeholder experiences , 2003, Inf. Softw. Technol..

[11]  Ivan A. Garcia,et al.  A systematic literature review of stakeholder identification methods in requirements elicitation , 2012, J. Syst. Softw..

[12]  Galal H. Galal-Edeen,et al.  Stakeholder identification in the requirements engineering process , 1999, Proceedings. Tenth International Workshop on Database and Expert Systems Applications. DEXA 99.

[13]  Daniela E. Damian,et al.  StakeSource2.0: using social networks of stakeholders to identify and prioritise requirements , 2011, 2011 33rd International Conference on Software Engineering (ICSE).

[14]  Barry Boehm,et al.  Using the Incremental Commitment Model to Integrate System Acquisition, Systems Engineering, and Software Engineering , 2007 .

[15]  Kamsuriah Ahmad,et al.  Achieving Effective Communication during Requirements Elicitation - A Conceptual Framework , 2011, ICSECS.

[16]  Ian Sommerville,et al.  Requirements Engineering: Processes and Techniques , 1998 .

[17]  Anna Perini,et al.  Facing scalability issues in requirements prioritization with machine learning techniques , 2005, 13th IEEE International Conference on Requirements Engineering (RE'05).

[18]  Suzanne Robertson,et al.  Mastering the Requirements Process , 1999 .

[19]  R. Weber Basic Content Analysis , 1986 .

[20]  Sheetal Girase,et al.  A NEW APPROACH TO REQUIREMENT ELICITATION BASED ON STAKEHOLDER RECOMMENDATION AND COLLABORATIVE FILTERING , 2012 .

[21]  Patrik Berander,et al.  Hierarchical Cumulative Voting (hcv) - Prioritization of Requirements in Hierarchies , 2006, Int. J. Softw. Eng. Knowl. Eng..

[22]  Richard Stevens,et al.  Writing Better Requirements , 2002 .

[23]  Ian F. Alexander,et al.  Understanding project sociology by modeling stakeholders , 2004, IEEE Software.

[24]  R. Mason Challenging strategic planning assumptions , 1981 .