TOGAF® Version 9 - A Pocket Guide (eBook)

The Group (Autor)

eBook Download: PDF | EPUB

2009 | 1. Auflage
158 Seiten
van Haren Publishing (Verlag)
978-90-8753-602-2 (ISBN)

Infos

This is the official Open Group Pocket Guide for TOGAF Version 9 Enterprise Edition. This pocket guide is published by Van Haren Publishing on behalf of The Open Group. TOGAF, The Open Group Architectural Framework is a fast growing, worldwide accepted standard that can help organisations build their own Enterprise Architecture in a standardised way. This book explains why the in’s and out’s of TOGAF in a concise manner. This book explains how TOGAF can help to make an Enterprise Architecture. Enterprise Architecture is an approach that can help management to understand this growing complexity.

Inhalt

Preface 10
Trademarks 15
About the Authors 16
Acknowledgements 19
Chapter 1 Introduction to TOGAF® 20
1.1 Introduction to TOGAF 9 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
1.5.1 The Architecture Development Method (ADM) 24
1.5.2 ADM Guidelines and Techniques 24
1.5.3 Architecture Content Framework 25
1.5.4 The Enterprise Continuum 25
1.5.5 TOGAF Reference Models 25
1.5.6 The Architecture Capability Framework 26
Chapter 2 The Architecture Development Method 28
2.1 What is the ADM? 28
2.2 What are the Phases of the ADM? 29
2.3 The ADM in Detail 31
2.3.1 Preliminary Phase 32
2.3.2 Phase A: Architecture Vision 33
2.3.3 Phase B: Business Architecture 34
2.3.4 Phase C: Information Systems Architectures 35
2.3.5 Phase D: Technology Architecture 38
2.3.6 Phase E: Opportunities and Solutions 39
2.3.7 Phase F: Migration Planning 41
2.3.8 Phase G: Implementation Governance 42
2.3.9 Phase H: Architecture Change Management 43
2.3.10 Requirements Management 45
2.4 Scoping the Architecture Activity 46
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.3.1 Developing Architecture Principles 52
3.3.2 Defining Architecture Principles 53
3.3.3 Qualities of Principles 55
3.3.4 Applying Architecture Principles 55
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.10.1 Steps in the Stakeholder Management Process 61
3.11 Communications Plan 63
3.12 Business Transformation Readiness Assessment 64
3.13 Capability Assessment 65
3.14 Risk Management 66
3.15 Architecture Definition Document 67
3.15.1 Business Architecture 68
3.15.2 Information Systems Architectures 69
3.15.3 Technology Architecture 70
3.16 Architecture Requirements Specification 70
3.16.1 Business Architecture Requirements 71
3.16.2 Information Systems Architectures Requirements 72
3.16.3 Technology Architecture Requirements 72
3.16.4 Interoperability Requirements 72
3.17 Architecture Roadmap 72
3.18 Business Scenarios 73
3.19 Gap Analysis 74
3.20 Architecture Viewpoints 76
3.21 Architecture Views 79
3.21.1 Developing Views in the ADM 79
3.22 Architecture Building Blocks 79
3.23 Solution Building Blocks 80
3.24 Capability-Based Planning 81
3.25 Migration Planning Techniques 82
3.25.1 Implementation Factor Assessment and Deduction Matrix 82
3.25.2 Consolidated Gaps, Solutions, and Dependencies Matrix 83
3.25.3 Architecture Definition Increments Table 83
3.25.4 Enterprise Architecture State Evolution Table 84
3.25.5 Business Value Assessment Technique 85
3.26 Implementation and Migration Plan 86
3.27 Transition Architecture 87
3.28 Implementation Governance Model 88
3.29 Architecture Contracts 89
3.30 Change Request 91
3.31 Compliance Assessment 92
3.32 Requirements Impact Assessment 92
Chapter 4 Guidelines for Adapting the ADM 94
4.1 Introduction 94
4.2 Applying Iteration to the ADM 96
4.3 Applying the ADM at Different Enterprise Levels 101
4.4 Security Architecture and the ADM 103
4.5 Using TOGAF to Define and Govern SOAs 105
4.5.1 Further Reading 107
Chapter 5 Architecture Content Framework 110
5.1 Architecture Content Framework Overview 110
5.2 Content Metamodel 111
5.2.1 Core and Extensions 113
5.2.2 Catalogs, Matrices, and Diagrams 113
5.3 Architectural Artifacts 115
5.4 Architecture Deliverables 119
5.5 Building Blocks 119
Chapter 6 The Enterprise Continuum 122
6.1 Overview of the Enterprise Continuum 122
6.1.1 The Enterprise Continuum and Architecture Re-Use 123
6.1.2 Using the Enterprise Continuum within the ADM 124
6.2 Architecture Partitioning 124
6.3 Architecture Repository 126
Chapter 7 TOGAF Reference Models 128
7.1 TOGAF Foundation Architecture 128
7.1.1 Technical Reference Model (TRM) 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
A.1 Introduction 138

Textauszug

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 architects, 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

•   Guidelines on tools 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 9, 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 meet the business directive for a new enterprise architecture, including the definition of an organization-specific architecture framework and tools, and the definition of 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. Define stakeholders. Validate the business context and create the Statement of Architecture Work. Obtain approvals.

Develop architectures at three levels: Business Information Systems Technology In each case, develop the Baseline and Target Architectureand analyze gaps.

Perform initial implementation planning and the identification of delivery vehicles for the building blocks identified in the previous phases. Identify major implementation projects, and group them into Transition Architectures.

Analyze cost benefits and risk. Develop detailed Implementation and Migration Plan.

Provide architectural oversight for the implementation. Prepare and issue Architecture Contracts (Implementation Governance Board). 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

To review the organizational context forconducting enterprise architecture To identify the stakeholders, their requirements, and priorities To confirm the commitment of the stakeholders To identify and scope the elements of the enterprise organizations affected and define the constraints and assumptions; this is particularly important for large organizations where there may be a federated architecture environment To define an organization’s “architecture footprint”; that is, the people responsible for performing the architecture work, where they are located, and their responsibilities To define the framework and detailed methodologies that are going to be used to develop the enterprise architecture in the organization; this is typically an adaptation of the ADM To set up a governance and support framework to provide business process and architecture governance through the ADM cycle; these will confirm the fitness-for-purpose and ongoing effectiveness of the Target Architecture; normally this includes an initial pilot project To select and implement supporting tools and other infrastructure to support the architecture activity To define the constraining 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 Select and tailor architecture framework(s) Implement architecture tools

Inputs

Outputs

TOGAF Other architecture framework(s) Business principles, business goals, and business drivers Architecture governance strategy IT strategy Existing organizational model for enterprise architecture Existing architecture framework, if any Existing architecture principles, if any Existing Architecture Repository, if any

Organizational model forenterprise architecture Tailored Architecture Framework, including architecture principles Initial Architecture Repository Restatement of, or reference to, business principles, businessgoals, 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

Obtain management commitment for thisparticular cycle of the ADM Define and organize an architecture development cycle Validate business principles, goals, drivers, and key performance indicators (KPIs) Define, scope, and prioritize architecture tasks Identify stakeholders, their concerns, and objectives Define business requirements and constraints Articulate an Architecture Vision and valueproposition to respond to the requirements and constraints Create a comprehensive plan in line with theproject management frameworks adopted bythe enterprise Obtain formal approval to proceed Understand the impact on, and of, otherparallel architecture development cycles

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...

Produkt-Details

• Erscheint lt. Verlag: 2.2.2009
• Sprache: englisch
• Themenwelt: Mathematik / Informatik ► Informatik ► Theorie / Studium
• Themenwelt: Sozialwissenschaften ► Pädagogik
• ISBN-10: 90-8753-602-X / 908753602X
• ISBN-13: 978-90-8753-602-2 / 9789087536022