Enterprise Architecture Stakeholders - a Holistic View

The importance of identifying and managing stakeholders and their needs has been emphasized in literature from various fields, including management, Information Systems (IS), Enterprise Architecture (EA) and Software Architecture (SA). The concept of stakeholder has been extensively discussed especially in management literature, but in the domain of EA, no comprehensive and generalizable view of stakeholders has yet been introduced. In this exploratory study, a holistic and generic view of EA stakeholders is constructed by identifying the stakeholders and their EA-related concerns through an extensive literature review, supplemented and validated by a focus group interview of EA practitioners. Moreover, a classification scheme for the stakeholders is suggested. The results are applicable by a wide range of academics and practitioners alike, potentially in other related contexts as well.

[1]  Kalle Lyytinen,et al.  Information systems failures—a survey and classification of the empirical literature , 1988 .

[2]  Athanasia Pouloudi,et al.  Aspects of the stakeholder concept and their implications for information systems development , 1999, Proceedings of the 32nd Annual Hawaii International Conference on Systems Sciences. 1999. HICSS-32. Abstracts and CD-ROM of Full Papers.

[3]  Barry W. Boehm,et al.  Anchoring the Software Process , 1996, IEEE Softw..

[4]  F. J. Armour,et al.  Building an enterprise architecture step by step , 1999 .

[5]  Hans van Vliet,et al.  The many faces of architectural descriptions , 2006, Inf. Syst. Frontiers.

[6]  Chung-Horng Lung,et al.  A stakeholder-centric software architecture analysis approach , 1996, ISAW '96.

[7]  John F. Sowa,et al.  Extending and Formalizing the Framework for Information Systems Architecture , 1992, IBM Syst. J..

[8]  Kari Smolander,et al.  Four metaphors of architecture in software organizations: finding out the meaning of architecture in practice , 2002, Proceedings International Symposium on Empirical Software Engineering.

[9]  Beate List,et al.  Holistic software process performance measurement from the stakeholders' perspective , 2005, 16th International Workshop on Database and Expert Systems Applications (DEXA'05).

[10]  Nicholas May.  A Survey of Software Architecture Viewpoint Models , .

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

[12]  Farhad Arbab,et al.  Enterprise architecture: Management tool and blueprint for the organisation , 2006, Inf. Syst. Frontiers.

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

[14]  Stephen H. Kaisler,et al.  A UML-driven enterprise architecture case study , 2003, 36th Annual Hawaii International Conference on System Sciences, 2003. Proceedings of the.

[15]  John A. Zachman,et al.  A Framework for Information Systems Architecture , 1987, IBM Syst. J..

[16]  Hans van Vliet,et al.  Polyphony in architecture , 2004, Proceedings. 26th International Conference on Software Engineering.

[17]  Marc M. Lankhorst,et al.  Enterprise Architecture at Work - Modelling, Communication and Analysis, 2nd Edition , 2005, The Enterprise Engineering Series.

[18]  J ArmourFrank,et al.  Building an Enterprise Architecture Step by Step , 1999 .

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

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

[21]  David C. Hay,et al.  Requirements Analysis: From Business Views to Architecture , 2002 .

[22]  Tanja Ylimäki,et al.  POTENTIAL CRITICAL SUCCESS FACTORS FOR ENTERPRISE ARCHITECTURE , 2008 .

[23]  Andrew P. Sage,et al.  A System of Systems Focused Enterprise Architecture Framework and an Associated Architecture Development Process , 2002, Inf. Knowl. Syst. Manag..

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

[25]  Frank S. de Boer,et al.  Change impact analysis of enterprise architectures , 2005, IRI -2005 IEEE International Conference on Information Reuse and Integration, Conf, 2005..

[26]  T. W. Rehkopf,et al.  Top 10 architecture land mines [enterprise] , 2003 .

[27]  David Garlan,et al.  Documenting software architectures: views and beyond , 2002, 25th International Conference on Software Engineering, 2003. Proceedings..

[28]  Matthew R. McBride,et al.  The software architect: essence, intuition, and guiding principles , 2004, OOPSLA '04.

[29]  Paul Clements,et al.  ATAM: Method for Architecture Evaluation , 2000 .

[30]  Donna H. Rhodes,et al.  Enterprise Systems Architecting: Emerging Art and Science within Engineering Systems , 2004 .

[31]  Stephen H. Kaisler,et al.  Enterprise Architecting: Critical Problems , 2005, Proceedings of the 38th Annual Hawaii International Conference on System Sciences.

[32]  Rick Kazman,et al.  An approach to software architecture analysis for evolution and reusability , 1997, CASCON.

[33]  Rick Kazman,et al.  Evaluating Software Architectures: Methods and Case Studies , 2001 .

[34]  Yair Levy,et al.  A Systems Approach to Conduct an Effective Literature Review in Support of Information Systems Research , 2006, Informing Sci. Int. J. an Emerg. Transdiscipl..