SOA - Integration Industry Pulse

Beth Gold-Bernstein

Open Group Releases TOGAF 9 Today

user-pic
Vote 0 Votes

Today the Open Group announced the release of TOGAF 9. Perhaps not earth shattering news to many, based on the whole scuttlebutt about SOA being dead, which to me says that the discipline of architecture is dead. However, as the design points of this release were making TOGAF easier to use and easier to plug into external frameworks including ITIL, those who are struggling with architecture within the enterprise may wish to take a second look at TOGAF 9.

The Open Group has been around for 25 years, and claims over 7,800 participants from 350 member enterprises. They are completely vendor neutral, and work with other frameworks and standards. Some other interesting statistics include over 90,000 downloads of TOGAF, 8,491 certified practitioners, and 529% growth since October 2006. When it comes to enterprise architecture, I don't think there is a competing alternative that comes close.

TOGAF 9 encompasses the entire enterprise architecture life cycle, which is important as architecture is a never ending journey, always changing and evolving. The figure below depicts the TOGAF Architecture Development Method (ADM) which covers the entire architecture life cycle.

Open Group ADM.jpg

The Open Group members were looking for an evolutionary step for version 9, not a revolution. Design goals for the release were greater usability, closer alignment with the business, and more guidance on SOA. To deliver on this, the Open group has expanded detail and clarification of existing proof points, focused on holistic enterprise change, created clear links between business and IT objects, including a metamodel for an enterprise architecture repository, and has provided more consistency of output deliverables. TOGAF 9 was developed around a web based view, and has a more modular structure than the previous version. Below is a depiction of the components.

Open Group TOGAF 9 Components.jpg

There is also more guidance on how to use TOGAF in a consistent way within the enterprise. While there is no single architecture that fits all needs in all enterprises, there is a body of knowledge and capabilities to help organizations more successful in their enterprise architecture endeavors. This is what TOGAF 9 attempts to do - to show organizations how to apply the architecture development method (ADM) . And version 9 includes hooks to ITIL, Zachman, and other frameworks. This means that organizations looking to get a leg up on their SOA implementation by purchasing, for example, one of IBM's industry solutions, will then have a way to incorporate the framework into TOGAF and bring it under a consistent life cycle management methodology. This will help organizations develop architectural competency and consistency - both essential to long term architectural agility and ROI.

For this release the Open Group has also created a metamodel for the TOGAF framework. In another post I plan to compare this framework to the OMG SOA Consortium framework. In an effort to increase usability, the Open Group has also published a metamodel on how the different components of TOGAF 9 relate to each other.

TOGAF Capability Framework.jpg

I was looking forward to discussing this release with Alan Brown, President of The Open Group and Judith Jones, President and founder of Architecting the Enterprise which does TOGAF certification, particularly in the light of the recent pronouncement by some analysts that SOA is dead. SOA, is after all, a specific style of distributed architecture. If SOA is dead, then it is in large part because organizations are not particularly adept at the discipline of enterprise architecture. Bringing TOGAF into an organization and going through TOGAF certification represents a big commitment to architecture.
Were organizations making that commitment during the down turn?
According to Judith Jones, the answer is yes. When I asked her what reason the organizations who have recently become members cited for joining. She answered that these organizations view the downturn as both an opportunity and a necessity to take a very strategic look at their business operations and architecture, determine what is holding them back, and deciding not to keep making the same mistakes. According to Jones, these organizations are viewing architecture discipline as the basis for moving forward with agility. They regard competency in enterprise architecture a critical need. Interestingly, she noted that new members include financial services and retail organizations - both which have been hit hard by the recession.

2 TrackBacks

It’s just a standard day in San Diego. That is to say, the friendly people over here are kind of used to blue skies and summer temperatures at the beginning of February. On the other hand, these days are quite... Read More

This week, there were two standard announcements, one involving enterprise architecture and the other Web services. First, The Open Group Architecture Framework (TOGAF) updated . TOGAF is a vendor- and technology-neutral standard for enterprise... Read More

5 Comments

Two points in Beth's post are outstanding:
1) If SOA is dead, then it is in large part because organizations are not particularly adept at the discipline of enterprise architecture.
2)She [Judith Jones] answered that these organizations view the downturn as both an opportunity and a necessity to take a very strategic look at their business operations and architecture, determine what is holding them back

I think, these are the lessons everybody has to carry out for this time.

BTW, in my analysis of posts related to SOA 'death', I've found that it was not about a death of SOA but about the death of IT initiatives that treated SOA as a technology but promised business benefits as they would been using methodology.

Thanks for your comment Michael. I totally agree with you that the issue behind the demise of SOA was that organizations lacked skills and discipline and were expecting the answer and agility to come in the ESB box. Never mind the fact that every analyst and consultant warned that SOA is not a single technology. That message was somehow lost.

IMHO I do not think that pronouncing SOA DOA is at all helpful. I think what would be helpful is to make it easier to consume for organizations. But bottom line, when it comes to distributed computing, architecture is a core skill that is vital to the organization because YOU, not the vendors, are creating the architecture.

Would be nice if you could link the images in the article to larger, more readable images

Excellent introduction.

TOGAF 9 is a step forward for enterprise architecture. TOGAF 9 presents the first public enterprise architecture framework to cover the full spectrum of content, process and needed capabilities. Now, companies can say "Never mind the architecture frameworks" and just use TOGAF.

Carsten Molgaard, The Rasmussen Report

Good artcle, Open Group has made great efforts to move TOGAF 9.0 to be more EA business oriented than it used to be IT-Oriented. The alignement of IT and Business in immature Enterprises requires closer look to what TOGAF 9 has brought into the table. The Delimma of SOA and Applying SOA will not be resolved without business community buying it as a business driven archiecture that requires mature Corporate and IT governance. As of now, SOA is seen to be an IT "thing".

Industry trends and vendor spotlights from Beth Gold-Bernstein.

Beth Gold-Bernstein

Beth Gold-Bernstein is a recognized expert in integration technologies and SOA with over 20 years experience View more

Subscribe

 Subscribe in a reader

Recently Commented On

Monthly Archives

Blogs

ADVERTISEMENT