Towards a More Integrated EA Planning: Linking Transformation Planning with Evolutionary Change

Enterprises are subject to continuous change driven by top-down planned transformation projects as well as by bottom-up initiatives realizing what is called the evolution of the enterprise. Enterprise architecture (EA) planning presents itself as a means for facilitating and controlling this change. Nevertheless, the methods and models of EA planning developed in recent years either have a strong focus on planned (proactive) transformations or on guided (reactive) evolution. In this paper, we outline an EA planning method that accounts for both types of enterprise change by illustrating the interplay of EA planning, requirements, release and synchronization management. Specifically we focus on the coordination of design activities modeled as intermeshed closed-loop control systems and on an integrated information model describing EA transformation planning.

[1]  Stephan Aier,et al.  Applying Design Research Artifacts for Building Design Research Artifacts: A Process Model for Enterprise Architecture Planning , 2010, DESRIST.

[2]  R. Winter,et al.  Business Engineering — Betriebswirtschaftliche Konstruktionslehre und ihre Anwendung in der Informationslogistik , 2008 .

[3]  Alexander M. Ernst,et al.  Roadmaps for Enterprise Architecture Evolution , 2010, Software Engineering.

[4]  Roel Wagter,et al.  Dynamic Enterprise Architecture: How to Make It Work , 2005 .

[5]  Stephan Aier,et al.  Towards a Systematic Approach for Capturing Dynamic Transformation in Enterprise Models , 2010, 2010 43rd Hawaii International Conference on System Sciences.

[6]  Samir Chatterjee,et al.  A Design Science Research Methodology for Information Systems Research , 2008 .

[7]  John C. Henderson,et al.  Strategic Alignment: Leveraging Information Technology for Transforming Organizations , 1993, IBM Syst. J..

[8]  Thomas A. Gutzwiller,et al.  Das CC RIM-Referenzmodell für den Entwurf von betrieblichen, transaktionsorientierten Informationssystemen , 1994 .

[9]  John C. Henderson,et al.  Strategic Alignment: Leveraging Information Technology for Transforming Organizations , 1999, IBM Syst. J..

[10]  W. Ashby,et al.  Every Good Regulator of a System Must Be a Model of That System , 1970 .

[11]  Alexander L. Wolf,et al.  Software release management for component‐based software , 2003, Softw. Pract. Exp..

[12]  Dietger Hahn,et al.  PuK, Controllingkonzepte : Planung und Kontrolle, Planungs- und Kontrollsysteme, Planungs- und Kontrollrechnung , 1994 .

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

[14]  L WolfAlexander,et al.  Software release management for component-based software , 2003 .

[15]  James M. Antill,et al.  Critical path methods in construction practice , 1970 .

[16]  Robert Winter,et al.  Method construction - a core approach to organizational engineering , 2005, SAC '05.

[17]  Mirja Pulkkinen,et al.  Systemic Management of Architectural Decisions in Enterprise Architecture Planning. Four Dimensions and Three Abstraction Levels , 2006, Proceedings of the 39th Annual Hawaii International Conference on System Sciences (HICSS'06).

[18]  Florian Matthes,et al.  An Information Model for Managed Application Landscape Evolution , 2009 .

[19]  Jerry N. Luftman,et al.  Transforming the Enterprise: The Alignment of Business and Information Technology Strategies , 1993, IBM Syst. J..