Model offers measure for SOA success - Part 1

SOA Service Oriented Architecture Articles : Model offers measure for SOA success By Jon Bachman

Service-oriented architecture has emerged as the most significant shift in how applications are designed, developed and implemented in the last 10 years.

A consortium of software vendors and consultants recently introduced the SOA Maturity Model, which is designed to provide IT decision makers with a framework for benchmarking the strategic value of their SOA implementations and planning. The model is divided into five levels.

Read the latest WhitePaper - Wait-Time Analysis Method: New Best Practice for Performance Management

Level 1: Initial services

At the initial stage, an organization creates definitions for services and integrates SOA into methodologies for project development. In a financial-services environment, a Level 1 project may use an application server or an enterprise service bus (ESB) adapter to create Simple Object Access Protocol and HTTP Web service invocations between a management system that places an order and a trading service that accepts the order.

Want to compare network applications products? Visit the IT Buyer's Guides now.

Level 2: Architected services

At this stage, standards are set for the technical governance of an SOA implementation, typically under the leadership of the architecture organization. Standard SOA infrastructure and components, such as an ESB, a services and policies repository, an exception-management service, a transformation service and a single sign-on service, are used to foster greater reuse of services, as well as provide tight management and control of services across an organization.

Level 3: Business services and collaborative services

Level 3 features the introduction of business-oriented services, such as business process management (BPM). With a focus on the partnership between technology and business organizations, Level 3 optimizes the flexibility of business processes, allowing IT to respond quickly to changing business requirements.

For example, a Level 3 project utilizing BPM might use a Universal Description, Discovery and Integration registry to find a funds-transfer service that could significantly reduce settlement times. This service would be connected to the ESB process within hours of recognizing the business need.

Source: http://www.networkworld.com/news/tech/2006/021306-soa.html