Title: SERVICE ORIENTED ARCHITECTURE
1- SERVICE ORIENTED ARCHITECTURE
- (SOA)
2Outline
- What
- Why
- How
- Business Cases
- Vendors
3What is SOA
4The Definition
- A service oriented architecture is an
information technology approach for building
applications that implement business processes
(services) by using a set of loosely coupled
black-box components orchestrated to deliver a
well-defined level of service. -
5Lego blocks
- Interoperable
- Unbreakable
- Composable
- Reusable
6What Technology is SOA Replacing?
Current IT System
Component Based IT
7The Magical Black Box
- A Component or Device
- Inner workings are not understood
- Hides Complexity
INPUT
Services
OUTPUT
8If it aint broke, dont fix it
- Its all about reusing existing systems...
SERVICES HUB
Adapter
Adapter
ORIGINAL INVOICING SYSTEM Written in JAVA
OLD SCHOOL ORDER PROCESSING Written in COBOL
Adapter Lego Bumps Web Services
9How Lego Blocks are like Services
- Industry Standard Interface
Industry Standard Bumps
Any Lego block will fit into any other Lego block
CREDIT CHECK
10Web Service
- Common Interface Think Lego Bumps
- XML
- WSDL
- SOAP
11Extensible Markup Language (XML)
- A human readable way of organizing documents on
the internet - ltProjectgt
- ltNamegtSOAlt/Namegt
- ltDescriptiongtCool Technologylt/Descriptiongt
- lt/Projectgt
12Web Services Description Language (WSDL)
- Describes all the commands and data required to
use a Web Service - Defines the Bumps
getInvoice addInvoice deleteInvoice
13Simple Object Access Protocol (SOAP)
- A standard language that enables components to
talk to each other
14All Together Now
Phone Book for Services
Service Registry
Publish WSDL
Lookup Services
SOAP
SOAP
1
2
3
Service Provider
Service Consumer
SOAP
Request and Provide Service
15Why SOA
16Why SOA?
- Do you want your business to?
- Respond quicker to marketplace
- Better align processes with business goals
- Make processes faster and more efficient
- Realize greater agility in your business
practices - Allow re-use of current systems
17Why SOA?
SOA
A way to develop a flexible technical architecture
A way to streamline business processes
A way to become more agile
- Improved visibility within and across a process
- SOA services can deliver information faster and
to more systems
- New value from existing investments
- Architecture components are less technically
dependent
- Faster speed to market for future changes
- Increased customer satisfaction
- Easy integration of future systems
18BPM SOA
- Improvement of the entire business process
lifecycle, including modeling, management and
optimization of processes -
- Single dedicated interface that guides you
through information and provides information in
the appropriate format -
- User empowerment balanced with corporate need for
control and management
19How to Implement SOA
205 Considerations
- Understanding the pain
- Defining the value
- Focusing on understanding
- Remembering the people
- Concentrating on the long term value
21Roadmap
- Have you considered?
- Adoption and maturity models
- Where is the enterprise at in the relative scale
of maturity in the adoption of SOA and Web
Services? - Assessments
- Does the company have pilots?
- Has the organization dabbled into Web services?
- How good is the current architecture?
- Should the organization keep going in the same
direction? - Will this scale to an enterprise SOA?
- Have you considered everything you need to
consider?
22Roadmap
- Have you considered?
- Strategy and planning activities
- How does the company plan to migrate to an SOA?
- What steps, tools, methods, technologies,
standards and training need to be taken into
account? - Whats the roadmap/vision and how will the
company get there? Whats the plan? - Governance
- Should API or capability become a service? If
not, which ones are eligible? - Every service should bring value to the business.
How will the company manage this process without
getting in the way? - Implementation of best-practices
- What are the best ways implement security,
ensuring performance, complying with standards
for interoperability and designing for change?
23Business Cases
24ACUITY
- Opportunity
- Insurance company foresaw opportunity to
increase premiums and agent productivity by
making it faster and easier for agents to access
information - Solution
- Created direct company-to-company communication
processes - connecting agents own management
systems to its core insurance transactions - by
creating an adaptable, open infrastructure using
industry standards - Key Benefits
- 200 million increase in premiums over a 2-year
period 15 higher profitability than national
average for property-casualty insurance
companies 40 increase in average premium per
agency in most recent fiscal year
25Broward County School Board
- Opportunity
- Transform an IT environment that inhibited
information access and stakeholder
productivityhindering student achievement and
compliance with mandates such as the No Child
Left Behind Act - Solution
- Implement a cost-effective and powerful platform
designed to provide students, parents, educators
and administrators with integrated, role-based
access to educational resources, applications and
collaborative tools - Benefits
- Integrates people, processes and information
can help improve decision making can help
increase efficiency and effectiveness in school
operations enhances flexibility for all
stakeholders
26Ohio Casualty
- Opportunity
- Needed an effective way to improve the quality
of the applications, while lowering costs and
verifying compliance with continuously evolving
regulatory requirements - both at the state and
federal level - Solution
- The company used IBM Rational testing products
to ensure quality and regulatory compliance. The
company also adopted a more service-oriented
approach, supported by the IBM Rational Software
Development Platform, IBM Rational Unified
Process methodology, and IBM Information
Management products - Benefits
- Passed numerous internal and external compliance
audits without problem. Individual productivity
and team efficiency have increased. They are
better able to govern their development efforts
and teams are better able to communicate
resulting in less re-work, higher quality
software, and faster time to market
27Vendors
28Vendors
29Start small, but start now
- Interoperable
- Reusable
- Agile
- Efficient
- Flexible
30Questions?