SOURCE: Torry Harris Business Solutions

May 07, 2007 03:31 ET

Torry Harris Business Solutions Presents "Six Steps to Transitioning Successfully to SOA"

Service-Oriented Architecture Makes IT a Strategic Partner in Achieving Business Objectives by Decreasing Dependencies, Improving Communication Across Disparate Systems and Enabling Reuse of Existing and Legacy Systems

ISELIN, NJ -- (MARKET WIRE) -- May 7, 2007 -- Torry Harris Business Solutions (THBS), a global niche technology services and solutions provider for mission-critical distributed enterprise computing and middleware, presents six steps to embarking on a service-oriented architecture (SOA) implementation in a cost-effective offshore model.

"Successful enterprise IT managers today understand that SOA is not a luxury, it is a necessary IT methodology that lends to a flexible infrastructure capable of adapting to business needs," said Thiru Sivasubramanian, country manager USA, Torry Harris Business Solutions. "The next step is to select from the many implementation options available, and this process need not keep decision-makers awake at night as long as they begin with a clear roadmap. Our attempt is to help de-mystify the methodology."

Torry Harris Business Solutions' heritage is in middleware and distributed enterprise computing, which has naturally evolved to become the basis of SOA methodology. The company has worked and partnered with a myriad of SOA product vendors, and provides advice on the use of open source software in SOA implementation. By accessing the following elements, decision-makers can determine the right path to SOA implementation.

1. Determine which business processes are most frequently changed

Identify the application or sets of applications that are impacted by the most frequently required changes demanded by the business. This is the first step that gives an idea of the project's scope, though in small segments. A parallel run will be required during the transition that involves both legacy and different versions, each incorporating more services, progressively exposed in each iteration.

2. Document use cases that will be impacted by changes to business applications

The documentation should include a study of client-based executables or interfaces, invoked by each user community. The purpose of this study is to allow a fuller view of the scope and establish a narrower set of important milestones.

3. Review server-based application code to identify and abstract business processes from an application's functionality

The exercise of parsing business processes apart from an application's functionality helps to form a reasonable estimate of the work and timelines involved, further defining the scope of work.

4. Expose potential latency issues of re-use and content-heavy XML and the security issues of opening these assets for access

When business systems operate conditionally, many of the tasks are buried deep within the rules engines. The process of separating process from systems and making each discrete will necessarily expose weaknesses. These considerations will determine the classes and types of products to be used in the enterprise architecture. Once this is done, the first sketch of the target architecture is made visible.

5. Build and expose the separate functionality that is identified to be a part of one or more business processes

At this time, it is important to get started. A registry and/or a repository that describes the service is necessary, so that incoming messages can find them. The SOA could initially be made available within the firewall, tested and then subsequently made available through holes in the firewall that are opened specifically with relevant security measures to allow access to nominated users.

6. Research and select the right offshore SOA partner

The selection of a SOA partner largely depends on whether a SOA product is purchased or if a custom solution is desired. Selecting an entity that is knowledgeable in both open source and proprietary solutions affords cost-sensitive and time-sensitive options. Knowledge, skill and expertise is of little value without client-centric support. The following questions should be asked: Is this merely a vendor or a true business ally with domain-specific expertise? Is there visibility into the process and is the support team accessible around the clock to meet your needs?

About Torry Harris Business Solutions

Torry Harris Business Solutions (THBS) is a global niche IT service provider that creates and maintains mission critical systems for the telecommunications, banking, financial services and insurance (BFSI), government, health care, manufacturing, utilities, automotive and travel industries. Founded in 1998, THBS is headquartered in New Jersey with offshore development centers in Bangalore, India; Shenzhen, China; and sales offices in Europe, Middle East and Asia-Pacific regions. THBS employs approximately 1,000 staff members worldwide. For more information, please visit us at

Contact Information