A systematic literature review of stakeholder identification methods in requirements elicitation

This paper presents a systematic review of relevant published studies related to topics in Requirements Engineering, specifically, concerning stakeholder identification methods in requirements elicitation, dated from 1984 to 2011. Addressing four specific research questions, this systematic literature review shows the following evidence gathered from these studies: current status of stakeholder identification in software requirement elicitation, the best practices recommended for its performance, consequences of incorrect identification in requirements quality, and, aspects which need to be improved. Our findings suggest that the analyzed approaches still have serious limitations in terms of covering all aspects of stakeholder identification as an important part of requirements elicitation. However, through correctly identifying and understanding the stakeholders, it is possible to develop high quality software.

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

[2]  Forrest Shull,et al.  Using the ISO/IEC 9126 product quality model to classify defects: A controlled experiment , 2012, EASE.

[3]  Ivar Jacobson,et al.  A New Software Engineering , 2014, ACM Queue.

[4]  Nan Niu,et al.  On-Demand Cluster Analysis for Product Line Functional Requirements , 2008, 2008 12th International Software Product Line Conference.

[5]  Nancy R. Mead,et al.  Requirements engineering in practice: making the business case for requirements engineering , 2003, Proceedings. 11th IEEE International Requirements Engineering Conference, 2003..

[6]  Natalia Juristo Juzgado,et al.  Effectiveness of Requirements Elicitation Techniques: Empirical Results Derived from a Systematic Review , 2006, 14th IEEE International Requirements Engineering Conference (RE'06).

[7]  Des Greer,et al.  Software release planning: an evolutionary and iterative approach , 2004, Inf. Softw. Technol..

[8]  Sooyong Park,et al.  Using classification techniques for informal requirements in the requirements analysis-supporting system , 2007, Inf. Softw. Technol..

[9]  Milena M. Parent,et al.  A Case Study of Stakeholder Identification and Prioritization by Managers , 2007 .

[10]  Ian Sommerville,et al.  Software engineering (6th ed.) , 2001 .

[11]  Barbara Kitchenham,et al.  Procedures for Performing Systematic Reviews , 2004 .

[12]  Natalia Juristo Juzgado,et al.  Systematic review and aggregation of empirical studies on elicitation techniques , 2011, IEEE Transactions on Software Engineering.

[13]  Fabio Q. B. da Silva,et al.  Motivation in software engineering: A systematic review update , 2011, EASE.

[14]  Dennis Linscomb.  Requirements Engineering Maturity in the CMMI , 2022 .

[15]  Edmundo Tovar,et al.  Stakeholder Identification as an Issue in the Improvement of Software Requirements Quality , 2007, CAiSE.

[16]  J. Fleiss.  Measuring nominal scale agreement among many raters. , 1971 .

[17]  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).

[18]  Luciana C. Ballejos,et al.  Stakeholders Selection for Interorganizational Systems: A Systematic Approach , 2006, IFIP TC8 WCC ISS.

[19]  Zhen He,et al.  The requirements engineering process model based on design for six sigma , 2010, 2010 2nd IEEE International Conference on Information Management and Engineering.

[20]  R. Singh.  Harmonization of software engineering and system engineering standards , 1995, Proceedings of Software Engineering Standards Symposium.

[21]  Richard W. Woolridge,et al.  Co-adaptive processes of stakeholder networks and their effects on information systems specifications , 2011, SIGMIS-CPR '11.

[22]  Mattias Holmgren,et al.  A process view of maintenance and its stakeholders , 2007 .

[23]  Luciana C. Ballejos,et al.  A Stakeholder Model for Interorganizational Information Systems , 2008, REFSQ.

[24]  Haruhiko Kaiya,et al.  Identifying stakeholders and their preferences about NFR by comparing use case diagrams of several existing systems , 2004, Proceedings. 12th IEEE International Requirements Engineering Conference, 2004..

[25]  Didar Zowghi,et al.  Teaching requirements engineering through role playing: lessons learnt , 2003, Proceedings. 11th IEEE International Requirements Engineering Conference, 2003..

[26]  Motoshi Saeki,et al.  Goal-oriented idea generation method for requirements elicitation , 2003, Proceedings. 11th IEEE International Requirements Engineering Conference, 2003..

[27]  Daniele Quercia,et al.  StakeNet: using social networks to analyse the stakeholders of large-scale software projects , 2010, 2010 ACM/IEEE 32nd International Conference on Software Engineering.

[28]  Marta López,et al.  Updating a Systematic Review about Selection of Software Requirements Elicitation Techniques , 2008, WER.

[29]  S. Lauesen.  Software Requirements Styles and Techniques , 2001 .

[30]  J. Barrie Thompson,et al.  Quality and people in the development of situationally specific methods , 2001, Proceedings Second Asia-Pacific Conference on Quality Software.

[31]  Peter J. Bentley,et al.  Evolving relationships between social networks and stakeholder involvement in software projects , 2011, GECCO '11.

[32]  Daniela E. Damian,et al.  Stakeholders in Global Requirements Engineering: Lessons Learned from Practice , 2007, IEEE Software.

[33]  Athanasia Pouloudi,et al.  Stakeholder analysis as a front-end to knowledge elicitation , 1997, AI & SOCIETY.

[34]  Tore Dybå,et al.  Evidence-based software engineering , 2004, Proceedings. 26th International Conference on Software Engineering.

[35]  Klaas Sikkel,et al.  A systematic mapping study on empirical evaluation of software requirements specifications techniques , 2009, 2009 3rd International Symposium on Empirical Software Engineering and Measurement.

[36]  Y. Fassin,et al.  Faculteit Economie En Bedrijfskunde Tweekerkenstraat 2 B-9000 Gent the Stakeholder Model Refined , 2022 .

[37]  Joaquín Nicolás,et al.  On the generation of requirements specifications from software engineering models: A systematic literature review , 2009, Inf. Softw. Technol..

[38]  Paul Grünbacher,et al.  System dynamics modelling and simulation of collaborative requirements engineering , 2001, J. Syst. Softw..

[39]  Vasundhara Kulkarni.  A Conceptual Model for Capturing Stakeholders' Wish List , 2008, 2008 International Conference on Computer Science and Software Engineering.

[40]  Roger S. Pressman,et al.  Software Engineering: A Practitioner's Approach , 1982 .

[41]  Stefan Biffl,et al.  An economic approach for improving requirements negotiation models with inspection , 2003, Requirements Engineering.

[42]  Shou-De Lin,et al.  StakeNet: Devise, Study and Utilize Social Networks Using Stakeholder Information , 2010, 2010 International Conference on Technologies and Applications of Artificial Intelligence.

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

[44]  S. R. Jernigan,et al.  Hybrid Domain Representation Archive (HyDRA) for requirements model synthesis across viewpoints , 2000, Proceedings of the 2000 International Conference on Software Engineering. ICSE 2000 the New Millennium.

[45]  A Straw,et al.  Guide to the Software Engineering Body of Knowledge , 1998 .

[46]  Roel Wieringa,et al.  Guest Editors' Introduction: Stakeholders in Requirements Engineering , 2007, IEEE Software.

[47]  J Bosch.  ICSE 2004: 26TH INTERNATIONAL CONFERENCE ON SOFTWARE ENGINEERING, PROCEEDINGS , 2004 .

[48]  Peter Sawyer,et al.  Identifying tacit knowledge-based requirements , 2006, IEE Proc. Softw..

[49]  Elayne Coakes,et al.  Focus issue on legacy information systems and business process engineering: the role of stakeholders in managing change , 1999 .

[50]  Haruhiko Kaiya,et al.  Improving the detection of requirements discordances among stakeholders , 2005, Requirements Engineering.

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

[52]  Mark T True,et al.  Software Requirements , 2005 .

[53]  Jorge J. Gómez-Sanz,et al.  Understanding the human context in requirements elicitation , 2010, Requirements Engineering.

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

[55]  Robert D. Macredie,et al.  Effective Communication in Requirements Elicitation: A Comparison of Methodologies , 2002, Requirements Engineering.

[56]  Edward Yourdon,et al.  OUTSOURCE: Competing in the Global Productivity Race , 2004 .

[57]  Ronald K. Mitchell,et al.  Toward a Theory of Stakeholder Identification and Salience: Defining the Principle of who and What Really Counts , 1997 .

[58]  J. Barrie Thompson,et al.  PisoSIA® a stakeholder approach to assist change in information systems development projects and aid process improvement , 2006, Software Quality Journal.

[59]  Pearl Brereton,et al.  Performing systematic literature reviews in software engineering , 2006, ICSE.

[60]  Franz Lehner,et al.  Requirements Engineering as a Success Factor in Software Projects , 2001, IEEE Softw..

[61]  Helen Sharp,et al.  Motivation in Software Engineering: A systematic literature review , 2008, Inf. Softw. Technol..

[62]  Ala Abu-Samaha,et al.  Eliciting Web application requirements - an industrial case study , 2007, J. Syst. Softw..

[63]  Paulo Rupino da Cunha,et al.  Who are the Players? Finding and Characterizing Stakeholders in Social Networks , 2010, 2010 43rd Hawaii International Conference on System Sciences.

[64]  Gary Ford,et al.  Lecture Notes on Requirements Elicitation , 1994 .

[65]  Luciana C. Ballejos,et al.  Method for stakeholder identification in interorganizational environments , 2008, Requirements Engineering.

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

[67]  Hoh Peter In,et al.  Visualization issues for software requirements negotiation , 2001, 25th Annual International Computer Software and Applications Conference. COMPSAC 2001.

[68]  Daniele Quercia,et al.  StakeSource: harnessing the power of crowdsourcing and social networks in stakeholder analysis , 2010, 2010 ACM/IEEE 32nd International Conference on Software Engineering.

[69]  Tom Rodden,et al.  Human factors in requirements engineering: A survey of human sciences literature relevant to the improvement of dependable systems development processes , 1999, Interact. Comput..

[70]  Anthony Finkelstein,et al.  Ieee Transactions on Software Engineering, Manuscript Id Stakerare: Using Social Networks and Collaborative Filtering for Large-scale Requirements Elicitation , 2022 .

[71]  Jaime Arguello,et al.  A bootstrapping approach for identifying stakeholders in public-comment corpora , 2007, DG.O.

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

[73]  Denise Johnson McManus,et al.  Stakeholder Risk Assessment: An Outcome-Based Approach , 2007, IEEE Software.

[74]  Bashar Nuseibeh,et al.  Requirements engineering: a roadmap , 2000, ICSE '00.

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

[76]  Ban Al-Ani,et al.  An empirical study of a Qualitative Systematic Approach to Requirements Analysis (QSARA) , 2004, Proceedings. 2004 International Symposium on Empirical Software Engineering, 2004. ISESE '04..

[77]  Mary Beth Rosson,et al.  Effectiveness of elicitation techniques in distributed requirements engineering , 2002, Proceedings IEEE Joint International Conference on Requirements Engineering.

[78]  Marcos R. S. Borges,et al.  Athena: A collaborative approach to requirements elicitation , 2009, Comput. Ind..

[79]  Betty H. C. Cheng,et al.  Research Directions in Requirements Engineering , 2007, Future of Software Engineering (FOSE '07).

[80]  Pearl Brereton,et al.  Lessons from applying the systematic literature review process within the software engineering domain , 2007, J. Syst. Softw..

[81]  Bernard Wong,et al.  Understanding Stakeholder Values as a Means of Dealing with Stakeholder Conflicts , 2005, Software Quality Journal.

[82]  Z.M. Kasirun,et al.  Focus Group Discussion Model for Requirements Elicitation Activity , 2008, 2008 International Conference on Computer and Electrical Engineering.

[83]  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.

[84]  Claus Pahl,et al.  Adaptive development and maintenance of user-centric software systems , 2004, Inf. Softw. Technol..

[85]  Anastasia Papazafeiropoulou,et al.  How Stakeholder Analysis can be Mobilized with Actor-Network Theory to Identify Actors , 2004, Relevant Theory and Informed Practice.