In a recent article at Inside Architecture, Nick Malik took time to detail the different enterprise architecture frameworks. He then goes on to pose the question, what would the ideal framework be? What would you take from each of the individual methods below to make your enterprise architecture fit your needs?
- TOGAF - Basic strength: solution architecture. Various models and how to create them. Basic weaknesses: Planning methods and governance framework. Weak on Information Architecture
- FEAF - Basic strength: complete implementation tied to measurement framework. Basic weaknesses: very specific to government, lack of independent process taxonomy keeps processes "in the silo."
- eTOM - Basic strength: excellent process taxonomy with rich details. Strong information architecture. Great for governing external vendors. Basic weaknesses: fairly specific to telecom industry, gaps in governance and enterprise architecture models.
- ITIL - Basic strength: excellent process framework for operations and (now) governance. Basic weaknesses: no architectural methodology to speak of. Sizeable gaps in information or application architecture.
-
- Zachman - Basic strength: comprehensive taxonomy of architectural artifacts (to let you know when you are done). Basic weaknesses: Lack of published and vetted methods to avoid "boil-the-ocean" exercises and focus on one particular benefit. Very shallow: No detailed process, capability, or solution frameworks for "level 2" detail. Highly proprietary.
We're getting ready to launch a new blog that looks at the broader issues of Enterprise Architecture, update your RSS feed now as we get it ready for our official launch: http://evolveea.blogspot.com/
No comments:
Post a Comment