Ok, I confess, I’ve had the near 800-page TOGAF 9 document for a couple weeks and find myself with several hundred pages still to read. So, this post is not further commentary from me on TOGAF 9, rather a collection of TOGAF 9 (and related) links and resources you might want to check out.
Before I go further, I should set some context by reiterating my comment to Mark Griffin on enterprise architects, architecture frameworks and ivory towers:
“I share your concern that EA can be (sometimes deserving) viewed as an ivory tower. I’m encouraged by the modularity of TOGAF 9 and the related messaging from the creators that EAs should pick and choose the TOGAF steps, artifacts & practices that make sense for their business situation. Used this way, TOGAF (and any other framework) becomes a tool rather than a mission in itself.
For the reasons you mention, I’ve never been an ardent framework follower. Too often that leads to excessive documentation and little implementation. I’m more of a “sampler”, on the look out for artifacts, guidance, practitioner ideas I can apply to my work in the context of delivery.
As I dig into TOGAF, I’ll be testing for value within my “sampling” point of view and sharing those findings for real-world folks like you.”
TOGAF 9 Overviews & Commentary
Nick Malik: A first look at TOGAF 9.0
The ever thoughtful Nick Malik shares his first impressions of TOGAF 9:
“I’m not a certified TOGAF practitioner. That caveat aside, I am someone who has studied multiple frameworks, and created an architectural framework, so I can draw on a good bit of experience when reviewing one. I spent some time reviewing the prior version of TOGAF, and my first impression of the new version is this: Substantial and Deep Improvements.
The new version has a comprehensive model for the content, insuring that the stakeholders for architecture have separate sections of the framework dedicated to each of their varied concerns. This makes navigation and adoption considerably easier. In addition, substantially new content, along with new models and a richer set of descriptions, have been added. The new framework is more readable and more usable than it’s predecessor.
The focus of TOGAF 9.0 has been sharpened, drawing the distinctions between different concepts and activities into the light. This was needed for strategic architecture to be successful in to TOGAF model. The terminology is more consistently described and used, and the attention to detail is refreshing.
The TOGAF is, and probably always will be, a work in progress. It is a community effort, and the community that worked on this version have expended considerable effort. That effort shows. I really like where this framework is going.
Here is my call to action: for the first time, I’m willing to say this: The TOGAF is enterprise ready. If your organization does not have a framework, or if you are using Zachman with some home-grown methods, I recommend that you serious consider TOGAF 9 for adoption.”
Nick’s post continues with a discussion of specific things he appreciates and opportunities for improvement. If you are interested in TOGAF 9, this is a must read post.
Mike Walker: TOGAF 9 Release & Impressions
Mike does a nice job of describing the TOGAF 9 enhancements, followed by commentary on what architects will care about and what needs improvement. Mike’s bottom line:
“Whether you are using TOGAF in your organization or not TOGAF 9 is definitely a framework you want to evaluate. I didn’t find anything that was negative about TOGAF 9. Even though there are some gaps and some areas that could be more developed the bits that are refined were really good. Keep in mind that the focus for TOGAF is still mostly at the process level and dealing at a high level of abstraction should be expected.”
Dana Gardner: TOGAF 9 Podcasts
Dana has a lot of TOGAF 9 coverage. In addition to some overview posts, he published podcasts with Open Group’s Allen Brown and of an architect thought leader panel session he moderated at the EA conference. [I also live-blogged that session.]
Michael Poulin: TOGAF 9 is short on SOA
Of course, not all is sunshine and puppies. On ebizQ, Michael Poulin offers an in-depth 3-post series on why TOGAF’s new ADM guidelines for SOA fall short.
“For the whole last year we waited for new TOGAF version with high expectations regarding proper positioning SOA in the Enterprise Architecture. Being a TOGAF 8 Certified Practitioner and a ‘SOA guy’, I was, probably, among the most impatient ones. I mean positioning of Service Orientation (SO) rather than SOA, though. The TOGAF 9.0 release has finally brought a lot of very right words about business nature of SO but still lacked the right order of those words in a few crucial places.
While not mentioning that TOGAF 9.0 does not refer any other SOA standards (from OASIS or OMG), I am mostly dissatisfied with three areas of ‘Using TOGAF to Define & Govern SOAs’ chapter:
• representation of the essence of service
• Service contract
• SO role in ADM”
What I’ve yet to run across is any commentary on the new ADM Security Guidance. Could this be another sign that enterprise architects prefer to remain “blissfully ignorant” on security?
I’m sure there are many other insightful TOGAF 9 posts that I missed. Please pass along those links in the comments.
TOGAF 9 Resources
The Open Group Bookstore: TOGAF 9 Pocket Guide
I found this pocket guide to be helpful. It gives you an introduction to TOGAF 9 and helps you determine applicable areas to explore further. A pdf of the pocket guide is free to Open Gro
up members. For the rest of us, a hardcopy of the pocket guide is available for $26. I received my pocket guide for free at the recent conference.
“This Pocket Guide is based on TOGAF Version 9 Enterprise Edition. It gives a concise introduction to TOGAF 9. What’s more, it’s authoritative, with material derived from The Open Group’s TOGAF 9 documentation and contributions from members of The Open Group Architecture Forum. The audience for this Pocket Guide is enterprise architects, business architects, IT architects, data architects, systems architects, solutions architects, and senior managers seeking a ﬁrst introduction to TOGAF.”
TOGAF(tm) Version 9 – Non-Member Download
“You may download TOGAF Version 9 under a free, personal, 90-day Evaluation License; and you may then go on to use it internally under a free, perpetual, Corporate License or a free, perpetual, Academic License, if you wish. Alternatively, you may take out an annual Commercial License.”
ArchiMate & The Open Group
In related enterprise architecture activity, according to the January 2008 ArchiMate newsletter (pdf) ArchiMate and The Open Group are Joining Hands:
“The board of the ArchiMate Foundation and the board of The Open Group have expressed their intentions to adopt ArchiMate as an independent standard for enterprise architecture modelling and analysis under the aegis of The Open Group.
When the ArchiMate Foundation was initiated, international adoption of ArchiMate was expressed as one of the most important goals, the reason being that standards such as ArchiMate need international adoption to have impact and remain viable.
The above steps with The Open Group will pave the path towards international adoption. These steps have come sooner than expected. The Open Group themselves were searching for a good standard for enterprise architecture modelling and analysis. ArchiMate will fill in this need.
The Open Group also governs TOGAF (The Open Group Architecture Framework). TOGAF mainly contains methods and best practices to create an enterprise architecture. ArchiMate complements this, as it is a language for enterprise architecture models. Thus, TOGAF and ArchiMate can work hand in hand or be used independent from each other. Both TOGAF and ArchiMate will remain independent standards so user organisations have a choice what to adopt.
At this very moment, The ArchiMate Foundation, The Telematica Instituut and The Open Group are working out the best way to hand over the rights and obligations. Current ArchiMate license holders will be informed via the ArchiMate user council.”
If you are like me, you might be thinking “I’ve never heard of ArchiMate”. And “isn’t modeling the purview of the OMG?” From the ArchiMate site:
“ArchiMate is a modelling technique (“language”) for describing enterprise architectures. It presents a clear set of concepts within and relationships between architecture domains, and offers a simple and uniform structure for describing the contents of these domains.”
To learn about ArchiMate, check out the language primer (pdf) and this interactive resource tree. If you currently use ArchiMate, drop a comment or email on usage scenarios and your impressions. I discovered ArchiMate at the conference and plan to investigate further.
[Disclosure: The Open Group is not a client of my company, Elemental Links. However, the Open Group did invite me to their recent EA Conference & Cloud Computing Summit and provided my on-site accommodations. The OMG, via their management of the SOA Consortium, is a client.]
I suggest to debate a bit further on ArchiMate. I use it now for a while for my EA activities. What you have to keep in mind is that the Telematica Institute had a good reason to develop ArchiMate. Until now no other tool was available for architects to create viewpoints and views with a business/ICT-alignment state in mind. ArchiMate has it all. It’s not something you give to OMG because it’s for a totally different purpose group. Only similarities could be the semantic-rules for all objects like: service, process, component etcetera.
ArchiMate is based on behavior and structural objects and the relations between them.
However for a good practice of ArchiMate I’d always suggest to use an empowered tool like BizzDesign Architect.
Wilbert de Wolf