Stakeholder identification as an issue in the improvement of software requirements quality

16Citations
Citations of this article
30Readers
Mendeley users who have this article in their library.

This article is free to access.

Abstract

Stakeholder identification together with its needs and expectations has been poorly realized in software projects. This is probably because the process is mistakenly viewed as a self-evident task in which direct users and the development team are the only stakeholders. It could also be due to the fact that the identification area can be substituted by opinions or knowledge from other more accessible sources of information. This paper provides a review of stakeholder identification literature and an overview of the state-of-the-art in methods for that purpose, which leads to a number of issues that are important in further research (e.g. developing a methodology). 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. © Springer-Verlag Berlin Heidelberg 2007.

Cite

CITATION STYLE

APA

Pacheco, C., & Tovar, E. (2007). Stakeholder identification as an issue in the improvement of software requirements quality. In Lecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics) (Vol. 4495 LNCS, pp. 370–380). Springer Verlag. https://doi.org/10.1007/978-3-540-72988-4_26

Register to see more suggestions

Mendeley helps you to discover research relevant for your work.

Already have an account?

Save time finding and organizing research with Mendeley

Sign up for free