The Road to SOA

1
The Road to SOA
2
Whats the target ?
3
The SOA Reference Architecture
Operational Management
SOA Delivery
Application composition
Native services
Communications
Operational storage
Security and policy enforcement
Runtime governance
Modeling, Design, Development
4
Pragmatic Next Steps for SOA
5
Gap Analysis

• An industry Best Practice is to augment your
  existing governance structure with a support
  group or competency center for successfully
  deploying any new technology.
• Integration Competency Centers (ICC) have evolved
  for addressing integration technologies
• Shared Service Organizations in addition to an
  ICC have evolved for addressing the adoption of
  SOA.
• Many companies extend their existing ICC to
  address SOA.

6
Introducing The SOA CC
7
Evolution of the SOA CC
Best Practices
Technology Standards
Shared Services
Central Services
Process Defined Defined Defined Defined
Technology Recommended Standardized Standardized Shared
Organization Distributed Distributed Hybrid Centralized
Benefits
Knowledge Leverage
Resource Optimization
Consistency
Control
8
SOA CC Interaction
9
Design for Change
Improve
Transition
Agile
Waterfall
Review

• Change during a project is expensive so define
  everything up front so nothing needs to change
• Large deliverables
• Longer Cycles
• Large Analysis

• Change during a project is expensive and
  unavoidable so do everything possible to
  minimize the cost of change
• Smaller deliverables
• Shorter Cycles
• Smaller Analysis

• Continual process improvement

• Strategies
• Composition
• Versioning
• Testing
• Operations

10
Development and Support Disciplines
11
Enterprise Disciplines

• Before projects start perform planning around
  services
• Service Versioning Strategies
• Configuration Management Process
• Major/Minor versioning schemes
• Deprecation Policies
• Service Testing Strategies
• Complete Testing
• Collaborative Testing
• Continuous Testing
• Service Capacity/Sizing
• of Versions
• of Consumers
• Transaction Volumes
• Write the policies
• Determine if they can be enforced with technology

12
Organizational Functions
Overall alignment of business goals, multi-year
plans, and opportunities.
Cross-functional team responsible for ensuring
optimal alignment of IT capability with business
goals - minimizing implementation, runtime,
evolution costs, complexity, downtime, and
technology risk.
Enterprise Architecture
Business focus on improving their results / goals
by determining tactile change to business
operations (leveraging IT capability).
Overall IT governance capability for the overall
lifecycle project Management, systems
development, testing, release, change management,
system support.
Connecting applications together
includingtraditional EAI and B2B disciplines,
with re-usable interfaces and inter-application
standards.
Disciplines for application development,
packaged application customization and
implementation.
13
Waterfall Methodologies and SOA

• The Premise Change during a project is
  expensive, so define everything up front so
  nothing needs to change
• SOA Impact Considerations
• Architects at the front of the Waterfall Process
  need to have tight integration with service
  registries.
• Specifications need to be updated as service
  versions evolve in outside efforts
• Use and modification of services across projects
  must be handled via outside governance
• Developed services are enterprise assets
  testing and release of service sub-components may
  need to move towards iterative models
• Testing during the development cycle needs to
  adopt automation and continuous regression
  concepts
• Functional Domain Models hugely important
• Process-centric business development moves out
  of purview of application development to BPM
  which can be a difficult transition

14
Agile / Iterative Methodologies and SOA

• The Premise Change during a project is
  expensive And Unavoidable so do everything
  possible to minimize the cost of change
• SOA Impact Considerations
• Just in Time building can limit future re-use
  opportunities for services without careful
  consideration
• This project only philosophy can make it
  challenging for effective outside governance
  enforcement
• There is typically no re-use metric within these
  methodologies
• Integrated testing model fits amazingly well
  with SOA
• Closer involvement of business sponsors can
  facilitate line between business logic hard-coded
  within services and process logic / business
  rules held in more flexible, abstracted
  technology

15
Role Changes within Application Delivery

• Application Architects
• The role specialization between application and
  enterprise architects grows
• Enhanced knowledge of the companys inventory
  of service assets required
• Run-time information and service level exchanges
  required for web services in building
  applications
• Service Developers
• Building towards a detailed policy for service
  definitions
• Services begin to give up process logic to
  outside orchestration
• Good understanding of object and functional
  models
• Testers
• End-to-end, automated regression testing
  important
• Version testing important
• Must begin to gain greater system design
  understanding

16
SOA-ing the Integration Competency Center
Service-enable existing End-Points Evolve
Point Integration to Enterprise Service
Bus Composite Service Creation Metadata /
Policy Management Web Services
Management Integrated / Automated Composite
Testing
17
Organizational Governance
Governance, more than any other area, will drive
the success or failure of a scalable SOA strategy
LOB Project Prioritization along Pre-Agreed
Axis Higher level IT Processes are implemented
at the services layer Asset, Change and
Configuration Management Project Governance of
SOA Usage / Adoption Governance of Process Usage
/ Adoption Governance of Development and
Application Architecture The Registry Owner
lives here Think about how other technology
assets are managed and you are on the way
18
Rise of the SOA Enabled Business Analyst
Greatest Impact in terms of Efficiency The true
key between IT Integration 2.0 and
Business-Agile SOA The SOA Analyst Expanded
Roles New Training and Concepts!! BPM / BAM
Embedded in the SOA Business-level
Semantics True Process Improvement Discipline
Huge Value and potentially huge cultural threat
19
Enterprise Architecture Front and Center
SOA Mandates the end of the Ivory
Tower Increased control increased
accountability and measurements Multi-Year view
combined with incremental ROI measurement Techno
logy-first infatuation is a detriment In some
organizations these teams are evolving to
delivery centers for Enterprise Assets
20
Communication with the Business
End of the silos Requires maturity in the face
of true IT execution capability Process-centric
focus drives more complex IT-LOB relationships
21
Funding / Budget for Shared Services Whats
the Answer?

• Allocation Models often deployed in the industry
• He who comes to the river builds the first
  bridge
• Enterprise Funding Business Level belief
• IT Funding Infrastructure team responsible for
  mitigating complexity and cost
• Cost Shielding Net zero, hiding ABC Costing
• Chargeback Unit Mechanisms often deployed
• Shared service units virtual units created
  based on underlying
  transaction rate consumption of
  assets
• Tiered service units virtual units based on
  underlying
  consumption, level of service, and/or
  consumer
• Enterprise Pool Higher level distribution of
  cost of enterprise assets
  not based on direct usage (based on
  revenue, LOB employee count, etc)

22
Get Started with an SOA Implementation

• Keys to a successful
• Quick Start
• Start small
• Non-production vs. production
• Evolve SOA
• Integrate with strategic direction
• Disciplined approach

23
Quick-start use industry standard

• Use specification from an industry standard (e.g.
  eTOM for telecommunications)
• Top-down business process definition approach is
  possible
• Focus on DesignTime and ChangeTime
• As services are identified and deployed, evolve
  into RunTime mediation and governance

24
Managing Outcomes

• Step One Establish top level goals and outcomes
• Measurable goals
• Metrics Reporting and Auditing
• Step Two Establish policies and contracts
• Accountability, adjudication, responsibilities
• Interoperability Standards
• Service Lifecycle Processes
• Security Policies
• Step Three Build the Foundation
• Assign ownerships, budgets and responsibilities
• Develop Organizational Tools (CoE, chargebacks,
  shared services org)
• Establish federated systems of record for
  policies, contracts and services
• Automate governance processes

25
Resources centrasite.org
26
softwareag.com

• Where are you?
• Business context
• Arch and Tech
• Governance Process
• People
• What is your destination / itinerary?
• Vision
• Evolution
• Alignment