Abstract
Stakeholders identification is a critical task for successful software projects. In general, there are no methodologies that allow performing it in a systematic way. Besides, several facts must be analyzed when the project is carried out in a context formed by multiple organizations. The complexity of these environments makes the task extremely hard. To face these difficulties, stakeholders are defined and analyzed taking into account the characteristics of the interorganizational dimension. Also a methodology is proposed for canying out their identification that allows systematically specifying all people, groups and organizations whose interests and needs are affected by the information system in all the involved dimensions.
Chapter PDF
Similar content being viewed by others
Keywords
- National Health Service
- Requirement Engineer
- Versus Versus Versus Versus Versus
- Requirement Elicitation
- Stakeholder Analysis
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.
References
K. Bittner, I. Spence, Establishing the Vision for Use Case Modeling, Use Case Modeling, Addison Wesley Professional, 2003.
A. Pouloudi, R. Gandecha, A. Papazafeiropoulou, C. Atkinson, How Stakeholder Analysis can Assist Actor-Network Theory to Understand Actors. A Case Study of the Integrated Care Record Service (ICRS) in the UK National Health Service, Eltrun Working Paper Series, WP 2004-002,2004.
J. Giesen, A. Völker, Requirements Interdependencies and Stakeholders Preferences, IEEE Joint International Conference on Requirements Engineering (RE’02), 2002.
B. Nuseibeh, S. Easterbrook, Requirements Engineering: A Roadmap, ICSE, Conference on The Future of Software Engineering, 2000, pp. 35–46.
G.S.C. Pan, Information Systems Project Abandonment: A Stakeholder Analysis, International Journal of Information Management, 25(2), 2005, pp. 173–184.
A. Papazafeiropoulou, A. Pouloudi, A. Poulymenakou, Electronic Commerce Competitiveness in the Public Sector: The Importance of Stakeholder Involvement, Int. J. of Services Technology and Management, 3(1), 2002, pp. 82–95.
A. Pouloudi, Aspects of the Stakeholder Concept and their Implications for Information Systems Development, 32 Annual Hawaii International Conference on System Sciences. 1999.
H. Sharp, A. Finkelstein, G. Galal, Stakeholder Identification in the Requirements Engineering Process, DEXA Workshop1999, pp. 387–391.
G. Kotonya, I. Sommerville, Requirements Engineering: Processes and Techniques, J. Wiley & Sons Eds. 2003.
D. Chatterjee, T. Ravichandran, Inter-organizational Information Systems Research: A Critical Review and an Integrative Framework, 37th Hawaii International Conference on System Sciences, 2004.
A. Pouloudi, E.A Whitley, Stakeholder Identification in Inter-Organizational Systems: Gaining Insights for Drug Use Management Systems, European Journal of Information Systems,6, 1997, pp. 1–14.
J. Coughlan, R.D. Macredie, Effective Communication in Requirements Elicitation: A Comparison of Methodologies, Requirements Engineering Journal, 7,2002, pp. 47–60.
J. Jonker, D. Foster, Stakeholder Excellence? Framing the Evolution and Complexity of a Stakeholder Perspective of the Firm, Corporate Social Responsibility and Environmental Management, 9,2002, pp. 187–195.
G. Khalifa, Z. Irani, L.P Baldwin, S. Jones, Evaluating Information Technology With You in Mind, Electronic Journal of Information Systems Evaluation, 4(1), 2001.
P. Gruenbacher, Integrating Groupware and CASE Capabilities for Improving Stakeholder Involvement in Requirements Engineering, Euromicro Workshop on Software Process and Product Improvement at 26th Euromicro Conference, 2000, pp. 2232–2239.
I.F. Alexander, A Better Fit-Characterising the Stakeholders, Requirements Engineering for Business Process Support (REBPS) 2004 Workshop, CAISE’04,2004.
A. Kelvin, How stakeholders with various preferences converge on acceptable investment programs, Journal of Evaluation and Program Planning, 23,2000, pp. 105–113.
J. Ropponen, K. Lyytinen, Components of Software Development Risk: How to Address Them?A project Manager Survey, IEEE Transactions on Software Engineering, 26(2), 2000.
V. Shankar, G.L. Urban, F. Sultan, Online trust: a stakeholder perspective, concepts, implications and future directions, J. of Strategic Information Systems, 11,2002, pp. 325–344.
L. M. Applegate, Stakeholder Analysis Tool, Harvard Business Review, April, 2003.
J. Boutelle, Understanding Organizational Stakeholders for Design Success, Boxes and Arrows, May 2004. Available at: <http://www.boxesandarrows.com/view/understanding> organizational stakeholders for desien success
A. Qualman, A Note on Stakeholder Analysis, Guidance Note on How to Do Stakeholder Analysis of Aid Projects and Programmes. Document prepared by the British Overseas Development Administration (ODA), Social Development Department. July 1995.
L.W. Smith, Project Clarity Through Stakeholder Analysis, CrossTalk, The Journal of Defense Software Engineering. December, 2000.
National Health Service, in: http://www.connectingforhealth.nhs.uk.
The Go Between Information for Information Users, 54, October, 2003. In: <http://www>. assist.org.uk/Branches/London/the go between/Go-Between%20-%2OISSUE54.pdf
Author information
Authors and Affiliations
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2006 International Federation for Information Processing
About this paper
Cite this paper
Ballejos, L.C., Montagna, J.M. (2006). Stakeholders Selection for Interorganizational Systems: A Systematic Approach. In: Avison, D., Elliot, S., Krogstie, J., Pries-Heje, J. (eds) The Past and Future of Information Systems: 1976–2006 and Beyond. IFIP WCC TC8 2006. IFIP International Federation for Information Processing, vol 214. Springer, Boston, MA . https://doi.org/10.1007/978-0-387-34732-5_4
Download citation
DOI: https://doi.org/10.1007/978-0-387-34732-5_4
Publisher Name: Springer, Boston, MA
Print ISBN: 978-0-387-34631-1
Online ISBN: 978-0-387-34732-5
eBook Packages: Computer ScienceComputer Science (R0)