The Enterprise Architecture site has been launched on MSDN. Enterprise Architecture has become a common practice for large IT organizations. For the first time there is a methodology to encompass all of the various IT aspects and processes into a single practice. However, realizing the full potential of Enterprise Architecture (EA) can be challenging. There are many aspects to EA, including architecture planning, governance, taxonomies and ontologies, all of which impact its success. Without the right guidance, tools, frameworks and methodologies EA can quickly become unwieldy.
When enterprise architectures work well, they are a tremendous asset in finding effective ways to better use technology. When they don't work well, they can be a huge counterproductive drain on precious organizational resources. All too often, it is the latter case that is realized.
Twenty years ago, a field was born that came to be known as enterprise architecture. Initially, it addressed two problems: system complexity and poor business alignment. Today these problems have reached a crisis point. The cost and complexity of IT systems have increased while the chances of deriving real value from those systems have decreased.
Over the past few years, and as software and systems engineering has matured, it has become accepted that there is a clear need for an 'architectural view' of systems. This article describes Cap Gemini Ernst & Young's Integrated Architecture Framework, and describes a model for enterprise architecture and its importance in helping software architects understand the business as a whole.
Many enterprise architectural methodologies have come and gone in the last 20 years. The Zachman Framework, TOGAF, the Federal Enterprise Architecture