An integrated view on business- and IT-architecture

ABSTRACT

The paper outlines the domains of enterprise architecture and fundamental design techniques. The consolidation of architecture description to three basic views is proposed. The component view describes the elements of architecture and their relationships. The communication view shows how the elements interact with one another. The distribution view describes how the elements are distributed in terms of location or organizational assignment. Key element of architecture design is to account for interdependencies among the building blocks of architecture. Blueprints are introduced as a means in planning the deployment of architecture on a large scale. They give a comprehensive view on the building blocks and how the interact. Blueprints show the effects of architecture design between business-, application-, and infrastructure architecture, thus providing an integrated view on architecture. The techniques introduced for architecture design are illustrated by using a selection of real life examples from an architecture design project.

REFERENCES

• 1: Paul Allen, Service Orientation: Winning Stratergies and Best Practices, Cambridge University Press, New York, NY, 2006
• 2: AMICE (1994). (Esprit Consortium): CIM-OSA: Open Systems Architecture for CIM, Esprit Project 688/5288, Berlin 1994
• 3: Aranow, E. (2002). Enterprise Integration Strategies, Cutter 2002
• 4: Bachmann, F. Software Architecture Documentation in Practice: Documenting Architectural Layers, Special Report CMU/SEI-2000-SR-004, March 2000
• 5: Becker, J./ Schütte R. (2004). Handelsinformationssysteme: Domainenorientierte Einführung in die Wirtschaftsinformatik, Frankfurt am Main 2004
• 6: Bernus, P./ Mertins, K./ Schmidt, G. (Eds.): Handbook of Information Systems, Berlin 1998
• 7: Norbert Bieberstein , Sanjay Bose , Marc Fiammante , Keith Jones , Rawn Shah, Service-Oriented Architecture Compass: Business Value, Planning, and Enterprise Roadmap, Prentice Hall PTR, Upper Saddle River, NJ, 2005
• 8: Birkhölzer, T,/ Vaupel, J. (2003). IT-Architekturen: Planung, Integration, Wartung, Berlin u.a. 2003
• 9: Buhl, U.; Heinrich, B. (Ed.) (2004): Meinung/Dialog: Unternehmensarchitekturen in der Praxis -- Architekturdesign vs. situationsbedingte Realisierung von Informationssystemen, Wirtschaftsinformatik 46(2004)4, p. 311--321
• 10: Paul Clements , David Garlan , Len Bass , Judith Stafford , Robert Nord , James Ivers , Reed Little, Documenting Software Architectures: Views and Beyond, Pearson Education, 2002
• 11: Dern, G. (2003). Management von IT-Architekturen, Wiesbaden 2003
• 12: FEAF: Federal Enterprise Architecture Framework (FEAF), http://www.whitehouse.gov/omb/egov/, called 2007-08-30
• 13: Ferstl, O./ Sinz, E. (1995). Der Ansatz des Semantischen Objektmodells (SOM) zur Modellierung von Geschäfts-prozessen, in: Wirtschaftsinformatik 37(1995)3, S. 209--220
• 14: Ferstl, O./ Sinz, E. (1990). Objektmodellierung betrieblicher Informationssysteme im Semantischen Objektmodell (SOM), in: Wirtschaftsinformatik 32(1990)6, S. 556--581
• 15: Frank, U. (1995). MEMO - eine Methode zur objektorientierten Unternehmensmodellierung, in: Objektspektrum (1995)6, S. 43--47
• 16: Gartner. The Gartner Enterprise Architecture Framework, see http://www3.gartner.com/Init, called 2007-08-30
• 17: Günzel, H./ Rohloff, M. (2003). Architektur im Großen: Gegenstand und Handlungsfelder, in: Dittrich K.; König, W.; Oberweis, A., Rannenberg, K.; Wahlster, W. (Hrsg.): Informatik 2003 Innovative Informatikanwendungen, Band 2, Beiträge der 33. Jahrestagung der Gesellschaft für Informatik e.V. (GI) in Frankfurt a. M., Bonn 2003, S. 422--425
• 18: IEEE (2000). IEEE Standard 1471--2000, Recommended Practice for Architectural Description of Software-Intensive Systems. IEEE Computer Society, New York, October 2000
• 19: Helmut Krcmar, Informationsmanagement, Springer-Verlag New York, Inc., Secaucus, NJ, 2005
• 20: Krcmar, H. (1990). Bedeutung und Ziele von Informationssystem-Architekturen. Wirtschaftsinformatik 32(1990)5, p. 395--402.
• 21: Lapkin, A. (2004a). Architecture Frameworks: How to Choose, Gartner Research, November 2004
• 22: Lapkin, A. (2004b). Architecture Frameworks: Some Options, Gartner Research, November 2004
• 23: Eric A. Marks , Michael Bell, Service-Oriented Architecture (SOA): A Planning and Implementation Guide for Business and Technology, John Wiley & Sons, Inc., New York, NY, 2006
• 24: James Martin, Information Engineering: Introduction, Prentice Hall PTR, Upper Saddle River, NJ, 1989
• 25: Dieter Masak, Moderne Enterprise Architekturen (Xpert.press), Springer-Verlag New York, Inc., Secaucus, NJ, 2007
• 26: Meta Group (2002). Enterprise Architecture Desk Reference, 2002
• 27: Österle, H. (1995). Business Engineering: Prozess- und Systementwicklung, Berlin 1995
• 28: Eric Pulier , Hugh Taylor, Understanding Enterprise SOA, Manning Publications Co., Greenwich, CT, 2005
• 29: August-Wilhelm W. Scheer, Aris-Business Process Frameworks, Springer-Verlag New York, Inc., Secaucus, NJ, 1998
• 30: Jaap Schekkerman, How to Survive in the Jungle of Enterprise Architecture Framework: Creating or Choosing an Enterprise Architecture Framework, Trafford, 2003
• 31: Siemens RPH (2004). Siemens Reference Process House, internal documentation, München 2004
• 32: Sinz, E. J. (2002). Architektur von Informationssystemen, in: Rechenberg, P./ Pomberger, G.: Informatik Handbuch, München 2002, p. 1055--1068
• 33: Sinz, E. (1997). Architektur von Informationssystemen, München 1997
• 34: J. F. Sowa , J. A. Zachman, Extending and formalizing the framework for information systems architecture, IBM Systems Journal, v.31 n.3, p.590-616, 1992
• 35: TOGAF (2003). The Open Group Architecture Framework: Version 8.1 "Enterprise Edition", December 2003, see http://www.opengroup.org/togaf/ called 2007-08-30
• 36: Umek, A./ Tannhäuser, C. (2004): Wert schaffen durch nutzenorientiertes Architekturmanagement in EAI Projekten, in: Aier, S./ Schönherr, M. (Eds.): Enterprise Application Integration: Service Orientierung und nachhaltige Architekturen, Berlin et al. 2004, pp. 49--71
• 37: John A. Zachman, A framework for information systems architecture, IBM Systems Journal, v.26 n.3, p.276-292, 1987
• 38: Zachmann Framework, see http://www.zifa.com/, called 2007-08-30

INDEX TERMS

Primary Classification:
  H. Information Systems
  H.1 MODELS AND PRINCIPLES
      H.1.0 General

Additional Classification:
  H. Information Systems
  H.4 INFORMATION SYSTEMS APPLICATIONS
      H.4.0 General

  K. Computing Milieux
  K.6 MANAGEMENT OF COMPUTING AND INFORMATION SYSTEMS
      K.6.1 Project and People Management

General Terms:
Management

Keywords:
architecture framework, architecture management, architecture process, blueprints, enterprise architecture, information systems planning, stakeholders, views