enterprise architecture management pattern catalog .usingtheeampc 9 2.1 ... togaf 1 1995 togaf 8.1

Download Enterprise Architecture Management Pattern Catalog .UsingtheEAMPC 9 2.1 ... TOGAF 1 1995 TOGAF 8.1

Post on 05-Jun-2018

215 views

Category:

Documents

0 download

Embed Size (px)

TRANSCRIPT

  • Enterprise Architecture Management Pattern Catalog

    Version 2.0November 2015

    Pouya Aleatrati Khosroshahi, Matheus Hauder, Alexander W. Schneider, Prof. Dr. FlorianMatthes

    Software Engineering for Business Information Systems (sebis)Ernst Denert-Stiftungslehrstuhl

    Chair for Informatics 19Technische Universitt Mnchen

    Boltzmannstrae 3, 85748 Garching b. Mnchen, Germany

  • About sebis

    Software Engineering for Business Information Systems (sebis) is a research chair at the Insti-tute for computer science of the Technische Universitt Mnchen. Sebis has been establishedin 2002 with funding of the Ernst Denert-Stiftung and is headed by Professor Dr. FlorianMatthes. Main research areas of sebis are:

    Enterprise Architecture Management: Development of methods that support the strate-gic planning, analysis, and enactment of holistic models for business processes, informa-tion systems, and IT infrastructure with their relationships.

    Social Software Engineering: Development of social software solutions that improve thecollaborative organization of information and processes.

    Copyright

    Copyright 2015 Technische Universitt Mnchen, sebis, Germany. All rights reserved.

    No part of this publication may be reproduced, stored, archived, or transmitted in any formby any means (electronical, mechanical, by photocopying, or otherwise) without the priorprinted permission of the publisher, Technische Universitt Mnchen, sebis. The informationcontained and opinions expressed herein may be changed without prior notice.

    Trademarks

    All trademarks or registered trademarks are the property of their respective owners.

    Disclaimer

    The information contained herein has been obtained from sources believed to be reliable atthe time of publication but cannot be guaranteed. Please note that the findings, conclusionsand recommendations that Technische Universitt Mnchen, sebis delivers will be based oninformation gathered in good faith from both primary and secondary sources, whose accuracycannot always be guaranteed by Technische Universitt Mnchen, sebis.

    Technische Universitt Mnchen, sebis disclaims all warranties as to the accuracy, complete-ness, or adequacy of such information. Technische Universitt Mnchen, sebis shall have noliability for errors, omissions, or inadequacies in the information contained herein or for in-terpretations thereof. In no event shall Technische Universitt Mnchen, sebis be liable forany damage of any kind (e.g. direct, indirect, special, incidental, consequential, or punitivedamages) whatsoever, including without limitation lost revenues, or lost profits, which mayresult from the use of these materials. The reader assumes sole responsibility for the selectionof these materials to achieve its intended results.

    There will be no warranty that the results of this publication will be economically and tech-nically exploitable and unencumbered by third-party proprietary rights.

    II

  • Abstract

    There ist no denying that the Enterprise Architecture Management (EAM) func-tion is gaining increased attention in todays organizations: Upcoming trends invarious branches and the increased focus on the demands of single customers,leads to entire new business requirements, fundamental changes in organizationalstrategies and thus in the operating IT landscapes. EAM focuses on steering suchIT transformation projects by supporting with smart EAM methods, transparentvisualizations and fast provisioning of information.

    Based on several years of research experience and EAM projects, the sebis chairof the Universitt Mnchen has a concrete perception of what kind of conceptsconstitute EAM functions in large organizations: EAM functions address variousconcerns of multiple stakeholders by using concrete EAM methods and visual-ize the current state of the respective concern visualizations. Moreover archi-tecture principles, and branch and organization specific influence factors impactthe organizational and operational structure and thus the EAM function of theorganization.

    In 2008, the sebis chair published the Enterprise Architecture Management Pat-tern Catalog, a EAM best practice and pattern collection. After seven years, theEAM function might has changed in todays organizations and thus new EAMpatterns have been observed. For this reason, the Enterprise Architecture Man-agement Catalog V2 (EAMPC V2) picks up this topic again and focuses on iden-tifying new EAM patterns and best practices. We conducted an online survey andsingle expert interviews with 31 practitioners and identified various new trends intodays EAM functions. This catalog includes our observed EAM patterns.

    III

  • IV

  • Acknowledgments

    Since the majority of gathered information originate from practitioners, we thankour industry partners which shared their knowledge and provided useful insights.

    Last but not least, we want to thank Daniel Elsner, mer Uludag and SimonPigat for their support in documenting and compiling the catalogs content.

    Garching b. Mnchen, November 2015

    Pouya Aleatrati KhosroshahiMatheus Hauder

    Alexander W. SchneiderProf. Dr. Florian Matthes

    V

  • VI

  • Contents

    1. Introduction 11.1. Research objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.2. Research design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41.3. Extending the language of the EAMPC . . . . . . . . . . . . . . . . . . . . . . 51.4. Miscellaneous information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

    2. Using the EAMPC 92.1. Implementing an organization-specific EAM . . . . . . . . . . . . . . . . . . . . 102.2. Performing benchmarks with the EAMPC . . . . . . . . . . . . . . . . . . . . . 112.3. The EAMPC as basis for academic research . . . . . . . . . . . . . . . . . . . . 112.4. How to read the EAM pattern graph . . . . . . . . . . . . . . . . . . . . . . . . 12

    3. Influence Factors 133.1. Overview of influence factors . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143.2. Interpretation of results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

    4. Stakeholders 174.1. Overview of stakeholders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184.2. Amount of mentioned concerns for each stakeholder . . . . . . . . . . . . . . . . 19

    5. Concerns 215.1. Overview of concerns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225.2. Amount of allocated stakeholders for every concern . . . . . . . . . . . . . . . . 23

    6. Methodology Patterns and Principles 256.1. Overview of architecture principles . . . . . . . . . . . . . . . . . . . . . . . . . 266.2. Identification of architecture principle sets . . . . . . . . . . . . . . . . . . . . . 266.3. Overview of used methodologies . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

    7. Viewpoint Patterns 417.1. Viewpoint V-107 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427.2. Viewpoint V-108 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

    Technische Universitt Mnchen, sebis, 2015. All rights reserved. VII

  • Contents

    7.3. Viewpoint V-109 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 517.4. Viewpoint V-110 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 527.5. Viewpoint V-111 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 537.6. Viewpoint V-112 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 577.7. Viewpoint V-113 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 587.8. Viewpoint V-114 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 627.9. Viewpoint V-115 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 667.10. Viewpoint V-116 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 677.11. Viewpoint V-117 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 687.12. Viewpoint V-118 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 697.13. Viewpoint V-119 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 707.14. Viewpoint V-120 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

    8. Information Model Patterns 738.1. Information model I-99 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 748.2. Information model I-100 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 758.3. Information model I-101 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 768.4. Information model I-102 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 778.5. Information model I-103 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 788.6. Information model I-104 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 798.7. Information model I-105 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 808.8. Information model I-106 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 818.9. Information model I-107 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 828.10. Information model I-108 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 848.11. Information model I-109 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 858.12. Information model I-110 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 868.13. Information model I-111 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 878.14. Information model I-112 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 888.15. Information model I-113 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 898.16. Information model I-114 . . . .