Who Champions SOA?
A pain point for EAI projects in the past often was operational frustration stemming from a lack of stewardship or accountability. That was attributable to the fact that, with EAI, the business logic was embedded in the systems being integrated. Hard-coding did not lend itself to agility, so SOA brings the promise of mechanisms for combining, reconfiguring and reassembling components with simple adaptations. Those mechanismsmost likely Web Services standardshave to be collected and managed, and their dissemination enforced, by a champion supported by all facets of the organization. Rather than thinking solely about creating new functionality, all functional areas of the organization have an opportunity to think in harmony about the processes, network elements and data that can be shared by each service. That helps us to take advantage of possible overlap or synergies, says Turkcells Bayrakdar. The IT organization might be in charge of formulating requirements for something like a ratin
