Our third installment of our “SOA in Plain English” delves into the basics of project planning and project management of a SOA implementation.
SOA Adoption Planning Overview
Adapting SOA (Service Oriented Architecture) in an organization requires making changes to the information technology infrastructure which in turn lead to changes in the way business is managed both from technological and organizational point of view. Managing the impact of this process requires a structured change control process and a management organization that is firmly committed to a governance plan for adoption.
Successful SOA adoption is founded on firm stakeholder commitment, clearly defined criteria to evaluate output, and an established process to guide change and manageit.
It is also advisable to create matrices that establish SOA’s benefits, its value, business capability increments,as well as ROI and adoption metrics.
SOA adoption planning can also enhance business and engineering innovations by taking advantage of appropriate service reuse opportunities and allowing for quick alignment of new innovations and technology to business processes.
SOA Reference Architecture
Establishing a SOA reference architecture is also import part of adoption planning.
The first step in developing a SOA reference architecture is align business and IT. The next step is to create a version of existing baseline architecture to help understand the business technology footprint involved and to measure the impact and scope of change that will result from the SOA initiative.
Based on this impact assessment the next step is to create a target or SOA reference architecture which consists of IT environments, technology footprint, key systems, references to business and architecture principles, guidelines and key business drivers. This reference architecture provides guidance to overall adoption and implementation projects. In addition to baseline and target SOA reference architectures, you might consider creating an additional transitional architecture to sketch out a roadmap that takes you from your current or baseline architecture to the target SOA reference architecture. Each transitional roadmap willthe document business and IT capability incremental changes as each step towards the SOA reference architecture.
During the change and adoption process, make sure to pay special attention to your defined objectives and scope to avoid deviations. In other words, guard against “scope creep.” As the benefits of new technology become apparent, the temptation to add new objectives to the plan is normal, but resisting such temptations is key to keeping the project on track.
The stakeholders charged with holding the line against “scope creep” should be the governance and program management team which should be created during initial planning process. These teams will ensure that overall strategy, guiding principles are followed by making regular checks and evaluations are made on the committed deliverables as per milestones.
Start Previewing the Power of SOA Today
If you’re interested in streamlining your IT Architecture with SOA, then you can get a preview of the power of SOA by attending our webcast “Oracle SOA/B2B Architecture: Your Key to a Robust eCommerce Platform-ERP Integration ” to be held on Wednesday June 12th at 8:00 am Pacific/11:00 am Eastern. Click here to register now and reserve your spot.
Did Google, Bing, Yahoo! or some other search engine bring you to this page long after June 12th 2013?
Worry not. Simply click here to check out IT Convergence’s SOA Solutions and Oracle Fusion Middleware services .