Togaf introduction ver1 0

TOGAF Introduction

Crop Circle Overview

Preliminary Phase

• Steps1. Scope the enterprise organizations impacted

2. Confirm governance and support frameworks

3. Define and establish the enterprise architecture team and organization

4. Identify and establish architecture principles

5. Select and tailor Architecture Framework(s)

6. Implement architecture tools

• Outputs1. Organizational Model for Enterprise

Architecture

2. Tailored Architecture Framework, including architecture principles

3. Initial Architecture Repository

4. Restatement of, or reference to, business principles, business goals, and business drivers

5. Request for Architecture Work

6. Governance Framework

• Inputs1. TOGAF2. Other Architecture Framework(s)3. Business principles, business goals, and

business drivers4. Architecture Governance strategy5. IT strategy6. Existing Organizational Model for Enterprise

Architecture7. Existing Architecture Framework, if any8. Existing architecture principles, if any9. Existing Architecture Repository, if any

Preliminary Phase

• The following catalogs, matrices, and diagrams may be produced in (Preliminary).– Catalogs:

• Principles Catalog

– Matrices:• Stakeholder Map Matrix

– Core diagrams:• None

– Extension diagrams:• None

Phase A: Architecture Vision

• Steps1. Establish the architecture project

2. Identify stakeholders, concerns, and business requirements

3. Confirm and elaborate business goals, business drivers, and constraints

4. Evaluate business capabilities

5. Assess readiness for business transformation

6. Define scope

• Outputs1. Statement of Architecture Work

2. Refined statements of business principles, business goals, and business drivers

3. Architecture principles

4. Capability assessment

5. Tailored Architecture Framework

6. Architecture Vision, including:

1. Refined key high-level stakeholder requirements

2. Baseline Architecture (vision)

3. Target Architecture (vision)

7. Communications Plan

8. Additional content populating the Architecture Repository

• Inputs1. Request for Architecture Work2. Business principles, business goals, and

business drivers3. Organizational Model for Enterprise

Architecture4. Tailored Architecture Framework,

including architecture principles5. Populated Architecture Repository; that

is, existing architecture documentation (framework description, architecture descriptions, existing Baseline descriptions, etc.)

• Steps7. Confirm and elaborate architecture principles,

including business principles

8. Develop Architecture Vision

9. Define the Target Architecture value propositions and KPIs

10. Identify the business transformation risks and mitigation activities

11. Develop enterprise architecture plans and the Statement of Architecture Work; secure approval

Phase A: Architecture Vision

• The following catalogs, matrices, and diagrams may be produced in Phase A (Architecture Vision).– Catalogs:

• None

– Matrices:• None

– Core diagrams:• Value Chain Diagram

• Solution Concept Diagram

– Extension diagrams:• None

Phase B: Business Architecture

• Steps1. Select reference models, viewpoints, and tools2. Develop Baseline Business Architecture Description3. Develop Target Business Architecture Description4. Perform Gap Analysis5. Define roadmap components6. Resolve impacts across the Architecture Landscape7. Conduct formal stakeholder review8. Finalize the Business Architecture9. Create the Architecture Definition Document

• Outputs1. Statement of Architecture Work, updated

if necessary Validated business principles, business goals, and business drivers

2. Elaborated Business Architecture principles

3. Draft Architecture Definition Document containing content updates

4. Draft Architecture Requirements Specification including content updates

• Inputs1. Request for Architecture Work

2. Business principles, business goals, and business drivers

3. Capability Assessment


5. Organizational Model for Enterprise Architecture


7. Approved Statement of Architecture Work

8. Architecture principles, including business principles, when pre-existing

9. Enterprise Continuum

10. Architecture Repository

11. Architecture Vision

Phase B: Business Architecture

• The following catalogs, matrices, and diagrams may be produced in Phase B (Business Architecture).– Catalogs:

• Organization/Actor catalog

• Driver/Goal/Objective catalog

• Role catalog

• Business Service/Function catalog

• Location catalog

• Process/Event/Control/Product catalog

• Contract/Measure catalog

– Matrices:• Business Interaction matrix

• Actor/Role matrix

– Core diagrams:• Business Footprint Diagram

• Business Service/ Information diagram

• Functional Decomposition diagram

• Product Lifecycle diagram

– Extension diagrams:• No extension diagrams are defined to be created

during Phase A.

• Goal/Objective/Ser vice diagram

• Use-case diagram

• Organization Decomposition diagram

• Process Flow diagram

• Event diagram

Phase C: Data Architecture

• Steps1. Select reference models, viewpoints, and tools2. Develop Baseline Data Architecture Description3. Develop Target Data Architecture Description4. Perform Gap Analysis5. Define roadmap components6. Resolve impacts across the Architecture Landscape7. Conduct formal stakeholder review8. Finalize the Data Architecture9. Create Architecture Definition Document

• Outputs1. Statement of Architecture Work, updated if

necessary

2. Validated data principles, or new data principles

3. Draft Architecture Definition Document, containing content updates

4. Draft Architecture Requirements Specification, including content updates

5. Data Architecture components of an Architecture Roadmap

• Inputs






6. Application principles

7. Data principles, if existing

8. Statement of Architecture Work



11. Draft Architecture Definition Document:1. Baseline Architecture (detailed or vision)

2. Target Architecture (detailed or vision)

12. Draft Architecture Requirements Specification:1. Gap Analysis results

2. Relevant technical requirements

13. Business Architecture components of an Architecture Roadmap

Phase C: Data Architecture

• The following catalogs, matrices, and diagrams may be produced in Phase C (Data Architecture).– Catalogs:

• Data Entity/Data Component Catalog

– Matrices:• Data Entity/Business Function Matrix

• System Data Matrix

– Core diagrams:• Class Diagram

• Data Dissemination Diagram

– Extension diagrams:• Data Security Diagram

• Class Hierarchy Diagram

• Data Migration Diagram

• Data Lifecycle Diagram

Phase C: Application Architecture

• Steps1. Select reference models, viewpoints, and tools2. Develop Baseline Application Architecture Description3. Develop Target Application Architecture Description4. Perform Gap Analysis5. Define roadmap components6. Resolve impacts across the Architecture Landscape7. Conduct formal stakeholder review8. Finalize the Application Architecture9. Create Architecture Definition Document


necessary

2. Validated application principles, or new application principles

3. Draft Architecture Definition Document, containing content updates.

4. Draft Architecture Requirements Specification, including content updates

5. Application Architecture components of an Architecture Roadmap

• Inputs






6. Application principles

7. Data principles




11. Draft Architecture Definition Document:1. Baseline Architecture (detailed or vision)

2. Target Architecture (detailed or vision)



13. • Business Architecture components of an Architecture Roadmap

Phase C: Application Architecture

• The following catalogs, matrices, and diagrams may be produced in Phase C (Application Architecture).– Catalogs:

• Application Portfolio Catalog

• Interface Catalog

– Matrices:• System/Organisation Matrix

• Role/System Matrix

• System / Function Matrix

• Application Interaction Matrix

– Core diagrams:• Application Communication Diagram

• Application and User Location Diagram

• System Use-Case Diagram

– Extension diagrams:• Enterprise Manageability Diagram

• Process / System Realisation Diagram

• Software Engineering Diagram

• Application Migration Diagram

• Software Distribution Diagram

Phase D: Technology Architecture

• Steps1. Select reference models, viewpoints, and tools2. Develop Baseline Application Architecture Description3. Develop Target Application Architecture Description4. Perform Gap Analysis5. Define roadmap components6. Resolve impacts across the Architecture Landscape7. Conduct formal stakeholder review8. Finalize the Application Architecture9. Create Architecture Definition Document


necessary

2. Validated technology principles or new technology principles (if generated here)

3. Draft Architecture Definition Document, containing content updates

4. Draft Architecture Requirements Specification , including content updates

5. Technology Architecture components of an Architecture Roadmap

• Inputs






6. Technology principles




10. Draft Architecture Definition Document:1. Baseline Architecture (detailed)

2. Target Architecture (detailed)



12. Business, Data, and Application Architecture components of an Architecture Roadmap

Phase D: Technology Architecture

• The following catalogs, matrices, and diagrams may be produced in Phase D (Technology Architecture).– Catalogs:

• Technology Standards Catalog

• Technology Portfolio Catalog

– Matrices:• System / Technology Matrix

– Core diagrams:• Environments and Location Diagram

• Platform Decomposition Diagram

– Extension diagrams:• Processing Diagram

• Networked Computing / Hardware Diagram

• Communications Engineering Diagram

Phase E: Opportunities and Solutions

• Steps1. Determine/confirm key corporate change attributes2. Determine business constraints for implementation3. Review and consolidate Gap Analysis results from Phases B to D4. Review IT requirements from a functional perspective5. Consolidate and reconcile interoperability requirements6. Refine and validate dependencies7. Confirm readiness and risk for business transformation8. Formulate high-level Implementation and Migration Strategy9. Identify and group major work packages10. Identify Transition Architectures11. Create portfolio and project charters and update the architectures

• Outputs1. Statement of Architecture Work, updated if necessary

2. Architecture Vision, updated if necessary

3. Draft Architecture Definition Document, including content updates for:

1. Identification of increments

2. Interoperability and co-existence requirements

3. Implementation and Migration Strategy

4. Inclusion of project list and project charters

4. Draft Architecture Requirements Specification, updated if necessary

5. Capability Assessment, including content updates for:1. Enterprise Architecture Maturity Profile

2. Transformation Readiness Report

6. Transition Architectures (see Section 10.5.2), including:1. Consolidated Gaps, Solutions, and Dependencies Assessment

2. Risk Register

3. Impact analysis – project list

4. Dependency Analysis Report

5. Implementation Factor Assessment and Deduction matrix

7. Implementation and Migration Plan (outline)

• Inputs

1. Product information




5. Planning Methodologies






11. Draft Architecture Definition Document

12. Draft Architecture Requirements Specification

13. Change Requests for existing programs and projects

Phase E: Opportunities and Solutions

• The following catalogs, matrices, and diagrams may be produced in Phase E (Opportunities and Solutions).– Catalogs:

• No catalogs are defined to be created during Phase E.

– Matrices:• No matrices are defined to be created during Phase E.

– Core diagrams:• Project Context Diagram

• Benefits Diagram

– Extension diagrams:• No extension diagrams are defined to be created during

Phase E.

Phase F: Migration Planning

• Steps1. Confirm management framework interactions for the Implementation and Migration Plan2. Assign a business value to each project3. Estimate resource requirements, project timings, and availability/delivery vehicle4. Prioritize the migration projects through the conduct of a cost/benefit assessment and risk validation5. Confirm Transition Architecture increments/phases and update Architecture Definition Document6. Generate the Architecture Implementation Roadmap (time-lined) and Migration Plan7. Establish the architecture evolution cycle and document lessons learned

• Outputs1. Implementation and Migration Plan (detailed)

2. Finalized Architecture Definition Document

3. Finalized Architecture Requirements Specification

4. Finalized Architecture Roadmap

5. Transition Architecture

6. Re-Usable Architecture Building Blocks (ABBs)

7. Requests for Architecture Work for the architecture aspects of implementation projects (if any)

8. Architecture Contracts for implementation projects

9. Implementation Governance Model

10. Change Requests arising from lessons learned

• Inputs





5. Governance Models and Frameworks





10. Draft Architecture Definition Document, including:1. Strategic Migration Plan

2. Impact analysis – project list and charters

11. Draft Architecture Requirements Specification

12. Change Requests for existing programs and projects

13. Consolidated and validated Architecture Roadmap

14. Transition Architectures

15. Implementation and Migration Plan (outline)

Phase G: Implementation Governance

• Steps1. Confirm scope and priorities for deployment with development management2. Identify deployment resources and skills3. Guide development of solutions deployment4. Perform enterprise Architecture Compliance Reviews5. Implement business and IT operations6. Perform post-implementation review and close the implementation

• Outputs1. Implementation and Migration Plan (detailed)

2. Architecture Contract (signed) (see Section 11.5.1)

3. Compliance Assessments

4. Change Requests

5. Impact Analysis – Implementation Recommendations

6. Architecture-compliant solutions deployed, including:1. The architecture-compliant implemented system

2. Populated Architecture Repository

3. Architecture compliance recommendations and dispensations

4. Recommendations on service delivery requirements

5. Recommendations on performance metrics

6. Service Level Agreements (SLAs)

7. Architecture Vision, updated post-implementation

8. Architecture Definition Document, updated post-implementation

9. Transition Architecture, updated post-implementation

10. Business and IT operating models for the implemented solution

• Inputs1. Request for Architecture Work







8. Architecture Definition Document

9. Architecture Requirements Specification

10. Architecture Roadmap



13. Architecture Contract

14. Request for Architecture Work identified in Phases E and F

15. Implementation and Migration Plan

Phase H: Architecture Change Management

• Steps1. Establish value realization process2. Deploy monitoring tools3. Manage risks4. Provide analysis for architecture change management5. Develop change requirements to meet performance targets6. Manage governance process7. Activate the process to implement change

• Outputs1. Architecture updates

2. Changes to Architecture Framework and principles

3. New Request for Architecture Work, to initiate another cycle of the ADM

4. Statement of Architecture Work, updated if necessary

5. Architecture Contract, updated if necessary

6. Compliance Assessments, updated if necessary

• Inputs1. Request for Architecture Work identified in Phases E and F






7. Architecture Definition Document

8. Architecture Requirements Specification

9. Architecture Roadmap

10. Change Requests due to technology changes

11. Change Requests due to business changes

12. Change Requests from lessons learned



15. Architecture Contract (signed)

16. Compliance Assessments

17. Implementation and Migration Plan

Requirements Management

• Steps

1. Baseline requirements:

1. Determine priorities arising from current phase of ADM

2. Confirm stakeholder buy-in to resultant priorities

3. Record requirements priorities and place in requirements repository

2. Monitor baseline requirements

3. Identify changed requirements and record priorities:1. Identify changed requirements. Ensure the

requirements are prioritized by the architect(s) responsible for the current phases and by the relevant stakeholders

• Outputs1. Changed requirements in the Architecture

Requirements Specification

2. Requirements Impact Assessment, which identifies the phases of the ADM that need to be revisited to address any changes.

3. The final version must include the full implications of the requirements (e.g., costs, timescales, and business metrics).

• Inputs1. The inputs to the Requirements

Management process are the requirements-related outputs from each ADM phase.

2. The first high-level requirements are produced as part of the Architecture Vision.

3. Each architecture domain then generates detailed requirements.

4. Deliverables in later ADM phases contain mappings to new types of requirements (e.g., conformance requirements).

• Steps2. Record new priorities

3. Ensure that any conflicts are identified and managed throughout the phases

4. Generate Requirements Impact Statement for steering the architecture team

4. Update the requirements repository with information relating to the changes requested, including stakeholder views affected.

Viewpoints for Requirements Management

• The following catalogs, matrices, and diagrams may be produced in the Requirements Management Phase.– Catalogs:

• Requirements Management Catalog.

– Matrices:• No matrices are defined to be created during

Requirements Management Phase.

– Core diagrams:• No core diagrams are defined to be created

during the Requirements Management phase.

– Extension diagrams:• No extension diagrams are defined to be created

during the Requirements Management phase.

If you have one last breath use it to say...

Togaf introduction ver1 0

Technology

Transcript of Togaf introduction ver1 0