Loading presentation...

Present Remotely

Send the link below via email or IM


Present to your audience

Start remote presentation

  • Invited audience members will follow you as you navigate and present
  • People invited to a presentation do not need a Prezi account
  • This link expires 10 minutes after you close the presentation
  • A maximum of 30 users can follow your presentation
  • Learn more about this feature in our knowledge base article

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.


TOGAF Overview

overview of The Open Group Architecture Framework 9.1

tout web

on 28 October 2013

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of TOGAF Overview

what is it?
TOGAF provides a set of activities to be done in a transformation program.
The activities are grouped in ordered phases.
The cycle is iterative. The cycle is requirement-driven.
When an organization runs the ADM cycle, actors produce and use content. This content has to be structured, stored and shared. Togaf® describes how to structure your architecture repository.
TOGAF means The Open Group Architecture Framework.
TOGAF describes what an enterprise should do to successfully manage a transformation program.
TOGAF is a framework, allowing you to freely adapt it to to create your own way.
Structure and Classify
Description of the Architecture
Togaf® uses the concept of point of view and views to describe the content. Togaf® proposes a way to describe the content, the artifacts. Togaf® provides a modular meta model.
A building block is the basic component of an architecture. To describe a building block or a set of building blocks, you use architectural artifacts. Some artifacts are considered as architectural deliverables as they are playing a specific role in the course of the ADM cycle.
Artifacts & Deliverables
ADM: Architecture Development Method
Togaf provides guidelines to adapt the cycle.
Togaf indicates somes techniques to be used during the cycle.
Guidelines & Techniques
Your ability to build a fit-for-purpose enterprise architecture depends on your Enterprise Architecture Capability. This business capability has to be managed as any other business capabilities, wisely and incrementally.
The success or failure of enterprise architecture initiative is deeply linked with an effective governance. Be sure to be in control and to be business focused.
Nothing is possible without skilled people. The skills framework helps you to understand and develop the skills of every stakeholder of enterprise architecture approach, especially the soft skills.
Is your enterprise architecture capability good enough ? Assess the maturity of your enterprise architecture capability. Here some hints to help you.
Architecture Development Method
Phase A: Architecture Vision
Phase B: Business Architecture
Phase C: Information Systems Architectures
(Data Architecture and Applications Architecture)
Phase D: Technology Architecture
Phase E: Opportunities and Solutions
Phase F: Migration Planning
Phase G: Implementation Governance
Phase H: Architecture Change Management
ADM Architecture Requirements Management
Techniques for the ADM
Guidelines for the ADM
Introduction to the ADM
Architecture Repository
Architecture Landscape
Reference Library
Architecture Meta Model
Governance Log
Architecture Capability
Standards Information Base
Content Framework
How do you describe the system?
How do we structure and share the content?
Viewpoints and Views
Organization & Maturity
Skills categories
Proficiency Levels
Architecture Board
Architecture Contract
Conformance Review
Contact us
A proven way of developing an architecture
Specifically designed to address business requirements
An iterative method
A set of architecture views to ensure that a complex set of requirements are adequately addressed
The core of TOGAF
The Architecture Content Framework provides a detailed model of architectural work products, including Deliverables, Artifacts within deliverables, and the Architecture Building Blocks (ABBs) that deliverables represent.

It drives for greater consistency in the outputs of TOGAF
It provides a comprehensive checklist of architecture outputs
It promotes better integration of work products
It provides a detailed open standard for how architectures should be described
It includes a detailed metamodel
The Architecture Capability Framework provides guidance on establishing an operational enterprise architecture practice
The Architecture Content Framework provides three categories to describe architectural work products:
Building blocks
Formal products Contractually specified Outputs from a project

A deliverable can contain many artifacts
Building Blocks
components that can be combined with other building blocks to deliver architectures and solutions
Artifacts are fine grained products that describe an architecture from a specific viewpoint

Classified as:
catalogs (lists of things),
matrices (showing relationships between things)
diagrams (pictures of things).

Artifacts make up the content of the Architecture Repository
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 Capability
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 Framework(s)
Implement Architecture Tools
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 Business Transformation Risks and Mitigation Activities
Develop Statement of Architecture Work; Secure Approval
Develop the Target Business Architecture that describes how the enterprise needs to operate to achieve the business goals, and respond to the strategic drivers set out in the Architecture Vision, in a way that addresses the Request for Architecture Work and stakeholder concerns
Identify candidate Architecture Roadmap components based upon gaps between the Baseline and Target Business Architectures
Select Reference Models, Viewpoints, and Tools
Develop Baseline Business Architecture Description
Develop Target Business Architecture Description
Perform Gap Analysis
Define Candidate Roadmap Components
Resolve Impacts Across the Architecture Landscape
Conduct Formal Stakeholder Review
Finalize the Business Architecture
Create Architecture Definition Document
Develop the Target Data and Application Architecture that enables the Business Architecture and the Architecture Vision, while addressing the Request for Architecture Work and stakeholder concerns
Identify candidate Architecture Roadmap components based upon gaps between the Baseline and Target Data and Application Architectures
Select Reference Models, Viewpoints, and Tools
Develop Baseline Business Architecture Description
Develop Target Business Architecture Description
Perform Gap Analysis
Define Candidate Roadmap Components
Resolve Impacts Across the Architecture Landscape
Conduct Formal Stakeholder Review
Finalize the Business Architecture
Create Architecture Definition Document
Select Reference Models, Viewpoints, and Tools
Develop Baseline Business Architecture Description
Develop Target Business Architecture Description
Perform Gap Analysis
Define Candidate Roadmap Components
Resolve Impacts Across the Architecture Landscape
Conduct Formal Stakeholder Review
Finalize the Business Architecture
Create Architecture Definition Document
Develop the Target Technology Architecture that enables the logical and physical application and data components and the Architecture Vision, addressing the Request for Architecture Work and stakeholder concerns
Identify candidate Architecture Roadmap components based upon gaps between the Baseline and Target Technology Architectures
Generate the initial complete version of the Architecture Roadmap, based upon the gap analysis and candidate Architecture Roadmap components from Phases B, C, and D
Determine whether an incremental approach is required, and if so identify Transition Architectures that will deliver continuous business value
Determine/Confirm Key Corporate Change Attributes
Determine Business Constraints for Implementation
Review and Consolidate Gap Analysis Results from Phases B to D
Review Consolidated Requirements Across Related Business Functions
Consolidate and Reconcile Interoperability Requirements
Refine and Validate Dependencies
Confirm Readiness and Risk for Business Transformation
Formulate Implementation and Migration Strategy
Identify and Group Major Work Packages
Identify Transition Architectures
Create the Architecture Roadmap & Implementation and Migration Plan
Finalize the Architecture Roadmap and the supporting Implementation and Migration Plan
Ensure that the Implementation and Migration Plan is coordinated with the enterprise's approach to managing and implementing change in the enterprise's overall change portfolio
Ensure that the business value and cost of work packages and Transition Architectures is understood by key stakeholders
Confirm Management Framework Interactions for the Implementation and Migration Plan
Assign a Business Value to Each Work Package
Estimate Resource Requirements, Project Timings, and Availability/Delivery Vehicle
Prioritize the Migration Projects through the Conduct of a Cost/Benefit Assessment and Risk Validation
Confirm Architecture Roadmap and Update Architecture Definition Document
Generate the Implementation and Migration Plan
Complete the Architecture Development Cycle and Document Lessons Learned
Ensure conformance with the Target Architecture by implementation projects
Perform appropriate Architecture Governance functions for the solution and any implementation-driven architecture Change Requests
Confirm Scope and Priorities for Deployment with Development Management
Identify Deployment Resources and Skills
Guide Development of Solutions Deployment
Perform Enterprise Architecture Compliance Reviews
Implement Business and IT Operations
Perform Post-Implementation Review and Close the Implementation
Ensure that the architecture lifecycle is maintained
Ensure that the Architecture Governance Framework is executed
Ensure that the enterprise Architecture Capability meets current requirements
Establish Value Realization Process
Deploy Monitoring Tools
Manage Risks
Provide Analysis for Architecture Change Management
Develop Change Requirements to Meet Performance Targets
Manage Governance Process
Activate the Process to Implement Change
Ensure that the Requirements Management process is sustained and operates for all relevant ADM phases
Manage architecture requirements identified during any execution of the ADM cycle or a phase
Ensure that relevant architecture requirements are available for use by each phase as the phase is executed
Architecture Principles - principles for the use and deployment of IT resources across the enterprise - describes how to develop the set of general rules and guidelines for the architecture being developed.
Stakeholder Management describes Stakeholder Management, an important discipline that successful architecture practitioners can use to win support for their projects.
Architecture Patterns provides guidance on using architectural patterns.
Business Scenarios describes the Business Scenarios technique, a method for deriving business requirements for architecture and the implied technical requirements.
Gap Analysis describes the technique known as gap analysis. It is widely used in the TOGAF ADM to validate an architecture that is being developed.
Migration Planning Techniques describes a number of techniques to support migration planning in Phases E and F.
Interoperability Requirements describes a technique for determining interoperability requirements.
Business Transformation Readiness Assessment describes a technique for identifying business transformation issues.
Risk Management describes a technique for managing risk during an architecture/business transformation project.
Capability-Based Planning describes the technique of capability-based planning.
Applying Iteration to the ADM discusses the concept of iteration and shows potential strategies for applying iterative concepts to the ADM.

Applying the ADM across the Architecture Landscape discusses the different types of architecture engagement that may occur at different levels of the enterprise. This section then also discusses how the ADM process can be focused to support different types of engagement.

Security Architecture and the ADM provides an overview of specific security considerations that should be considered during different phases of the ADM.

Using TOGAF to Define & Govern SOAs shows how SOA concepts can be supported by the TOGAF framework and the specific SOA considerations for different phases of the ADM.
The Architecture Metamodel describes the organizationally tailored application of an architecture framework, including a method for architecture development and a metamodel for architecture content.
The Architecture Capability defines the parameters, structures, and processes that support governance of the Architecture Repository
The Architecture Landscape presents an architectural representation of assets in use, or planned, by the enterprise at particular points in time.
The Standards Information Base captures the standards with which new architectures must comply, which may include industry standards, selected products and services from suppliers, or shared services already deployed within the organization.
The Reference Library provides guidelines, templates, patterns, and other forms of reference material that can be leveraged in order to accelerate the creation of new architectures for the enterprise.
The Governance Log provides a record of governance activity across the enterprise
Organizations that can manage change effectively are generally more successful than those that cannot.

Capability Maturity Models (CMMs) address this problem by providing an effective and proven method for an organization to gradually gain control over and improve its change processes.

It indicates the organization's ability to execute in the area concerned, and the practices on which the organization needs to focus in order to see the greatest improvement and the highest return on investment. The benefits of CMMs to effectively direct effort are well documented.
A key element in a successful architecture governance strategy is a cross-organization Architecture Board to oversee the implementation of the strategy.
This body should be representative of all the key stakeholders in the architecture, and will typically comprise a group of executives responsible for the review and maintenance of the overall architecture.
Architecture Boards may have global, regional, or business line scope.
Architecture Contracts are the joint agreements between development partners and sponsors on the deliverables, quality, and fitness-for-purpose of an architecture. Successful implementation of these agreements will be delivered through effective architecture governance
Ensuring the compliance of individual projects with the enterprise architecture is an essential aspect of architecture governance
Generic Skills: - typically comprising leadership, teamworking, inter-personal skills, etc.
Business Skills & Methods: - typically comprising business cases, business process, strategic planning, etc.
Enterprise Architecture Skills: - typically comprising modeling, building block design, applications and role design, systems integration, etc.
Program or Project Management Skills: - typically comprising managing business change, project management methods and tools, etc.
IT General Knowledge Skills: - typically comprising brokering applications, asset management, migration planning, SLAs, etc.
Technical IT Skills: - typically comprising software engineering, security, data interchange, data management, etc.
Legal Environment: - typically comprising data protection laws, contract law, procurement law, fraud, etc.
Architecture Building Blocks
Architecture Contract
Architecture Definition Document
Architecture Principles
Architecture Repository
Architecture Requirements Specification
Architecture Roadmap
Architecture Vision
Business Principles, Business Goals, and Business Drivers
Capability Assessment
Change Request
Communications Plan
Compliance Assessment
Implementation and Migration Plan
Implementation Governance Model
Organizational Model for Enterprise Architecture
Request for Architecture Work
Requirements Impact Assessment
Solution Building Blocks
Statement of Architecture Work
Tailored Architecture Framework
You should adapt these deliverables
You already have a lot of good deliverables
use them first and complete them with Togaf-inspired one
Where do we share the knowledge about the system?
Do we re-use good stuff?
Do we adhere to specific standards?
Do we build a lasting capability?
Are decisions traced and enforced ?
How do we define our way to make enterprise architecture?
Architectural Artifacts by ADM Phase
Togaf provides a list of typical artifacts.

That is a starter point for your tailored viewpoint library.

Grouping the viewpoints and artifacts by phase eases the use of them.
The choice of which particular architecture views to develop is one of the key decisions that the architect has to make.

The architect has a responsibility for ensuring the completeness (fitness-for-purpose) of the architecture, in terms of adequately addressing all the pertinent concerns of its stakeholders; and the integrity of the architecture, in terms of connecting all the various views to each other, satisfactorily reconciling the conflicting concerns of different stakeholders, and showing the trade-offs made in so doing (as between security and performance, for example).

The choice has to be constrained by considerations of practicality, and by the principle of fitness-for-purpose (i.e., the architecture should be developed only to the point at which it is fit-for-purpose, and not reiterated ad infinitum as an academic exercise).
a Content Meta Model
Start with the core and enrich with additional extensions
Skills Matrix
for each skill category
Deliverables are inputs and ouputs of the ADM phases
Full transcript