An EA might (should?) encompass the components that provide integration facilities. Thus a separate IA definition isn't necessary unless one wants to elaborate the integration-related components to a degree that it would muddle the EA.
IME, an IA is typically created when an EA does not exist. The company hasn't yet realized the need for an EA and the IA is a step in that direction. IMO, the EA and the IA can be SO (among other things). However, other folks (whose opinions I respect) don't think an IA can be SO. SO is the style (one of multiple styles that an architecture will leverage). EA or IA is the scope. -Rob --- In [email protected], David Chappell <david.chapp...@...> wrote: > > Anyone out there have any nuggets of wisdom on the relationship > between EA and integration architecture? > I know you won't disappoint me :) > Dave
