I produced this page after fielding a question for a succinct definition, in three pages or less, describing what Enterprise Architecture is, and how it is valuable.  Unfortunately, I don’t have time at the moment to pull all the various strands of information together as a nifty three page document.  What I can do, at this time, is provide a series of links to prior articles that can help to describe and define Enterprise Architecture from my point of view. 

First off, let me say that Microsoft does not favor, endorse, or promote any particular EA framework.  We have had experience with numerous approaches and frameworks, have developed our own metamodel and framework for internal use that guides our strategic planning.  Our consulting organization, Microsoft Consulting Services has many Enterprise Architects among the ranks.

Selected Links:

Nick Malik (me):
  • Value of EA (link), (link),
  • Functions of EA (link),
  • Double Iron Triangle of EA (link)
  • Job desc for Business Architect (link),
  • EA vs. SA (link),
  • IEEE1471 and EA (link),
  • measuring EA (link),
  • On being relevant (link)
  • Multiple interacting teams (link)
  • Review of TOGAF 9 (link),

 

Gabriel Morgan:
  • EA vs. SA (link),
  • traceability (link),

 

Mike Walker:
  • EATK article (link)

 

And of course, there’s the Wikipedia’s entry (to which I have contributed) http://en.wikipedia.org/wiki/Enterprise_architecture

Here are some useful blog posts from some friends in the blogosphere:

Leo de Souza: EA Maturity Model (link)

Chris Potts: Definition of EA (link), Moving EA out of IT (link)

Adrian Grigoriu: Review of Gartner Emergent EA (link)