ArchiMate Support in System Architect
We at Corso are seeing many EA practitioners gravitating to the ArchiMate framework as the tool for delivering Enterprise Architecture. Why is this? Unlike many frameworks to date that do not specify how model views are represented, ArchiMate provides a clear notation and language for the communication of EA.
The ArchiMate framework is currently at version 1, owned by the Open Group (who also own TOGAF), and has some limitations, which we see are already being addressed in version 2. These limitations include a lack of mappings to technical reference architectures, the lack of BPMN views, and the lack of provision of other industry specific frameworks such as eTom. Corso have addressed many of these issues in its System Architect release of ArchiMate.
ArchiMate is rapidly gaining momentum, especially in Europe. We expect to see a clear convergence between ArchiMate and TOGAF over the next 2 years, now that they are effectively from the same stable. Much like BPMN becoming the defacto standard for representation of business processes (based on the fact that it provided a common notation), we expect ArchiMate to have the same impact on EA.
Join us for a Webinar on Thursday, November 10, 2011 at 3:30pm to 4:30pm GMT — An overview of the new ArchiMate extension for IBM Rational System Architect. Space is limited — reserve your seat now by clicking here.
If you cannot attend the webinar but are interested in our ArchiMate data sheet, please register at corso.co.uk, or if you require a coversation personally, call +44 (0) 1926 333222.
4
Comments
yesith
I don’t want start a flame war, just want to balance some of the above. I have been told by old CG hands that IAF was influenced by Zachman Framework. And it looks like that anyway. TOGAF 8 already had a content framework. In fact it had two. The Enterprise Continuum (a two dimensional classification, which shares one dimension with the two dimensional Zachman Framework). And the Taxomomy of Views structured according to Archiecture Domains. I’m not convinced advising people how to use TOGAF for tacical solution architeture is a priority, since many already do that. I think the focus should be on improving the overall integrity, not on adding more topics.
TOGAF is the de facto industry standard. Overall, TOGAF 9 is better 8. And I will use it happily. But some of the new contributions fall short of what one hoped. A couple of the new chapters would be better left as white papers. The new content framework is a move in the right direction but not yet fully integrated with the legacy. The content meta model is a move in the right direction, but not yet wholly aligned with the text.
Tomoko
Thanks for your feedback. I would not dare to suggest that Capgemini’s IAF is so much influenced by Zachman, I think it has a few quite unique features of its own. And both IAF and Zachman provide very useful perspectives that can easily be embedded in a TOGAF-driven enterprise architecture engagement. And you are right, many other things to achieve in architecture. But let’s be realistic: already sharing a common, non-proprietary methodological language between architects is a huge, huge step forward towards further maturity of the profession. Keep in touch!
Ian
I would not call that an end’ and obviously some of the best capabilitpes of IAF are now indeed a part of TOGAF 9 (e.g. the Content Framework). I would argue that the IAF way of architecting’ is actually a design school’ which fits very well into the TOGAF framework. And we should take care of our assets and we probably should use IAF’ as the containing framework for this unique style of architecting. But yes! Always as part of an open, global methodology framework. No doubt this is TOGAF. And thanks for noticing the wrong Twitter search link. Fixed now.
Cecilia
I remember TOGAF and IAF as a match made in heaven back in 2005 when Capgemini joined The Open Group.Now, TOGAF 9 presents the first public enterprise architecture framework to cover the full spectrum of content, process and needed capabilities, enabling the company to say Never mind the architecture frameworks and just use TOGAF. A step forward for enterprise architecture!
Leave a Reply