SERVICE ORIENTED ARCHITECTURE

Service Oriented Architecture

Service Oriented Architectures are distinguished by the fact that they implement the "Principles of Service Orientation," which include:

Standardized service contracts.
Service loose coupling.
Service abstraction.
Service reusability.
Service autonomy.
Service statelessness.
Service discoverability.
Service composability.

As a best practice, the above principles are leveraged by key design patterns to enable a high-degree of reuse, automation, and integration across an enterprise. The net effects are significantly reduced costs and enhanced agility.

In the above context, our solution will:

Define a relevant Ontology (an Ontology is essentially a Domain Model describing the business concepts and their relationships. Amongst other things, it acts as a discovery pool for new Web Services).

Align the corporate business models to the Ontology in order to automate them.

Perform a Service Oriented Analysis (i.e. map the steps of business processes to operations/functions of new Web Services or operations/functions of existing assets).

Perform Service Oriented Design.

Create a Transition Plan.

Create an Impact Analysis.

Create a Security Model.

Create a SOA Governance Model, Inclusive of a Reference Architecture.

Develop Services.

Test Services.

Apply key design patterns.

Deploy Services.

For additional information, call us at 800-314-9503 (select option 1, then 2), or send us an email.

1) Contrary to popular belief, a SOA can be implemented via both the SOAP and REST protocols.

2) Larger organizations with multiple business areas can have several ontologies, each governing a specific division of business. It is expected that these specialized ontologies all align to support an enterprise-wide ontology.