Stakeholder Identification Methods in Software Requirements: Empirical Findings Derived from a Systematic Review

One of the key challenges to producing high-quality software is to identify and to understand the software requirements. In the requirements acquisition, one of the crucial parts is the stakeholder identification. This paper reports a systematic review of empirical studies concerning the usefulness of stakeholder identification methods in requirements software, and the subsequential empirical evidence gathered from those studies. The paper findings are presented from two points of view: firstly, the impact of stakeholder identification on software requirements quality, and secondly, practices developed to carry out this task. Also, the present paper aims to describe the studies analyzed uniformly and show their contributions in this field.

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

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

[3]  Karl E. Wiegers,et al.  Software Requirements , 1999 .

[4]  J. T. Lochner The Journal of Defense Software Engineering , 1999 .

[5]  P. Krutchen,et al.  The Rational Unified Process: An Introduction , 2000 .

[6]  Ian Sommerville,et al.  Ingeniería de software , 1988 .

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

[8]  Soren Lauesen,et al.  Software Requirements: Styles & Techniques , 2002 .

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

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

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

[12]  Author $article.title , 2002, Nature.

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

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

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

[16]  Philippe Kruchten The Rational Unified Process - An Introduction, 3rd Edition , 2004, Addison Wesley object technology series.

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

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

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