Gartner’s EA team has been discussing emergent or middle-out EA approaches (we’ve even called them “EA Lite” at times) for some time, but this way of defining EA is new or unfamiliar to many EA practitioners we talk with.  My goal in the two presentations at the two EA Summit conferences is to lend some depth in both theory and practice (case studies) on how this EA approach works.

Basically, EA teams should define interoperability built on information sharing interfaces, rather than just technology (ESB, SOA’s WSDL/SOAP, etc.), that are more generalized than before, and thus more reusable both for defined needs as well as future serendipitous unplanned requirements.  By defining key base data interfaces, and perhaps also more complex process on data interfaces, you build in the ability to enable interaction between systems EA teams have little control over.  While this is a return in a way to integration as a prime EA theme or goal, this time the effort starts with defining enterprise information likely to be shared or common across the enterprise, then to services that enable easy access, and only then to technology needed to support this interaction.

The generalization of interfaces may be defined top down (via traditional EIA work) or bottom up (via examining existing SOA interfaces and other data).  Either way, the best generalized interfaces then must be sold so that they are reused in systems over time — sold, not just mandated.

This approach to EA enables some organizations to make headway in enabling significant business opportunity even in the face of very complex current states.  It also is the foundation of connecting the enterprise to it’s business partners and customers.

We’ve published a great deal on this approach — if you’re a client, you might start with this note: “Architecting the Emergent Enterprise: New Game, New Rules” (G00160427).