Large amounts of data can be exchanged with document-style interfaces.

This will provide the greatest opportunity for re-use from the widest possible number of consumers.

Document-style interfaces provide for tight coupling between consumers and service providers.

Document-style interfaces tend to be quite fine-grained so that they can be re-composed in innovative ways.

Document-style interfaces provide for tight coupling between consumers and service providers.

The head of the IT delivery organization needs to be engaged because It is their organization that will be affected the most by this change. The business and operations will continue as before.

The CIO needs to be leading this initiative as all aspects of IT need to be engaged from delivery through to operations, but business involvement can be minimised,

The SOA can be built up on a project-by-project basis so each project needs to be engaged when needed.

The CEO must drive this initiative because it will have far-reaching impacts for all parts of the organization.

The CIO and leaders of those business units falling under the scope of the SOA initiative need to drive the changes required for SOA adoption.

A single registry is employed to ensure Services are consistently published.

A single service engineering team is employed to build all Services which ensure implementation consistency.

A single technology (for example, Java) is employed to build all Services which ensure standards consistency.

Design-time governance quality points are employed to ensure that Services following agreed enterprise standards and guidelines.

A single repository is employed to ensure Services are consistently discoverable.

The SOA Service should implement an asynchronous "get account" method because that matches the legacy system access provided.

The SOA Service should implement a synchronous "get account" method because that Is what the service consumers have requested. A new synchronous Interface to the legacy system should be created.

The SOA Service should implement two synchronous methods. The first method is a "send account request" and the second method is a "get account response." This meets the synchronous interface request of the service consumers while matching the existing interface to the legacy system.

The SOA Service should implement a synchronous "get account" method because that is what the service consumers have requested. The SOA Service should use the synchronous-to-asynchronous bridging pattern and use the existing interface to the legacy system.

The SOA Service should implement a synchronous "get account" method because that is what the service consumers have requested. The SOA Service should use the store-and-forward pattern and use the existing interface to the legacy system.

Technical orchestrations are business processes that have been implemented using BPEL

Business processes should be isolated from technical details by encapsulating the technical details in technical orchestrations.

Activities within a business process that are likely to change due to business changes should be encapsulated in a technical orchestration.

Business processes should not use any technical orchestrations.

Business processes only call Business Services whereas technical orchestrations only call Connectivity Services.

To identify functional overlap and linkages in the SOA project selection process

To summarize what an enterprise does and the relationship between those functions

Identify the high-level business processes in the organization

Define the organizational structure for the business

Provide a structure for a federated enterprise service bus deployment