Modeling Enterprise Architecture with TOGAF

A Practical Guide Using UML and BPMN

Philippe Desfray, Gilbert Raymond

• Publisher: Morgan Kaufmann
• Year: 2014
• Print ISBN: 9780124199842
• eBook ISBN: 9780124199958
• Topic: Computer Science
• Subtopic: Information Technology
• Index: Computer Science

Modeling Enterprise Architecture with TOGAF explains everything you need to know to effectively model enterprise architecture with The Open Group Architecture Framework (TOGAF), the leading EA standard. This solution-focused reference presents key techniques and illustrative examples to help you model enterprise architecture.This book describes the TOGAF standard and its structure, from the architecture transformation method to governance, and presents enterprise architecture modeling practices with plenty of examples of TOGAF deliverables in the context of a case study.Although widespread and growing quickly, enterprise architecture is delicate to manage across all its dimensions. Focusing on the architecture transformation method, TOGAF provides a wide framework, which covers the repository, governance, and a set of recognized best practices. The examples featured in this book were realized using the open source Modelio tool, which includes extensions for TOGAF.- Includes intuitive summaries of the complex TOGAF standard to let you effectively model enterprise architecture- Uses practical examples to illustrate ways to adapt TOGAF to the needs of your enterprise- Provides model examples with Modelio, a free modeling tool, letting you exercise TOGAF modeling immediately using a dedicated tool- Combines existing modeling standards with TOGAF

Chapter 1

TOGAF®

General Presentation

Abstract

This chapter presents the foundations, positioning, and principles of TOGAF and introduces some dedicated vocabulary, as well as the structure and key concepts of the framework. It also discusses the architecture development method as an enterprise architecture transformation approach integrating different facets (business, system, technical) into its process and the place of the organization.

Key Words

TOGAF structure

Framework

Enterprise architecture

Architecture transformation

Impact assessment

Capability

Capability maturity model

Chapter Outline

1.1 What is TOGAF? 1

1.1.1 Positioning and history 1

1.1.2 “A” for Enterprise Architecture 2

1.1.3 “F” for framework 3

1.1.4 The TOGAF document 4

1.2 TOGAF: Key points 5

1.2.1 ADM and the TOGAF crop circle diagram 5

1.2.2 Architecture transformation 6

1.2.3 Architecture in TOGAF 11

1.2.4 Goals, constraints, and requirements 13

1.2.5 Stakeholders and the human factor 13

1.2.6 Architecture strategy, governance, and principles 16

1.3 Summary 17

1.4 Using TOGAF 18

1.4.1 Adapting the framework 18

1.4.2 TOGAF: One framework among many? 19

1.5 Fundamental concepts 24

This chapter presents the foundations, positioning, and principles of TOGAF and introduces some dedicated vocabulary, as well as the structure and key concepts of the framework. It also discusses the architecture development method (ADM) as an enterprise architecture transformation approach integrating different facets (business, system, technical) into its process and the place of the organization.

1.1 What is TOGAF?

1.1.1 Positioning and history

TOGAF¹ has long been recognized as a major reference in the field of enterprise architecture. It is successful because it meets a real need: the need for a common framework that will facilitate the capitalization and mutualization of architectural practices throughout a community. More specifically, TOGAF is positioned as a generic method, which groups together a set of techniques focusing on the transformation of enterprise architecture.

Developed by The Open Group (TOG) international consortium, the current version of TOGAF (version 9.1, December 2011) is the result of work carried out over several years by dozens of companies. Released in 1995, the first version of TOGAF was based on TAFIM,² itself developed by the DOD.³ Initially built as a technical framework, TOGAF then evolved, resulting in version 8 (“Enterprise Edition”) in 2003, whose content focused more on the enterprise and the business. Version 9 continued and built on this orientation. In 2008 a certification program was put in place, and today more than 20,000 people around the world are TOGAF-certified.

It should be noted that TOGAF can be applied to all types of architecture, including architecture based on enterprise resource planning systems. One example of this is SAP, who provide their own architecture framework⁴ (EAF) as an adaptation of TOGAF.

---

⁴ SAP Enterprise Architecture Framework.

The sheer size of the TOGAF reference document (nearly 750 pages) should not overshadow the orientation of the project, which focuses on the enterprise architecture transformation approach. This approach, described by the ADM, constitutes the heart of the reference document.

1.1.2 “A” for Enterprise Architecture

The “A” of TOGAF implies “Enterprise Architecture” in all its forms and is not limited to information systems (ISs). Admittedly, the goal remains the implementation of operational software systems, but to achieve this goal, a wider view is required, covering strategic, business, and organizational aspects. Moreover, the alignment of “business” and “technology” is a major concern for business managers and chief information officers (CIOs), who are constantly looking for IS agility. Architecture therefore covers requirements and strategies as well as business processes and technical applications and infrastructures and strives for optimal articulation between these different facets. It should be pointed out here that the term enterprise is not limited to its legal sense, but rather designates any organization linked by a common set of goals.⁵

In this context, TOGAF provides a pragmatic view of enterprise architecture, while highlighting the central role of organization. Any architectural transformation requires close collaboration between the different people involved in the enterprise architecture. Governance, stakeholder management, and an architecture-dedicated team implementation are among the many subjects dealt with by TOGAF.

This collaboration is based on an organized process. It is the role of the ADM to provide a structure for the progress of architectural transformation projects. Communication plays a vital role here. At each stage of transformation work, a common understanding of the goals and the target must constantly be sought. The media used (documents, models, etc.) must be clearly defined and adapted to the different participants.

Beyond the implementation of architecture projects, capitalization and reuse are constantly present goals. Consequently, the task of setting up an architecture repository is central to TOGAF. This repository can include all sorts of elements, such as examples, norms, models, rules, or guidelines. Fed by the different work carried out, the repository guarantees centralization and homogeneous distribution throughout the enterprise.

It should be noted that TOGAF does not recommend any particular style of architecture, let alone any specific technical infrastructure. Definition references are provided for these subjects, such as EAI, SOA, or BPM, accompanied by guides and best practices. This choice is justified by the sheer diversity of situations encountered and by the generic nature of the proposed framework.

1.1.3 “F” for framework

A framework groups together a collection of means and procedures dedicated to a particular field of activity. When used as a reference and a tool, a framework is most often presented as being complete and consistent for the f...

Table of contents

• Cover image
• Title page
• Table of Contents
• Copyright
• Preface
• Foreword
• Chapter 1: TOGAF®: General Presentation
• Chapter 2: The ADM Method
• Chapter 3: The Components of TOGAF Architecture
• Chapter 4: The Repository and Governance
• Chapter 5: Key Modeling Techniques
• Chapter 6: Introduction to TOGAF Models
• Chapter 7: Models for Phase A: Vision
• Chapter 8: Models for Phase B: Business Architecture
• Chapter 9: Models for Phase C: Information System Architecture
• Chapter 10: Models for Phase D: Technology Architecture
• Chapter 11: Models for Phase E: Opportunities and Solutions
• Chapter 12: SOA, Processes, and Information
• Chapter 13: Testimonials
• Chapter 14: ArchiMate
• Chapter 15: The EAP Profile
• Glossary
• Bibliography
• Index