APPLYING TO STAKEHOLDER IDENTIFICATION METHODS IN REQUIREMENTS ENGINEERING

This paper presents a systematic review of empirical studies in Requirements Engineering, specifically, concerning the usefulness of stakeholder identification methods, and the sub sequential empirical evidence gathered from those studies. The objective of this review is to plot the landscape of current reported knowledge in terms of motivating requirements engineers into producing high-quality software through identifying and understanding the software requirements. In the requirements acquisition, one of the crucial parts is the stakeholder identification. The paper reports experiences with applying the practice of systematic literature review, to the published studies relevant within stakeholder identification. Also, the present paper aims to describe the studies analyzed uniformly and show their contributions in this field.

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

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

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

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

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

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

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

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

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

[10]  Sue A. Conger,et al.  The new software engineering , 1993, notThenot Wadsworth series in management information series.

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

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

[13]  Donald Firesmith.  Requirements Engineering , 2002, J. Object Technol..

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

[15]  Tony Elliman,et al.  Focus Issue on Legacy Information Systems and Business Process Change: The Role of Stakeholders in Managing Change , 1999, Commun. Assoc. Inf. Syst..

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

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

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

[19]  Mik Lamming,et al.  Interactive system design , 1995 .

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

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

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

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

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

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