Public Sector Integration Solutions

1
SOA for GovernmentEvangelizing Applied SOA for
Government Systems
Jordan Braunstein PS Business Systems
Integration Integration Solutions Group May 2007

• Public Sector Integration Solutions

2
Agenda

• What is SOA
• Federal Government SOA
• BearingPoint SOA

3
What is SOA ?
4
What is SOA?

• A Business-centric IT strategic model where
  business functionalities are made available to
  consumers as shared, reusable services via a
  centralized IT network.
• Solutions implemented using Services Oriented
  Architecture principles have many well publicized
  benefits, such as greater agility and reuse.
• Some of the key principles supporting SOA
• SOA architecture shifts focus from software
  functions to business functions
• A service is an executable piece of application
  that is composed of a well defined interface
  accessed by one or more consumers
• Software as a Service (SaaS)- Each service is
  owned, delivered and managed by one or more
  providers. Large application based solutions are
  replaced by smaller coarse-grained components.
• Service Oriented Development Of Applications- A
  new paradigm in application development where
  Composite Applications are assembled and
  Configured rather than programmed and replaced
  through the traditional software development
  approach

5
The Service Oriented Business Today
Businesses and individuals use Service Oriented
business models every day.
6
Service Oriented Architecture

• SOA is an architectural style whose goal is to
  achieve loose coupling among interacting software
  agents. A service is a unit of work done by a
  service provider to achieve desired end results
  for a service consumer. Both provider and
  consumer are roles played by software agents on
  behalf of their owners.
• http//webservices.xml.com/pub/a/ws/2003/09/30/soa
  .html

Consumer
Provider
Service
Consumer
Consumer
7
Principles and Advantages of Service Oriented
Solutions

• Standard way to work with other devices
• Standard way to plug in anywhere
• My phone works at your house
• A phone from overseas can work here with an
  adapter
• Standard way to address other systems
  (703-555-1212)
• Architecture enriches experience with
  additional services
• Caller ID
• Voicemail
• Call Waiting
• Additional features can be added (and ignored)
• Vendor Independent
• Doesnt matter what kind of phone I have
• Doesnt matter how old my phone is

8
SOA Is Not Web Services
SOA is about expediting business processes via
services while EAI is traditionally about data
integration via near-real time messaging (i.e.,
EAI connects silos, SOA breaks them apart) The
business orchestration of SOA is the real driver
to the reusability strategy, agility and
flexibility. Service orchestration brings to an
enterprise a business process model that can
significantly improve the flexibility and agility
with which business processes are remodeled in
response to changes
SOA
EAI
9
Real Time Business Is Critical To Every
Organization
Perform Trading Analytics
30 minutes
5 seconds
Airline Operations
20 minutes
30 seconds
8 hours
10 seconds
Handle Call Center Inquiries
Track Financial/Risk Position
1 day
5 minutes
Supply Chain Updates
1 day
15 minutes
Mail express fax e-mail
Document Transfer
3 days
45 seconds
Phone/Service Activation
3 days
1 hour
1 month
1 hour
Refresh Data Warehouse
Settle Trade/Transaction
5 days
1 day
Build-to-Order Product
6 weeks
24 hours
Seconds 107 106 105 104 1,000 100
10 1
Source
10
Why SOA?

• Based on our experience, the following are the
  main business drivers that organizations adopt
  SOA
• Reduce operational, maintenance management
  costs due to defects, complex and lengthy upgrade
  cycles and the fragility of hard-coded
  dependencies
• Provide business flexibility to transform the
  value chain, adjust business process to changing
  environments and adjust resources to fluctuating
  demands.
• Support legacy applications with important
  business value without constraining future
  development or enhancements
• Great, lets get couple of J2EE programmers to
  build it.

11
SOA Migration Strategy
Leverage
Multi Step Journey
Speed
12
AMR Research Data
13
Benefits and Challenges of SOA
Benefits
Implications

• Architectural Partitioning
• Synergy with Different Technologies
• Process visibility
• Greater maintainability
• Seamless Outsourcing
• Greater Deployment
• Reduced Maintenance cost
• Better risk management
• Reuse of services
• Faster Time to deployment
• Lower Development cost
• Greater Adaptability

• Higher upfront cost
• Cultural changes
• Infrastructure
• Formalized planning and methodologies
• Longer design time
• Testing and QA efforts
• Distributed environment
• Expanded use of middleware technology
• Transaction management
• Security
• Troubleshooting and monitoring
• Management and oversight
• Accountability/Ownership
• Funding and cost allocation (Investment)
• Prioritization and justification

Best Practices
Initiate and sustain executive sponsorship- SOA
is an enterprise wide initiative Introduce a
closed-loop SOA Governance model Develop a SOA
Committee Define strategic Intent Of SOA- goal
driven approach is the key Use Pilot based
approach as a SOA strategy
14
Integration Cost- Source ZapThink
15
The SOA Concept
16
SOA Reference Architecture
SECURITY
SOA MANAGEMENT
SOA LIFECYCLE
security policies
authentication
integrity
service administration management
logging
configuration management
monitoring
process
policies
compliance
security standards
authorization
non repudiation
QoS SLA
notification
auditing
standards
versioning
quality control
identification
confidentiality
security management
PRESENTATION TIER
Browser Channel
Web Services Channel
Development Channel
Portals (SOAP, JMS)
Composite Applications
Screen Flow Definition
Screen Flow Enactment
WS Façade
Rich Internet Application
PROCESS TIER
RULES
COMPOSITE SERVICES TIER
LEGACY SERVICES TIER
SERVICE ORCHESTRATION
INFORMATION INTEGRATION
Process Modeling
Process Monitoring
build
validate
Service design build
Session Integration
Content-based routing
Process Administration
Process Control
execute
Ontologies
Transaction Integration
Transformation
ATOMIC SERVICES
manage
Semantics
Aggregation
Process Automation
Process Analysis
report
Inferencing
Data Integration
Compensation
simulate
Semantic enactment
Persistence
SOA REGISTRY REPOSITORY
associations
discover
metadata
policies
notification subscription
reporting
publish
metadata versioning
analysis
configuration management
COMMUNICATIONS TIER
asynchronous
synchronous
publish/subscribe
reliable messaging
correlation
queuing
IT TECHNOLOGY TIER
Applications
IT Infrastructure
17
SOA Adoption Path
OptimizedBusiness Services
Enterprise Framework
PilotProjects
First Experiments
50 Services
10-50 Services

• B2B II
• Federated systems
• Large organizations

5-10 Services

• Corporate-wide approach

1-5 Services

• Prove it
• Standards solidify

• What is it?
• Can we use it?

18
BE SOA Adoption Strategy

• BE SOA Adoption Strategy
• Initiates and Sustains executive sponsorship
• Is Consensus based
• Provides one-stop shopping for guidance
• Focuses on training, education and skill
  refreshment
• Includes street-level strategy
• Advances relationships with customers to be more
  advisory and less administrative
• Is Coordinated with Enterprise Architecture
• Is based on service reuse

Bottom up

• A bottom-up approach is used to build the
  foundation
• We focus on using web services and other SOA
  product line to deliver solutions
• The focus of shared services developed are based
  on technology enabler such as security,
  transaction
• Small number of rogue services are developed

Top Down

• A Joined up organization
• Composite based application development where the
  focus is an automation, and micro-flow processes
• Strong governance model and leadership
  involvement
• Focus on business and technology shared services
  such as procurement, HR, and tax services.

19
SOA And Government
20
Presidents Management Agenda

• The United States Government is one of the
  largest users and acquirers of data, information
  and supporting technology systems in the world,
  currently investing approximately 65 billion
  annually on Information Technology (IT) PMA
  2005
• In the coming months, the Presidential
  E-Government initiatives will continue to
  graduate from the development and implementation
  phase to mature service offerings supported by
  service fees. This service-oriented approach will
  ensure that future government IT investments will
  leverage existing capabilities to their maximum
  potential and will provide the most efficient and
  customer-centered services PMA 2005

21
Presidents Management Agenda

• The Office of E-Government and Information
  Technology will provide leadership and support
  for
• Common solutions focused on results
• Interoperability, with the adoption of data
  standards and modernization efforts in lieu of
  legacy systems incapable of providing upgrades or
  cross agency support
• Improved service levels with a focus on the
  citizen and
• Adoption of best practices and shutting down
  ancillary and duplicative systems within and
  across the federal government.

22
FEA Transformation
23
Why does SOA Make sense in Government
24
Gartner Government Hype-Cycle 2006
25
SOA Adoption in Government

• According to our experience, Federal government
  has its own unique set of challenges in becoming
  a SOA based enterprise.
• EA Architects are driven and interested but are
  not involved. A high percentage of government
  agencies are interested in SOA but there are no
  clear leaders driving the federal agencies SOA
  strategy.
• The mega-deal effect-Most of the procurement
  efforts for the government are driven by large IT
  transformation efforts. The IS contractor is
  often concerned with developing the system and
  less concerned with the reusable services. The
  SOA Development Approach (SOADA) differs from
  more traditional development approaches in that
  it demands new skills from government personnel
  and contractors to succeed.
• Rogue Services- web services are often developed
  and deployed throughout the organization with
  minimum or no oversight.

26
BearingPoint and SOA
27
Our credentials- SOA is a business strategy and
must be handled in such a manner
28
SOA Maturity Model

• Level Five- Enterprise wide imitative where SOA
  is handled as a business strategy
• Level four- Metrics are collected to understand
  areas of concerns
• Level Three- Business Process Automation and
  collaboration
• Level Two- Architectural and technological
  standards
• Level One- Pilot based approach

29
BearingPoint SOA Maturity Model
30
An Approach to SOA
31
BE SOA Delivery Model

• Our SOA delivery model is a closed-loop model
  that builds on our past experiences and metrics.

Inception
Elaboration
Construction
Conception
32
Questions