Point-to-point integrations should be avoided.

Integrations should be point-to-point using Web Services.

Message and data formats should be based on the native application data structures.

Extensive, intrusive modifications to existing applications should be avoided.

Service consumers should be able to migrate to a newer version of a SOA Service gracefully.

There should not be more than one version of a SOA Service in production concurrently.

Are realized by shared Services which are not owned by any single application, consist of their own lifecycle, and are managed independently.

May be implemented by existing applications, applications that are being developed, or proposed applications that have not yet been delivered.

Once handed to a project by the business, can be purely managed by that project.

Are focused on defining the integration points between applications,

Should only be managed by a SOA centre of excellence.

The capabilities in a product are identified and then the product is mapped to the architecture based on those capabilities. A product can map to more than one layer of the architecture.

The capabilities in a product are identified and then the product mapped to the architecture based on those capabilities. The product is mapped to the layer of the architecture where the most capabilities lie.

A product is compared to the Oracle products that are already mapped onto the architecture. The product is mapped onto the architecture as a replacement for the most similar Grade product,

A product is compared to the Oracle products that are already mapped onto the architecture. If the product provides all the capabilities of an Oracle product, the product replaces that Oracle product.

Products are not directly mapped onto the architecture; only the capabilities provided by the products are mapped onto the architecture.