Enterprise architecture: critical factors affecting modelling and management

Enterprise architecture is an important instrument to address company-wide integration both from a business and an IT point of view. Companies that choose to implement an Enterprise Architecture initiative often believe that if a description of the company’s architecture exists it will automatically generate value to the company but sadly, this is usually not the case. Even if companies know that enterprise architecture is important they still have problems with modelling and management of the enterprise architecture. The purpose of this article is two fold, to describe how an Enterprise Architecture is established and to identify the critical factors that affect the modelling and management of the Enterprise Architecture. The research is based on empirical study of two different companies: AstraZeneca and SKF. Both companies have several years of experience working with enterprise architectures and represent two completely different branches. The critical factors found are grouped in three different areas: Management, Scope and Content. To succeed with an enterprise architecture initiative it requires top IT and business management buy-in. The scope of the enterprise architecture must be defined and agreed between business and IT. To make the enterprise architecture useful the content must have certain characteristics. To get the buy-in of the business community the business functions and processes must be included and described with relevant artefacts and in business terminology in line with the scope.

[1]  Vassilios Peristeras,et al.  Towards an enterprise architecture for public administration using a top-down approach , 2000, ECIS.

[2]  H. Li,et al.  PERA and GERAM - Enterprise Reference Architectures in Enterprise Integration , 1998, DIISM.

[3]  Marc M. Lankhorst,et al.  Enterprise architecture modelling--the issue of integration , 2004, Adv. Eng. Informatics.

[4]  K. Pessi,et al.  Strategisk IT-management , 1998 .

[5]  Geoff Walsham,et al.  Interpretive case studies in IS research: nature and method , 1995 .

[6]  John A. Zachman,et al.  Enterprise Architecture: The Issue of the Century , 2001 .

[7]  Petter Gottschalk,et al.  Studies of key issues in IS management around the world , 2000, Int. J. Inf. Manag..

[8]  Steven C. Hill,et al.  Enterprise Architecture Planning: Developing a Blueprint for Data, Applications and Technology , 1993 .

[9]  Gordon B. Davis,et al.  Three stage model of MIS planning , 1983, Inf. Manag..

[10]  Pedro Manuel Antunes Sousa,et al.  A method to define an Enterprise Architecture using the Zachman Framework , 2004, SAC '04.

[11]  Theodore J. Williams,et al.  Use of the Purdue Enterprise Reference Architecture and Methodology in industry (the Fluor Daniel example) , 1996 .

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

[13]  Chris Sauer,et al.  Establishing the Business of the Future:: the Role of Organizational Architecture and Information Technologies , 2003 .

[14]  Vassilios Peristeras,et al.  Building an Enterprise Architecture for Public Administration: A High Level Data Model for Strategic Planning , 2001, ECIS.

[15]  Peter Bernus,et al.  GERAM: The Generalised Enterprise Reference Architecture and Methodology , 2003 .

[16]  James C. Wetherbe,et al.  Key issues in information systems management , 1987 .

[17]  Michael Rohloff,et al.  Enterprise Architecture - Framework and Methodology for the Design of Architectures in the Large , 2005, ECIS.

[18]  Lars Mathiassen,et al.  Collaborative Practice Research , 2000, Scand. J. Inf. Syst..

[19]  Fred Niederman,et al.  Information Systems Management Issues for the 1990s , 1991, MIS Q..

[20]  P. A. M. M. van der Poel,et al.  Framework for Architectures in Information Planning , 1989, ISCO.

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

[22]  Ovidiu Noran.  An analysis of the Zachman framework for enterprise architecture from the GERAM perspective , 2003, Annu. Rev. Control..

[23]  John A. Zachman,et al.  The information systems management system: a framework for planning , 1977, DATB.

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

[25]  Bala Iyer,et al.  The Four-Domain Architecture: An approach to support enterprise architecture design , 2004, IBM Syst. J..

[26]  Simon Liu,et al.  Getting the most from your enterprise architecture , 2000 .

[27]  Olivier Glassey.  Model and architecture for a virtual one stop public administration , 2001, ECIS.