TOGAF® Version 9.1 - A Pocket Guide (eBook)
161 Seiten
van Haren Publishing (Verlag)
978-90-8753-927-6 (ISBN)
Preface 10
Trademarks 15
About the Authors 16
Acknowledgements 19
Chapter 1 Introduction 20
1.1 Introduction to TOGAF 20
1.2 Structure of the TOGAF Document 21
1.3 What is Architecture in the Context of TOGAF? 22
1.4 What kinds of Architecture does TOGAF deal with? 22
1.5 What does TOGAF Contain? 23
Chapter 2 The Architecture Development Method 28
2.1 What is the ADM? 28
2.3 The ADM in Detail 32
2.4 Scoping the Architecture Activity 45
Chapter 3 Key Techniques and Deliverables of the ADM Cycle 48
3.1 Tailored Architecture Framework 50
3.2 Organizational Model for Enterprise Architecture 51
3.3 Architecture Principles 52
3.4 Business Principles, Business Goals, and Business Drivers 57
3.5 Architecture Repository 57
3.6 Architecture Tools 58
3.7 Request for Architecture Work 58
3.8 Statement of Architecture Work 59
3.9 Architecture Vision 59
3.10 Stakeholder Management 60
3.11 Communications Plan 63
3.12 Business Transformation Readiness Assessment 64
3.13 Capability Assessment 64
3.14 Risk Management 66
3.15 Architecture Definition Document 67
3.16 Architecture Requirements Specification 70
3.17 Architecture Roadmap 72
3.18 Business Scenarios 74
3.19 Gap Analysis 75
3.20 Architecture Viewpoints 77
3.21 Architecture Views 79
3.22 Architecture Building Blocks 80
3.23 Solution Building Blocks 81
3.24 Capability-Based Planning 82
3.25 Migration Planning Techniques 83
3.26 Implementation and Migration Plan 87
3.27 Transition Architecture 88
3.28 Implementation Governance Model 89
3.29 Architecture Contracts 89
3.30 Change Request 91
3.31 Compliance Assessment 92
3.32 Requirements Impact Assessment 93
Chapter 4 Guidelines for Adaptingthe ADM 94
4.1 Introduction 94
4.2 Applying Iteration to the ADM 96
4.3 Applying the ADM across the Architecture Landscape 102
4.4 Security Architecture and the ADM 103
4.5 Using TOGAF to Define and Govern SOAs 105
Chapter 5 Architecture Content Framework 108
5.1 Architecture Content Framework Overview 108
5.2 Content Metamodel 109
5.3 Architectural Artifacts 113
5.4 Architecture Deliverables 117
5.5 Building Blocks 117
Chapter 6 The Enterprise Continuum 120
6.1 Overview of the Enterprise Continuum 120
6.2 Architecture Partitioning 123
6.3 Architecture Repository 124
Chapter 7 TOGAF Reference Models 128
7.1 TOGAF Foundation Architecture 128
7.2 Integrated Information Infrastructure Reference Model (III-RM) 128
Chapter 8 Architecture Capability Framework 130
8.1 Establishing an Architecture Capability 132
8.2 Architecture Governance 132
8.3 Architecture Board 133
8.4 Architecture Compliance 134
8.5 Architecture Skills Framework 134
Appendix A Migration Summary 138
Glossary 152
Index 158
Chapter 2
The Architecture Development Method
This chapter describes the Architecture Development Method (ADM), its relationship to the rest of TOGAF, and high-level considerations for its use. It also includes a summary of each phase within the ADM.
Topics addressed in this chapter include:
• An introduction to the ADM
• The phases of the ADM
• The objectives, steps, inputs, and outputs to the ADM phases
• Requirements Management during the ADM cycle
• Scoping the architecture activity
2.1 What is the ADM?
The ADM, a result of contributions from many architecture practitioners, forms the core of TOGAF. It is a method for deriving organization-specific enterprise architectures and is specifically designed to address business requirements. The ADM describes:
• A reliable, proven way of developing and using an enterprise architecture
• A method of developing architectures on different levels4 (business, application, data, technology) that enable the architect to ensure that a complex set of requirements are adequately addressed
• A set of guidelines and techniques for architecture development
2.2 What are the Phases of the ADM?
The ADM consists of a number of phases that cycle through a range of architecture domains that enable the architect to ensure that a complex set of requirements is adequately addressed. The basic structure of the ADM is shown in Figure 2.
Figure 2: The Architecture Development Method Cycle
The ADM is applied iteratively throughout the entire process, between phases, and within them. Throughout the ADM cycle, there should be frequent validation of results against the original requirements, both those for the whole ADM cycle, and those for the particular phase of the process. Such validation should reconsider scope, detail, schedules, and milestones. Each phase should consider assets produced from previous iterations of the process and external assets from the marketplace, such as other frameworks or models.
The ADM supports the concept of iteration at three levels:
• Cycling around the ADM: The ADM is presented in a circular manner indicating that the completion of one phase of architecture work directly feeds into subsequent phases of architecture work.
• Iterating between phases: TOGAF describes the concept of iterating across phases (e.g., returning to Business Architecture on completion of Technology Architecture).
• Cycling around a single phase: TOGAF supports repeated execution of the activities within a single ADM phase as a technique for elaborating architectural content.
Further information on iteration is given in TOGAF, Part III: ADM Guidelines and Techniques (see Chapter 4).
Table 3: Architecture Development Method Activities by Phase
| ADM Phase | Activity |
| Prepare the organization for successful TOGAF architecture projects. Undertake the preparation and initiation activities required to create an Architecture Capability, including the customization of TOGAF, selection of tools, and the definition of Architecture Principles. |
| Every stage of a TOGAF project is based on and validates business requirements. Requirements are identified, stored, and fed into and out of the relevant ADM phases, which dispose of, address, and prioritize requirements. |
| Set the scope, constraints, and expectations for a TOGAF project. Create the Architecture Vision. Identify stakeholders. Validate the business context and create the Statement of Architecture Work. Obtain approvals. |
| Develop architectures in four domains: 1. Business 2. Information Systems – Application 3. Information Systems – Data 4. Technology In each case, develop the Baseline and Target Architecture and analyze gaps. |
| Perform initial implementation planning and the identification of delivery vehicles for the building blocks identified in the previous phases. Determine whether an incremental approach is required, and if so identify Transition Architectures. |
| Develop detailed Implementation and Migration Plan that addresses how to move from the Baseline to the Target Architecture. |
| Provide architectural oversight for the implementation. Prepare and issue Architecture Contracts. Ensure that the implementation project conforms to the architecture. |
| Provide continual monitoring and a change management process to ensure that the architecture responds to the needs of the enterprise and maximizes the value of the architecture to the business. |
2.3 The ADM in Detail
The following tables summarize the objectives, steps, and the inputs and outputs5 of each phase of the ADM cycle.
2.3.1 Preliminary Phase
The Preliminary phase prepares an organization to undertake successful enterprise architecture projects.
An overview of the phase is given below:
| Objectives | Steps |
| Determine the Architecture Capability desired by the organization: • Review the organizational context for conducting enterprise architecture • Identify and scope the elements of the enterprise organizations affected by the Architecture Capability • Identify the established frameworks, methods, and processes that intersect with the Architecture Capability • Establish Capability Maturity target Establish the Architecture Capability: • Define and establish the Organizational Model for Enterprise Architecture • Define and establish the detailed process and resources for architecture governance • Select and implement tools that support the architecture activity • Define the Architecture Principles | Scope the enterprise organizations impacted Confirm governance and support frameworks Define and establish enterprise architecture team and organization Identify and establish architecture principles Tailor TOGAF and, if any, other selected Architecture Frameworks Implement architecture tools |
| Inputs | Outputs |
| TOGAF Other architecture framework(s) Board strategies, business plans, business strategy, IT Strategy, business principles, business goals, and business drivers Governance and legal frameworks | Organizational model for enterprise architecture Tailored Architecture Framework, including architecture principles Initial Architecture Repository |
| Architecture capability Partnership and contract agreements Existing organizational model for enterprise architecture Existing architecture framework, if any, including: • Architecture method • Architecture content • Configured and deployed tools • Architecture Principles • Architecture Repository | Restatement of, or reference to, business principles, business goals, and business drivers Request for Architecture Work Governance Framework |
2.3.2 Phase A: Architecture Vision
Phase A is about project establishment and initiates an iteration of the architecture development cycle, setting the scope, constraints, and expectations for the iteration. It is required in order to validate the business context and to create the approved Statement of Architecture Work.
| Objectives | Steps |
| Develop a high-level aspirational vision of the capabilities and business value to be delivered as a result of the proposed enterprise architecture Obtain approval for a Statement of Architecture Work that defines a program of works to develop and deploy the architecture outlined in the Architecture Vision | Establish the architecture project Identify stakeholders, concerns, and business requirements Confirm and elaborate business goals, business drivers, and constraints Evaluate business capabilities Assess readiness for business transformation Define scope Confirm and elaborate architecture principles, including business principles Develop Architecture Vision Define the Target Architecture value propositions and KPIs Identify the... |
| Erscheint lt. Verlag | 1.1.2016 |
|---|---|
| Reihe/Serie | TOGAF Series |
| Verlagsort | Hertogenbosch |
| Sprache | englisch |
| Themenwelt | Schulbuch / Wörterbuch ► Schulbuch / Allgemeinbildende Schulen |
| Mathematik / Informatik ► Informatik ► Programmiersprachen / -werkzeuge | |
| Mathematik / Informatik ► Informatik ► Software Entwicklung | |
| Mathematik / Informatik ► Informatik ► Theorie / Studium | |
| Sozialwissenschaften ► Pädagogik | |
| Technik ► Architektur | |
| Wirtschaft ► Betriebswirtschaft / Management ► Finanzierung | |
| Wirtschaft ► Betriebswirtschaft / Management ► Marketing / Vertrieb | |
| Wirtschaft ► Betriebswirtschaft / Management ► Personalwesen | |
| Wirtschaft ► Betriebswirtschaft / Management ► Planung / Organisation | |
| Wirtschaft ► Betriebswirtschaft / Management ► Projektmanagement | |
| Wirtschaft ► Betriebswirtschaft / Management ► Unternehmensführung / Management | |
| ISBN-10 | 90-8753-927-4 / 9087539274 |
| ISBN-13 | 978-90-8753-927-6 / 9789087539276 |
| Haben Sie eine Frage zum Produkt? |
PDF (Adobe DRM)Größe: 3,9 MB
Kopierschutz: Adobe-DRM
Adobe-DRM ist ein Kopierschutz, der das eBook vor Mißbrauch schützen soll. Dabei wird das eBook bereits beim Download auf Ihre persönliche Adobe-ID autorisiert. Lesen können Sie das eBook dann nur auf den Geräten, welche ebenfalls auf Ihre Adobe-ID registriert sind.
Details zum Adobe-DRM
Dateiformat: PDF (Portable Document Format)
Mit einem festen Seitenlayout eignet sich die PDF besonders für Fachbücher mit Spalten, Tabellen und Abbildungen. Eine PDF kann auf fast allen Geräten angezeigt werden, ist aber für kleine Displays (Smartphone, eReader) nur eingeschränkt geeignet.
Systemvoraussetzungen:
PC/Mac: Mit einem PC oder Mac können Sie dieses eBook lesen. Sie benötigen eine
eReader: Dieses eBook kann mit (fast) allen eBook-Readern gelesen werden. Mit dem amazon-Kindle ist es aber nicht kompatibel.
Smartphone/Tablet: Egal ob Apple oder Android, dieses eBook können Sie lesen. Sie benötigen eine
Geräteliste und zusätzliche Hinweise
Buying eBooks from abroad
For tax law reasons we can sell eBooks just within Germany and Switzerland. Regrettably we cannot fulfill eBook-orders from other countries.
aus dem Bereich
