SOA Transformation A Methodology to Keep Service Providers Moving Ahead and Industry Case Studies to

1
SOA Transformation - A Methodology to Keep
Service Providers Moving Ahead and Industry Case
Studies to Ensure Best Practices

• Deepak Kataria, Head Architecture Consulting
  Advisory Services, Digital Convergence Solutions

• New Services Environment Summit 2008, Dallas TX

2
Agenda

• Current Environment
• Service Provider 2.0
• Service Provider Top Issues
• SOA Top Issues
• SOA Transformation
• Service Provider OSS/BSS Reference Architecture
• Methodology
• Risks Challenges
• Mitigation Best Practices
• QA

3
Current Environment

• Service Provider 2.0
• Service Provider Top Issues
• SOA Transformation Top Issues

4
Service Provider 2.0

• Services
• Integrated Value Chains for Content/ Service
  Delivery
• Value chains accommodate consumer behavior and
  social communication
• Value chains facilitate Mobile Fixed Web
  integrated services.
• Single Service Lifecycle - integrate SDPs and
  BSS/OSS processes
• Product Billing mgmt for dynamic services and
  Flow Back provisioning.
• Convergence retake thru Unified Communications
  communication gt desktop gt enterprise gt operations

• Technology and Initiatives
• Offers and Product evolution - Traditional Voice
  and New Voice balance struggle
• Technology continues to evolve
• Several initiatives across Aggregated as well
  as Built Owned Service Platforms

5
Service Provider Top Issues

• Increasing demands on IT structure/resources
• Industry Growth
• Normal Internal Operations
• Legacy Systems/Replacement
• Scalability
• Data/Information Management
• Business/Customer/Silos
• Customer Expectations
• New product and Services

Manage costs but also enable increase in revenues
6
SOA Transformation Top Issues

• Integration Complexity
• Integrate Business Process and Applications
• Internal COTS and Customized Systems
• External Partners and Customers
• What Technologies and Patterns to use?
• E.g. Oracle Fusion vs. IBM WebSphere
• E.g. Coarse vs. Fine-grained Services
• What Standards to use?
• TMF, OSS/J, TMN
• Canonical Messages and Enterprise Data Model
• Future On-boarding/Growth

7
SOA Transformation

• Service Provider OSS/BSS Reference Architecture
• Methodology
• Risks Challenges
• Mitigation Best Practices

8
OSS/BSS Reference Architecture
SOA Transformation
9
SOA Transformation Methodology
Six overlapping phases
10
SOA Transformation Dimensions
11
SOA Implementation Risks Mitigation

• Delayed implementations
• Design, Develop and Test Framework First
• Develop Services and compose business processes
  iteratively
• Cost overruns
• Prototype risk ridden interfaces and services
  before committing to a design there by reducing
  wasted efforts
• Avoid big-bang and implement iteratively
• Lack of ownership
• Implement Strong governance team and program
  management teams
• Technology obsolescence
• Have a technology roadmap, watch trends and stay
  on course
• Over dependency on single vendor
• Define and implement Conceptual Abstract
  framework for mapping the same to multiple vendor
  platforms and future versions
• Steep learning curve
• Make concepts clear and keep the design simple

12
SOA Application Performance Issues

• Working around Network Latency
• Designing coarse-grained services
• In some of our Projects this has been a design
  consideration minimizing the number of messages
  that travel on the network
• Avoid deep nesting of Web services. If
  unavoidable deploy on local high-bandwidth
  network
• Implementing client-side caching frameworks
• Separation of static part of messages from
  streaming part and re-assembling messages using
  cached static part
• Improving XML Performance
• XML compression implementation via SOAP
  extensions
• Use of XML Accelerators
• E.g. Sarvega XML Speedway for XSLT offload and
  for Virtual Web services
• Fast Web Services
• The advantages of XML's self-describing nature
  are offset by price on bandwidth and performance
• Uses Binary Data and also eliminates
  self-description by having client know the static
  description part ahead of time. Useful in
  scenarios where loss of self-description is not a
  requirement
• Improving throughput by queuing load on resources
• Use of Asynchronous Messaging Patterns

13
SOA Robustness Operational Issues

• Implement High Availability Disaster Recovery
  Features
• Optimize Servers and Standardize Operating
  Environment
• Standardize and implement Development Framework
  and Management/Monitoring Framework
• Implement BAM, error-exception-logging and
  auditing frameworks
• Implement Versioning of Services and have very
  clear configuration management processes
• Implement separate environments for Development,
  Integration, QA, UAT, Production and Disaster
  Recovery

14
SOA Engagement Models

• Due Diligence to elicit business requirements and
  current architecture
• AS-IS Architecture Analysis
• Requirements Analysis
• Reference Architecture Identification
• Gap Analysis
• TO-BE Architecture Definition
• Implementation Roadmap
• Plan and Define Projects
• Implementation in iterative phases
• Incremental Rollouts

15
Implementer Roles Satyam Customer

• Due Diligence to elicit business requirements and
  current architecture
• Satyam Provide Consulting Architects and
  Analysts, Conduct workshops, interviews, gather
  documents and artifacts, identify missing
  artifacts
• Customer Provide Contacts, Participate in
  Interviews, Workshops and Discussions, provide
  documents and artifacts
• AS-IS Architecture Analysis
• Satyam Provide resources to do the analysis and
  perform analysis with customer involvement
• Customer Participate in discussions and provide
  clarifications on architecture. Validate the
  analysis
• Requirements Analysis
• Satyam Provide resources to do the analysis and
  perform analysis with customer involvement
• Customer Participate in discussions and provide
  clarifications on requirements. Validate the
  analysis
• Reference Architecture Identification
• Satyam Identification and Customization
• Customer Review and Signoff
• Gap Analysis
• Satyam Provide resources and perform Gap
  Analysis
• Customer Participate in discussions, reviews and
  Signoff
• TO-BE Architecture Definition
• Satyam Jointly define target architecture,
  participate in discussions, product evaluations,
  do prototyping and performance benchmarking
• Customer Provide Infrastructure, define target
  architecture, participate in discussions,
  reviews, testing and signoff
• Implementation Roadmap

SAMPLE
16
QA
17
Satyam At A Glance
18
Thank You!

• Deepak Kataria,
• Head Architecture Consulting Advisory
  Services, Digital Convergence Solutions
• Deepak_Kataria_at_Satyam.com