Copyright © The Open Group 2011 Your Name Your title 44 Montgomery Street Suite 960 San Francisco, CA 94104 USA Tel +1 415 374 8280.

Slides:



Advertisements
Similar presentations
© 2007 BigVisible Solutions, Inc. All Rights Reserved Coaching Solutions Agile Project Start v
Advertisements

Scope of TOGAF ADM The scope of the four architecture domains of TOGAF align very well with the first four rows of the Zachman Framework, as shown in the.
0 Chicago, IL March 6 th, 2007 Use Case Requirements, Design and Standards Selection HITSP Use Case Requirements, Design and Standards Selection Date:
The Open Group Architecture Framework (TOGAF) Version 7.
Guidelines and Tools for ADM
Sixth Hour Lecture 10:30 – 11:20 am, September 9 Framework for a Software Management Process – Artifacts of the Process (Part II, Chapter 6 of Royce’ book)
TOGAF 9 Fundamental: 3. Core Concepts
Tool support for Enterprise Architecture in System Architect Architecture Practitioners Conference, Brussels David Harrison Senior Consultant, Popkin.
Extended Enterprise Architecture Framework (E2AF)
Enterprise Architecture
TOGAF 9 Fundamental: 2. Basic Concepts
Developing Enterprise Architecture
An Introduction to the new features in TOGAF® 9
The draft NSW English K-10 syllabus Version 2 February, 2012.
An Overview of TOGAF® Version 9.1
UML - Development Process 1 Software Development Process Using UML (2)
Introduction to RUP Spring Sharif Univ. of Tech.2 Outlines What is RUP? RUP Phases –Inception –Elaboration –Construction –Transition.
Software Engineering Chapter 15 Construction Leads to Initial Operational Capability Fall 2001.
Engineering, Operations & Technology | Information TechnologyAPEX | 1 Copyright © 2009 Boeing. All rights reserved. Architecture Concept UG D- DOC UG D-
Architectures review for interoperability in e-health
Thirteenth Lecture Hour 8:30 – 9:20 am, Sunday, September 16 Software Management Disciplines Process Automation (from Part III, Chapter 12 of Royce’ book)
Demystifying the Business Analysis Body of Knowledge Central Iowa IIBA Chapter December 7, 2005.
The Challenge of IT-Business Alignment
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
The Guide to the Software Engineering Body of Knowledge
RUP Design RUP Artifacts and Deliverables
Essential SNA Project being developed from 2011 to 2013.
February 28, 2008The Teaching Center, Washington University The Teaching Citation Program & Creating a Teaching Portfolio Beth Fisher, Ph.D. Assistant.
CHECKPOINTS OF THE PROCESS Three sequences of project checkpoints are used to synchronize stakeholder expectations throughout the lifecycle: 1)Major milestones,
The Open Group Architecture Framework (TOGAF) Version 7 John Spencer, Director – Architecture Forum Anaheim, January 24 th 2002.
Standards Certification Education & Training Publishing Conferences & Exhibits 1Copyright © 2006 ISA ISA-SP99: Security for Industrial Automation and Control.
Chapter 10 Analysis and Design Discipline. 2 Purpose The purpose is to translate the requirements into a specification that describes how to implement.
@2002 Copyright, Itreya Technologies CMMI kick off July 2005.
PMI’s “Project Manager” Role Delineation Explored The PMP ® Certification & Examination Eligibility Changes Explored The PMBOK ® 5 th Edition Detailed.
Copyright © The Open Group 2014 Your Name Your title 44 Montgomery Street Suite 960 San Francisco, CA USA Tel
PRJ566 Project Planning & Management Software Architecture.
1 Sobah Abbas Petersen Adjunct Associate Professor TDT4252 Modelling of Information Systems Advanced Course TDT4252, Spring 2011 Lecture.
Copyright © The Open Group 2011 Your Name Your title 44 Montgomery Street Suite 960 San Francisco, CA USA Tel
Enterprise Engineering Directorate (EE)
Introduction Data Modeling and Relational Database Design.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
EA Workflows 1 Establish EA Program Recruit EA Chief Architect Establish EA Governance Rules Prepare Stakeholder Communications Plan Prepare Stakeholder.
Enterprise Architectures Course Code : CPIS-352 King Abdul Aziz University, Jeddah Saudi Arabia.
ICT occupation specific capability set (Skills Framework for the Information Age - SFIA) An introduction.
Enterprise Architectures. Core Concepts Key Learning Points: This chapter will help you to answer the following questions: What are the ADM phase names.
Viewpoint Modeling and Model-Based Media Generation for Systems Engineers Automatic View and Document Generation for Scalable Model- Based Engineering.
Basic Concepts Key Learning Points : The objectives of this chapter are as follows:  To provide an introduction to the basic Concepts of enterprise architectures,
Enterprise Architectures Course Code : CPIS-352 King Abdul Aziz University, Jeddah Saudi Arabia.
Enterprise Architectures Course Code : CPIS-352 King Abdul Aziz University, Jeddah Saudi Arabia.
Enterprise Architectures Course Code : CPIS-352 King Abdul Aziz University, Jeddah Saudi Arabia.
Enterprise Architectures Course Code : CPIS-352 King Abdul Aziz University, Jeddah Saudi Arabia.
Information Technology Project Management, Seventh Edition.
ENTERPRISE ARCHITECTURE APPROACH - TOGAF 9 - Prashant Patade (Enterprise Architect) S trategic P rojects and C ore T echnology G roup - IT.
PMBOK Guide – Third Edition: Updates from PMBOK Guide – 2000 Edition Long Island Chapter - PMI1 May 2005 PMBOK Guide – Third Edition Focus on Changes.
Michael J. Novak ASQ Section 0511 Meeting, February 8, 2017
Understanding Enterprise Architecture
What is Enterprise Architecture?
ARIS Extension Pack TOGAF April 2016
TOGAF 9.1 By: Samuel Mandebvu Sources: Primary Slide Deck
Structure of the Code Phase 1
Review of the Massachusetts History and Social Science Curriculum Frameworks Board of Elementary and Secondary Education January 23, 2018 Heather introduce.
The Open Group Architecture Framework (TOGAF)
The Open Group OG Exam Best Study Guide - OG Exam Questions Answers
Latest The Open Group OG0-091 Exam Dumps PDF Questions - OG0-091 Best Study Material - Realexamdumps.com
Download The Open Group OG0-093 Exam - Valid OG0-093 Question Answers - Realexamdumps.com
Enterprise Data Model Enterprise Architecture approach Insights on application for through-life collaboration 2018 – E. Jesson.
Structure of the Code Phase 1
Introducing ISTQB Agile Foundation Extending the ISTQB Program’s Support Further Presented by Rex Black, CTAL Copyright © 2014 ASTQB 1.
EA Framework TOGAF is a framework - a detailed method and a set of supporting tools - for developing an enterprise architecture.
Presentation transcript:

Copyright © The Open Group 2011 Your Name Your title 44 Montgomery Street Suite 960 San Francisco, CA USA Tel Fax TOGAF ® 9.1 Changes Overview TOGAF is a registered trademark of The Open Group in the United States and other countries Your card goes here!

Copyright © The Open Group 2011 Audience The audience for this presentation is Enterprise architects, business architects, data architects, systems architects, solutions architects and senior managers seeking an overview of what has changed between TOGAF 9 and TOGAF 9.1 A prior knowledge of TOGAF 9 is presumed

Copyright © The Open Group 2011 Objectives To understand The key changes between TOGAF 9 and TOGAF 9.1 The implications on the TOGAF 9 Certification program

Copyright © The Open Group 2011 Agenda TOGAF 9.1 Components and Structure TOGAF 9.1 Change Highlights TOGAF 9.1 Features Removed TOGAF 9.1 Features Revised TOGAF 9.1 and Certification Backup Slides TOGAF 9.1 Detailed Changes

Copyright © The Open Group 2011 TOGAF 9.1 TOGAF 9.1 was released in December 2011 It is the first maintenance update to TOGAF 9 It is an upwards-compatible evolution from TOGAF 9, addressing usage feedback and comments raised It addresses over 400 comments received Contains over 450 changes TOGAF 9 Technical Corrigendum 1 (Document U112) is available describing each change in detail

Copyright © The Open Group 2011 TOGAF 9.1 Components

Copyright © The Open Group 2011 Part I - Introduction Part II – Architecture Development Method Part III – ADM Guidelines and Techniques Part IV – Architecture Content Framework Part V – Enterprise Continuum and Tools Part VI – TOGAF Reference Models Part VII – Architecture Capability Framework Preface, Executive Overview, Core Concepts, Definitions and Release Notes Introduction to ADM ADM Phase Narratives Architectural Artifacts Architecture Deliverables Building Blocks Guidelines for Adapting the ADM Process Techniques for Architecture Development Enterprise Continuum Architecture Partitioning Architecture Repository Tools for Architecture Development Foundation Architecture: Technical Reference Model Integrated Information Infrastructure Reference Model Architecture Board Architecture Compliance Architecture Contracts Architecture Governance Architecture Maturity Models Architecture Skills Framework Content Metamodel

Copyright © The Open Group 2011 TOGAF 9.1 Change Highlights Part I - Introduction Part II – Architecture Development Method Part III – ADM Guidelines and Techniques Part IV – Architecture Content Framework Part V – Enterprise Continuum and Tools Part VI – Reference Models Part VII – Architecture Capability Framework Preface, Executive Overview, Core Concepts, Definitions and Release Notes Introduction to ADM ADM Phase Narratives Architectural Artifacts Architecture Deliverables Building Blocks Guidelines for Adapting the ADM Process Techniques for Architecture Development Enterprise Continuum Architecture Partitioning Architecture Repository Tools for Architecture Development Foundation Architecture: Technical Reference Model Integrated Information Infrastructure Reference Model Architecture Board Architecture Compliance Architecture Contracts Architecture Governance Architecture Maturity Models Architecture Skills Framework Minor editorial Improvements No changes Editorial improvements. The Tools Evaluation Criteria and Guidelines have been removed. The relationship of the Architecture Repository to the Enterprise Repository has been clarified Corrections have been made to the metamodel diagrams and to aspects of the metamodel. Reworked descriptions of Architectural Artifacts and Viewpoints. The Building Blocks Example has been removed Editorial improvements. SOA chapter revised to reflect latest work in The Open Group. Introductory text on Architectural styles added. The concepts of levels/iteration/partitions have been clarified and made consistent Editorial improvements. Objectives sections reworked. Phases E and F descriptions reworked Editorial improvements. Definitions clarified. The Document Categorization Model removed Content Metamodel

Copyright © The Open Group 2011 TOGAF 9.1: Material Removed The Document Categorization Model has been removed (Chapter 2) Definitions of terms where usage is not distinctive from the common dictionary definition have been removed (Chapter 3) The Building Blocks example has been removed (chapter 37) The Evaluation Criteria and Guidelines have been removed (Chapter 42) Part I - Introduction Part II – Architecture Development Method Part III – ADM Guidelines and Techniques Part IV – Architecture Content Framework Part V – Enterprise Continuum and Tools Part VI – Reference Models Part VII – Architecture Capability Framework Preface, Executive Overview, Core Concepts, Definitions and Release Notes Introduction to ADM ADM Phase Narratives Architectural Artifacts Architecture Deliverables Building Blocks Guidelines for Adapting the ADM Process Techniques for Architecture Development Enterprise Continuum Architecture Partitioning Architecture Repository Tools for Architecture Development Foundation Architecture: Technical Reference Model Integrated Information Infrastructure Reference Model Architecture Board Architecture Compliance Architecture Contracts Architecture Governance Architecture Maturity Models Architecture Skills Framework Content Metamodel

Copyright © The Open Group 2011 TOGAF 9.1: Material Revised The "Objectives" sections of the ADM phases have been reworked to focus on actual objectives rather than techniques or a list of steps (chaps 6-17) Phase E and F descriptions have been reworked to match the level of detail in other phases (chaps 13,14) The concepts of levels, Iterations and partitions have been clarified and made consistent. (chaps 19/20/40) Additional introductory text on architectural styles has been added in Part III, Chapter 18 The SOA chapter (Part III, Chapter 22) has been updated to describe the latest work from The Open Group Part I - Introduction Part II – Architecture Development Method Part III – ADM Guidelines and Techniques Part IV – Architecture Content Framework Part V – Enterprise Continuum and Tools Part VI – Reference Models Part VII – Architecture Capability Framework Preface, Executive Overview, Core Concepts, Definitions and Release Notes Introduction to ADM ADM Phase Narratives Architectural Artifacts Architecture Deliverables Building Blocks Guidelines for Adapting the ADM Process Techniques for Architecture Development Enterprise Continuum Architecture Partitioning Architecture Repository Tools for Architecture Development Foundation Architecture: Technical Reference Model Integrated Information Infrastructure Reference Model Architecture Board Architecture Compliance Architecture Contracts Architecture Governance Architecture Maturity Models Architecture Skills Framework Content Metamodel

Copyright © The Open Group 2011 TOGAF 9.1 and Certification The TOGAF 9 Certification for People Program has been designed to accommodate maintenance updates to the TOGAF 9 standard such as TOGAF 9.1 The two levels of certification remain as TOGAF 9 Foundation and TOGAF 9 Certified Individuals who are currently certified in the TOGAF 9 People Certification program remain certified The Conformance Requirements for TOGAF 9 Certification have been updated and will become mandatory on June 1, 2012 All Accredited TOGAF 9 Training Courses will be updated to the revised Conformance Requirements by June 1, 2012

Copyright © The Open Group 2011 TOGAF 9.1 and Certification In the period between December 1, 2011 and June 1, 2012 candidates can study either to the original Conformance Requirements or the revised Conformance Requirements The examinations have been designed to accommodate both up to June 2013, which allows candidates up to twelve months after studying to take the exam The reference text provided with the Open Book examinations will remain TOGAF 9 until June 1, 2012 and will then switch to TOGAF 9.1 after that date

Copyright © The Open Group 2011 TOGAF 9.1 and Certification December June June Accredited TOGAF 9 Training Courses can cover either TOGAF 9 or 9.1 up to and including May Accredited TOGAF 9Training Courses must cover TOGAF 9.1 from June The Examinations accommodate both TOGAF 9 and TOGAF 9.1 until June The extended period allows for candidates who study and obtain a 12 month exam voucher The exam questions can cover new TOGAF 9.1 material from June Open Book Reference Text changes to TOGAF 9.1 on June Open Book Reference Text TOGAF 9

Copyright © The Open Group 2011 TOGAF 9.1 Changes in Detail

Copyright © The Open Group 2011 TOGAF 9.1 Changes in Detail The Document Categorization Model has been removed (Section 2.8). Definitions of terms where usage by TOGAF is not distinctive from the common dictionary definition have been removed (Chapter 3). The usage of the terms “application” versus “system” have been reviewed and made consistent (global change). The “Objectives” sections of the phases have been reworked to focus on actual objectives rather than techniques or a list of steps (Chapters 6-17). The possible artifacts (viewpoints) for each phase are now listed in the description of that phase, not just in Part IV, Chapter 35: Architectural Artifacts (Chapters 6-17). Duplicate text in several places has been replaced with an appropriate reference: Gap Analysis in Phases B, C, and D now references Part III, Chapter 27: Gap Analysis (Chapters 8,10,11,12). Requirements Management in several phases now references Part II, Section : Requirements Development in the Requirements Management phase (Chapters 8,10,11,12). The Phase E and F descriptions have been reworked to match the level of detail in other phases (Chapters 13,14). The uses of terminology for Transition Architecture/Roadmap/Implementation Strategy have been clarified and made consistent (Chapters 13,14).

Copyright © The Open Group 2011 TOGAF 9.1 Changes in Detail The concepts of levels/iterations/partitions have been clarified and made consistent. This includes a reorganization of material in Part III, Chapter 19: Applying Iteration to the ADM, Chapter 20: Applying the ADM across the Architecture Landscape, and Part V, Chapter 40: Architecture Partitioning (Chapters 5,19,20,40). Additional introductory text on architectural styles has been added in Part III, Chapter 18: Introduction (Chapter 18). Minor changes have been made to the Security Architecture chapter (Part III, Chapter 21: Security Architecture and the ADM) for consistency with the ADM (Chapter 21). The SOA chapter (Part III, Chapter 22: Using TOGAF to Define & Govern SOAs) has been updated to describe the latest SOA Work Group output (Chapter 22).

Copyright © The Open Group 2011 TOGAF 9.1 Changes in Detail The description of Architecture Principles now divides them into two types only – Enterprise and Architecture – whereas before they called out IT Principles separately. IT Principles are now seen as just part of Enterprise Principles (Chapter 23). The Stakeholder Map included in the Stakeholder Management chapter (Part III, Chapter 24: Stakeholder Management) is now explicitly referred to as an example, the table has been highlighted to refer to Stakeholder Concerns, and the list of artifacts for each stakeholder updated (Chapter 24). The Business Scenarios chapter (Part III, Chapter 26: Business Scenarios and Business Goals) has been renamed to Business Scenarios and Business Goals to better reflect the contents of the chapter (Chapter 26). Corrections have been made to metamodel diagrams (Chapter 34). Corrections have been applied to aspects of the metamodel (Chapter 34). The terms “artifact” versus “viewpoint” have been clarified and made consistent. This includes a restructuring of Part IV, Chapter 35: Architectural Artifacts (Chapter 35).

Copyright © The Open Group 2011 TOGAF 9.1 Changes in Detail Some of the artifacts have been renamed to better reflect their usage (Chapter 35): System/Data matrix becomes Application/Data matrix Class diagram has been replaced with Conceptual Data diagram and Logical Data diagram System/Organization matrix becomes Application/Organization matrix Role/System matrix becomes Role/Application matrix System/Function matrix becomes Application/Function matrix Process/System Realization diagram becomes Process/Application Realization diagram System Use-Case diagram becomes Application Use-Case diagram System/Technology matrix becomes Application/Technology matrix

Copyright © The Open Group 2011 TOGAF 9.1 Changes in Detail The Building Blocks example has been removed (Chapter 37). The relationship of the Enterprise Repository to the Architecture Repository is clarified in Part V, Chapter 41: Architecture Repository (Chapter 41). The Evaluation Criteria and Guidelines have been removed from Part V, Chapter 42: Tools for Architecture Development (Chapter 42). The chapter on Architecture Maturity Models (Part VII, Chapter 51: Architecture Maturity Models) has been editorially revised for consistency and clarity (Chapter 51).

Copyright © The Open Group 2011 Further Reading TOGAF 9.1 Web Page White paper: An Introduction to TOGAF TOGAF 9 Technical Corrigendum 1 TOGAF Information Web site

Copyright © The Open Group 2011 Further Reading