Oracle IT Architecture SOA

Implementation

Interface

Contract

Service Agreement

Business Process

Composite Service

The scope of the current state assessment is limited to one business unit at a time. This keeps the length of the assessment to approximately two weeks.

The current state assessment is performed by evaluating the maturity and adoption of capabilities in the SOA Maturity Model. This narrow focus allows the assessment to be completed in approximately two weeks.

The scope of the current state assessment is restricted to the projects that the Project Selection Framework identified as the best SOA projects. This limited set of projects can be assessed in approximately two weeks.

The current state assessment is time boxed to two weeks. At the end of the two weeks, thecurrent state assessment is deemed complete and the next step in the roadmap creation process is begun.

The current state assessment is done by reviewing documents provided by the customer. Two weeks is sufficient to review the documents and determine the current state.

Policy enforcement - enforce policies through gateways (self-contained modules) and agents (interceptors)

Dependency analysis - the ability to navigate taxonomies and asset relationships to facilitate Impact analysis based on Inter-dependency

Service discovery - facilitates Service discovery by providing a means to locate potential Serviceseither through taxonomy navigation, or direct search

Performance management - measures and monitors the availability and performance of Services for historical trending, troubleshooting, and root cause analysis purposes

A Service is a means of packaging reusable software building blocks to provide functionality to users, applications, or other Services.

A Service is comprised of Implementation code and a WSDL by which it is described.

A Service is only used for wrapping legacy systems to enable easier integration,

A Service is an independent, self-sufficient, functional unit of work.

A Service is discoverable, manageable, and measurable.

A Service is a Java-based component.

Requirements need to be assessed against the enterprise business model and not just the immediate project's scope.

Need to encompass requirements from operational staff to manage deployed Services as well as the business

Requirements need to expressed in terms of a Service contract, implementation, and interface.

All requirements are captured regardless of whether Services will be built from them.

There is one standardized SOA governance model that is appropriate for all enterprises.

There is no single model of good SOA governance because each enterprise has differences andnuances.

A SOA governance model focuses only on the lifecycle of a Service.

Compliance with a defined SOA governance model Is automatic after It has been deployed.

A SOA governance model enables the definition of policies andprocesses to guide management into
making effective SOA decisions.

A SOA governance model enables authorized groups to encourage/enforce alignment to SOA architecture and cultural orientation.

All of the architecture principles must be followed. If any of the principles are violated, the architecture is not service oriented.

The organization should review and evaluate the architecture principles, and then derive their own architecture principles that match their specific environment and goals.

An organization can add additional architecture principles, but the stated architecture principles must be followed.

An organization can decide to not enforce one or more of the architecture principles, but additional architecture principles will not be needed.

The architecture principles define what products will be used in the architecture, so the architecture principles must be adjusted to reflect the chosen products.

A Service Bus should be used to provide both Service discovery and Service version management capabilities.

A metadata repository should be used for Service version management and Service registry should be used for Service discovery.

A Service registry should be used to provide both Service discovery and Service version management capabilities.

A metadata repository should be used to provide both Service discovery and Service version management capabilities.

A Service portfolio provides a single location for storing Service meta-data, software relationships, and metrics in order to apply governance policies and systemetise reuse.

A Service portfolio provides a singlesoftware library from which artifacts can be deployed and versioned.

A Service portfolio provides a runtime view of the Services so that the right Service may be looked up and consumed in an environment.

A Service portfolio contains all the software artifacts that will be developed by a project so that project managers can track their lifecycle through the project.

SOA infrastructure must be designed to enable point-to-point integration.

SOA Infrastructure must support all Services with standards-based interfaces, regardless of their choice of implementation technology.

SOA Infrastructure must be based on open standards. This supports a best-of-breed approach and prevents vendor lock in.

Multiple versions of a SOA Service must not be run concurrently.