What Is an Enterprise Architecture Principle? - Towards a Consolidated Definition

Architecture can be defined as the fundamental organization of a system and the principles governing its design and evolution (IEEE 2000). While design representation issues like meta-modeling and notations have been intensely discussed in Enterprise Architecture (EA), design activity issues are often neglected. This is surprising because EA principles play an important role in practice. As a contribution towards a consensus on a clear definition of EA principles, we analyze state-of-the-art on EA principle definitions. Our literature analysis is based on the results of Stelzer’s (2009) broad literature review. Based on five selected approaches, seven common main components of EA principle definitions are identified: (1) An EA principle is based on business strategy and IT strategy; (2) EA design principles refer to the construction of an enterprise while requirements refer to its function; (3) Principles can be attributed to different layers (e.g. business, information system, technology); (4) An EA principle is described in a principle statement saying what to improve; (5) For each principle, a rationale is formulated explaining why the principle is meant to help reaching a pre-defined goal; (6) For each principle, concrete implications or key actions are described explaining how to implement the principle; and (7) For every principle, it should be defined how to determine its fulfillment.

[1]  Åsa Lindström,et al.  On the Syntax and Semantics of Architectural Principles , 2006, Proceedings of the 39th Annual Hawaii International Conference on System Sciences (HICSS'06).

[2]  Jan A. P. Hoogervorst,et al.  Enterprise Governance and Enterprise Engineering , 2009, The Enterprise Engineering Series.

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

[4]  Robert Winter,et al.  Essential Layers, Artifacts, and Dependencies of Enterprise Architecture , 2006, 2006 10th IEEE International Enterprise Distributed Object Computing Conference Workshops (EDOCW'06).

[5]  M. Wilkinson,et al.  Designing an ‘adaptive’ enterprise architecture , 2006 .

[6]  J ArmourFrank,et al.  A Big-Picture Look at Enterprise Architectures , 1999 .

[7]  Robert Winter,et al.  Language communities in enterprise architecture research , 2009, DESRIST.

[8]  Jan L. G. Dietz,et al.  Enterprise ontology - theory and methodology , 2006 .

[9]  Salvatore T. March,et al.  Design and natural science research on information technology , 1995, Decis. Support Syst..

[10]  M. Marcelli,et al.  Design and Methods , 2011 .

[11]  Jeanne W. Ross,et al.  Enterprise Architecture As Strategy: Creating a Foundation for Business Execution , 2006 .

[12]  Gary W. Dickson,et al.  A Principles-Based Enterprise Architecture: Lessons from Texaco and Star Enterprise , 1990, MIS Q..

[13]  Jean Hartley,et al.  Case study research , 2004 .

[14]  R. Yin Case Study Research: Design and Methods , 1984 .

[15]  Marten Schönherr,et al.  Towards a Common Terminology in the Discipline of Enterprise Architecture , 2009, ICSOC Workshops.

[16]  F. J. Armour,et al.  A big-picture look at enterprise architectures , 1999 .

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

[18]  Dirk Stelzer,et al.  Enterprise Architecture Principles: Literature Review and Research Directions , 2009, ICSOC/ServiceWave Workshops.

[19]  P. Weill,et al.  IT Governance , 2017 .

[20]  Bignolas Mira da Silva,et al.  Enterprise Architecture , 2007 .

[21]  Jan A. P. Hoogervorst,et al.  Enterprise Architecture: Enabling Integration, Agility And Change , 2004, Int. J. Cooperative Inf. Syst..

[22]  Richard T. Watson,et al.  Analyzing the Past to Prepare for the Future: Writing a Literature Review , 2002, MIS Q..