How To Build Cost

Effective SOA?
‘Made in India’ Really
Works!

B. G. Prasanna Krishna
Torry Harris Business
Contents:
• The Evolution of Off-shoring
• Traditional IT Services Off-shoring vis-
a-vis SOA Off-shoring
• What / How much to Off-shore?
• Implementation Framework & Model
• Challenges, hurdles and risks
• Selecting a Partner
• Case Study of a SOA implementation
2
 Evolution of Off-shoring
• Big boom in IT related services in – Early ‘90s
• Limited availability of skilled resources
• Discovered it was feasible
• The ‘cost’ aspect!!
• Aided by drastic improvement in data communication and
information exchange technology.
• Y2K was a turning point – Late ‘90s
• Huge amount of work
• Time and business critical
• Grave danger that existing system functionality could be
affected
• Successfully navigated into the 21st Century – minimal hiccups
• Quality concerns on off-shore services adequately addressed.

3
 Evolution of Off-shoring
• Post-Y2K, cost and quality was no longer the only
differentiator – 2001 - 2005
• VALUE proposition over COST proposition
• Off-shore Service Providers (OSPs) focus on Quality
• Process maturity of OSPs – Certification and accreditations
beyond vendor expectations
• Post 2005 – The passion for Excellence
• Meeting or exceeding customer expectations
• Meeting customers’ stated and unstated objectives
• Partnership participation vis-à-vis being Vendors

4
Evolution of Off-shoring

5
Traditional IT Off-shoring Vs.
SOA Off-shoring
• ‘Sauce’ for the Goose is indeed ‘Sauce’ for the Gander!!
• Fundamentally, the same model applies
• Scope definition, Solution Architecting and HLD better done on-
site.
• Integration Testing and UI definition need a lot interaction
• Agile Methodology more suitable.
• External interface testing of modules to be predetermined and
agreed to with all parties
• On-site coordinator from Partner’s side as a SPOC
• Off-shore DM depending on size of project

6
 Mandatory on-site activities
• Understanding the business scenario
• Existing IT systems
• Functionality
• System documentation available
• Expertise available in-house on the systems
• Redundancy in functionality across various systems
• Unused functionality in current systems
• Scope – identify what is NOT included
• ‘More’ may not always be better!
• Optimisation of the business scenario
• Brain storming involving Client, SI and implementation
Partner
7
 Mandatory on-site activities
• Enterprise Architecture
• Needs discussion with Client
• Standards, design, task allocation
• Process granularity
• Time line, schedule and overall plan
• Define re-use strategy and implementation
• Integration with existing systems
• Integration with third party products
• UAT and Pre-production Testing

8
 Activities which can be
considered for off-shoring
• Determined by
• Complexity of the project
• Process maturity of all parties involved
• Use of state-of-the-art development methodology
• High Level Design
• Part of the team can work off-shore
• On-site team can coordinate with the Client
• System / Integration Test plan preparation
• About 75% of the work can be off-shore
• Planning to start along with Designing

9
 Activities for Off-shore
• Part of HLD (optionally) and Post HLD
• Pre-UAT
• Post-release support
• Emphasis at off-shore
• IT skills and prior implementation experience
• Understanding customer’s business needs
• Agile methodology
• Frequent interaction and review with end-users
• During all phases of implementation
• Deliverables schedule to be agreed to

10
 Activities for Off-shore
• ‘Test–as–you–build’ Development Methodology
• Products available to facilitate this
• Better to work on the ‘same’ infrastructure rather
than ‘similar’ infrastructure
• Will avoid integration related issues later
• All parties involved have to plan and invest the time
• Design-build-test sequence can be iterative
• Feedback from users easily incorporated

11
 Your Partner Partner
Offices Onsite Offshore
Enterprise Wide
Document Audit &
Business Document IT
Processes Assets
Governance (Design
Define Time Stds/Policies & Low Level
Roadmap Runtime Policies) Design

Business Process
Technical
Implementation (logic,
Architecture
integration, modernization,
Business Document
mediation, orchestration)
Requirement Service
Specification Identification & Unit, Functional &
Documentation Performance Testing
High Level Design

Integration & Performance

Build Regression
Testing
User Acceptance Test Suite
Testing L2/L3 Support

Production
 Challenges, Hurdles & Risks
• Anything more than ‘Optimal’ may not work
• Scope definition and schedule definition
• Exposing legacy applications with ill-separated business
logic thru Web Services
• Understating the ‘Processing and Communication’
overheads
• Defining and implementing standards
• Definition of services
• Messaging
• Within and outside the organisation

13
 Challenges, Hurdles & Risks
• Security Requirements – applications more exposed to
out-side world
• Qualified human resources
• Solution and Architecting
• Implementation

• Internal adaptability factors

• Comfort feeling with existing systems
• Long term needs may not be perceived by all

14
 Selecting a Partner
• Experienced in SOA implementation with well
established delivery engine
• Technology Neutral
• Scalable, responsive and adaptable
• Expertise in Middleware
• SOA Testing
• Turn-key Solutions
• Cost Effectiveness

15
Case Study – to be incorporated

16
 Questions?

Get more details @ soa.thbs.com

17