TOGAF 9 July 14, 2009
Posted by Chris Eaton in architecture, architecture method, artitecture, EA, IT Architecture, methodology, methods, people, Uncategorized.Tags: architecture, enterprise architecture, TOGAF, togaf 9
trackback
the last 2 days i have been attending a TOGAF course run by cap gemini who have made the majority contribution to the latest version of TOGAF
The good
so i learnt that many of my criticisms of TOGAF 8 have been addressed. Specifically it adds:
The Architecture Content Framework which is a library of prior architectures to stimulate reuse and reuse of best practice rather than reinventing the wheel
A meta-model which includes specific artifacts which result from each of the phases i.e. what you should produce and when, this was absent from TOGAF 8
An architecture capability framework which recognised that good architectures result from consistently trained architects with a high level of education and experience. At the end of the day your architectures will only be as good as the people who developed them
TOGAF is now more obviously applicable to solution architecture, when previously i saw it much more in the enterprise/strategic architecture space
The bad
the vapourware of the enterprise continuum remains this is still poorly described and arguably redundant. The continuum was always poor conceived and in-specific now it is super seeded by the Architecture #Content Framework, It is a such a shame the open group cannot shed this kind of legacy and have much stronger editorial process.
The Architecture Development Method still does not split out data and application architecture, this is stil bucketed under Information System Architecture,. Other areas of the open group like the IT Architect Certification recognising that these are separate significant activities. Again it seems the open group is so wedded to the ADM crop circle diagram it cannot, or will not, move forward and improve on prior thinking
The ugly
well nothing was that ugly to be honest, togaf version 9 is is definitely a step forward
I agree that the information architecture should be split from the application architecture in the Togaf Adm.
I also recommending using ArchiMate as your main meta model for the EA content