book

Modeling Enterprise Architecture with TOGAF

by Philippe Desfray, Gilbert Raymond

August 2014

Intermediate to advanced

350 pages

8h 54m

English

Morgan Kaufmann

Read now

Unlock full access

Aim of this bookWho is this book for?Acknowledgments
Abstract1.1 What is TOGAF?1.2 TOGAF: Key points1.3 Summary1.4 Using TOGAF1.5 Fundamental concepts
Abstract2.1 The ADM cycle2.2 The phases of the ADM2.3 Iterations2.4 ADM techniques and guidelines2.5 Fundamental concepts
Abstract3.1 Architecture components3.2 The metamodel3.3 Artifacts3.4 Building blocks3.5 Deliverables3.6 Fundamental concepts
Abstract4.1 The architecture repository4.2 Architecture governance4.3 Fundamental concepts

Abstract5.1 Models: Benefits, uses, and characteristics5.2 The concept of viewpoints5.3 Special role played by diagrams5.4 Consistency and traceability5.5 Architecture repository5.6 Risks and main difficulties5.7 Repository governance5.8 Tools and languages5.9 Fundamental concepts
Abstract6.1 TOGAF artifacts6.2 UML and BPMN for TOGAF modeling6.3 The “Discount Travel” enterprise6.4 Fundamental concepts
Abstract7.1 Phase A artifacts7.2 Stakeholder matrix7.3 Artifacts linked to goals7.4 Artifacts linked to requirements7.5 Artifacts linked to business processes7.6 The “Solution concept diagram” artifact7.7 The “Value chain diagram” artifact7.8 Fundamental concepts
Abstract8.1 Phase B artifacts8.2 The “business dictionary” artifact8.3 Artifacts linked to enterprise organization8.4 Artifacts linked to enterprise functions and services8.5 Artifacts linked to business processes8.6 Artifacts linked to data8.7 Fundamental concepts
Abstract9.1 Phase C artifacts9.2 The “application communication diagram” artifact9.3 The “application migration diagram” artifact9.4 The “application and user location diagram” artifact9.5 The “system use case diagram” artifact9.6 The “process system realization diagram” artifact9.7 The “enterprise manageability diagram” artifact9.8 Data architecture9.9 The “service data diagram” artifact (Figure 9.14)9.10 Fundamental concepts
Abstract10.1 Phase D artifacts10.2 The “Environment and location diagram” artifact10.3 The “Processing diagram” artifact10.4 The “Network computing hardware diagram” artifact10.5 Fundamental concepts
Abstract11.1 Phase E artifacts11.2 The “Benefits diagram” artifact11.3 Project context diagrams
Abstract12.1 Service-Oriented Architecture12.2 Business processes12.3 Information12.4 Fundamental concepts
Abstract13.1 Introduction13.2 TOGAF within the AMUE13.3 TOGAF within the EDF Group
Abstract14.1 The ArchiMate standard14.2 ArchiMate to EAP correspondence examples14.3 Detailed mapping14.4 Fundamental concepts
Abstract15.1 Mapping UML and BPMN to TOGAF15.2 Vision and requirements15.3 Global structure and architecture domains15.4 Data architecture15.5 Business architecture (Figure 15.6)15.6 Application architecture (Figure 15.8)15.7 Technology architecture (Figure 15.10)15.8 Fundamental concepts

Content preview from Modeling Enterprise Architecture with TOGAF

Chapter 14

ArchiMate

Abstract

ArchiMate is a modeling standard published by The Open Group. ArchiMate has defined from scratch a modeling language dedicated to TOGAF. EAP, on the other hand, has taken the route of reusing and adapting existing standards (UML, BPMN, and UML profiles), both to benefit from tools already present in the marketplace and to address a wide community of practitioners already familiar with UML and BPMN. This chapter briefly presents the ArchiMate standard and shows how ArchiMate and EAP are mapped.

Key Word

ArchiMate