Recently launched at the Open Group meeting in London last week a venture between The Open Group and the TM Forum produced a 110 page report on how their two frameworks (TOGAF and Frameworx) align and where they extend each other. This report is a very deep and compressive with a quick reference guide.
I really like seeing this work. This is exactly what the enterprise architecture industry needs, the reduction of confusion and complexity between frameworks that have specific drivers vs. general purpose frameworks such as TOGAF.
Further evidence of this, I have been in western Europe for two weeks talking to some top Enterprise Architects in very large enterprises. I still get the questions around what is the difference between TOGAF and <…x…>. Given this over whelming amount of confusion I hope these resources continue to be developed. For example, I would like the TOGAF 8 to ITIL 2 article to be updated to the latest versions.
In the report, it does a really good job of positioning TOGAF as the framework it intends to be, a general purpose framework. With a general purpose framework it is important to understand that it is meant to address a broad and vast amount of needs, to do so it needs to be generic and extensible so customers and services providers can add their specific business driven execution model on top. The report really demonstrates that modularity, extensibility and flexibility of their framework without jeopardizing the integrity of the core.
Below are two models that show these relationships.
Andrew Josey has put together such a great list of synergies that it would be incredibly redundant for me to regenerate these already great points.
Below is the summary of the identified synergies:
Immediate synergies have been identified between the TOGAF Architecture Development Method (ADM) phases Preliminary, A, B, C and the Common Systems Architecture of the Enterprise Continuum. This document addresses the TOGAF ADM phases from Preliminary to Phase C. The synergies between business services (formerly known as NGOSS contracts) and the Common Systems Architecture will be dealt with in a separate document.
TOGAF® provides an Architecture Repository structure that can smoothly accommodate the mapping of TM Forum assets; this feature can be leveraged to identify and derive the added value of the content.
TM Forum assets can be classified as either Industry Architectures or Common Systems Architecture in (TOGAF®) Enterprise Continuum language. TOGAF® provides a widely accepted methodology to leverage these architectures into the development of enterprise architecture.
Professionals that use TM Forum assets will find templates and guidelines in TOGAF® that facilitate the transformation of such TM Forum assets into deliverables for a specific project/program.
TOGAF concepts as defined in the TOGAF® Architecture Content Framework provide clear definitions as to what artifacts from TM Forum assets have to be developed in order to be consistent and comprehensive with an architecture construct.
Resources
Publication - http://www.opengroup.org/bookstore/catalog/w114.htm
Technorati Tags: TOGAF,Open Group,Standards,Enterprise Architecture,EA Frameworks,eTOM,TM Forum
Comentarios