Four Steps to SOA

Computerworld - The latest architectural revolution to strike IT is service-oriented architecture. IT managers are not only excited about the promise of SOA, but also fearful of this new paradigm and the impact it will have on the organization. Here are four simple steps you can follow to ensure a smooth transition to SOA.

Ken Karacsony, senior data analyst at Toyota Motor Sales Inc. Image Credit: Seth Joel

If you are implementing service-oriented architecture, the most important point to remember is that your IT organization must have a clear understanding and definition of it.

Ask five IT professionals exactly what SOA means, and you are likely to hear five different answers. That's because such architectures are rapidly evolving.

But that's OK. It's not critical that the IT industry reach a consensus on a definition. But it is vital that everyone in your IT organization agrees upon exactly what SOA means to the company.

I recommend that you research respected IT literature on SOA and develop a definition that makes sense for your organization. You may also wish to consult experts in the field who can work with you to define an architecture based on your company's unique requirements. SOA is flexible enough to accommodate a variety of integration challenges.

The key take-away is that your company must own the definition that it develops. Everyone in the IT organization must understand the definition, fully support the new paradigm and align resources to make it happen.

Train Staff

For many companies, SOA is a radical departure from traditional architectures that are based on tightly coupled application interfaces. Consequently, there may be a steep learning curve to understanding SOA. Training and education are absolutely essential to flatten the curve.

I recommend a top-down training approach. First, educate senior management on the fundamental tenets of SOA and the benefits of deploying it. This is critical. If the CIO, for example, is unable to grasp the basic methodologies and goals of the architecture, then he will not be able to support it.

Once you have trained upper management, proceed to lower-level managers. They must not only be educated in the overall goals and philosophy of SOA, but also trained in its practical details and how it will be implemented.

Finally, train your staff on the specifics of building and deploying SOA. This granular level of training needs to address the specific technologies to support the company's move to SOA. This will require the greatest amount of training.