2007: SOA Vision And Reality

1. Achieving Interoperability in Systems Architecture
SOA - Vision and Reality
Presented By:
Presented By:
Rajat Chopra
Rajat Chopra
Associate Director
Associate Director
Bell Canada
Bell Canada
rajat.chopra@bell.ca
rajat.chopra@bell.ca
October 04th, 2007
Bell Canada Confidential
1

2. BCE (Bell Canada Enterprises)
Profile
BCE is Canada's largest communications company, providing the most
comprehensive and innovative suite of communication services to residential
and business customers in Canada.
For 127 years Bell Canada has served Canadians’ communication needs. Under the
Bell brand, the Company's services include local, long distance and wireless phone
services, high-speed and wireless Internet access, IP-broadband services,
information and communications technology services (or value-added services) and
direct-to-home satellite and VDSL television services. Other BCE holdings include
Telesat Canada, a pioneer and world leader in satellite operations and systems
management, and an interest in CTVglobemedia, Canada's premier media
company.
As technologies converge and the internet’s potential is realized, Bell Canada is
evolving to serve Canadians with innovative solutions and services for another 125
years and beyond.
BCE shares are listed in Canada and the United States. BCE Inc. (BCE-T)
Visit us @ www.bell.ca
Bell Canada Confidential
2

3. What is Service Oriented Architecture? SOA
http://www.youtube.com/watch?v=sbd_1G8Kqjs
Bell Canada Confidential
3

4. Service Oriented Architecture – SOA
Basic Concepts
What is SOA?
•Service-oriented architecture (SOA) is an evolution of distributed computing based
on the request/reply design paradigm.
•An application's business logic or individual functions are modularized and
presented as services for consumer/client applications. What's key to these
services is their loosely coupled nature; i.e., the service interface is independent of
the implementation.
•Application developers or system integrators can build applications by composing
one or more services without knowing the services' underlying implementations.
For example, a service can be implemented either in .Net or J2EE, and the
application consuming the service can be on a different platform or language.
Bell Canada Confidential
4

5. SOA: Service Oriented Architecture
A PARADIGM SHIFT
Distributed Component Service Oriented Architecture
Architecture
Functionality Oriented Process Oriented
Designed to Last Designed to Change
Long Development Cycle Interactive and Iterative
Development
Cost Centered Business Centered
Application Block Services Orchestration
Tightly Coupled Agile and Adaptive
Homogeneous Technology Heterogeneous Technology
Object Oriented Message Oriented
Known Implementation Abstraction
Bell Canada Confidential
5

6. Market evolution of SOA
2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 - 2015
SOA
Composite applications. Trust. Metadata-
driven interoperability. Dynamic
negotiation. Federation.
Dynamic Interoperability
Business Services
Systematic approach to web services on enterprise level. Adding
visibility, compliance, governance, security and manageability …
Web services reuse & governance
Web Services
Developer-driven, basic web services standards-based
interoperability (SOAP, WSDL). Substitute for proprietary API’s.
Reuse of discrete legacy applications (Java, C++, etc.) and
newly created applications …
Standard-based enablement
Standards emerge, evolve … Registry becomes governance, mission critical … Run-time compliance, enforcement …
Federated
Web Services Registry
registries
Bell Canada Confidential
6

7. SOA: Starting from Reality
Hardwired connections between functions inhibit change
Non-SOA based application
Non-SOA based application
• Functions are hardwired together.
• The orchestration of functions cannot
be separated easily therefore changes
have a high cost and high effort.
Collect Order Validate Process Track
• Very little reuse and marginal flexibility
Data Order Order Order
SOA based application
SOA based application
• Each function is autonomous.
Orchestration
• The orchestration of functions is not
hardwire. Each function can work
independently. Therefore orchestration
can happen many different ways.
• Much more flexible, easier to make
change, high reuse, cheaper to change.
Collect Order Validate Process Track
• Requires more planning!
Data Order Order Order
Bell Canada Confidential
7

8. Reality: Confronting Complexity and Brittleness
Actual application architecture – Does this look familiar?
Mainframe apps - Blue
DRAFT Best Buy - Application Diagram V4 DRAFT Page 1 of 2
PC/NT apps - Green
November 10, 1999 Depository
Unix apps - Yellow
Banks
Vendor Setup
3rd party interface - Orange
Lines: Colors have no special meaning.
Vendor
They are to help make the diagram easier to Process Servers I17 Customer Perceived
Maintenance UAR - Universal Account
Budget
read. NEW Soundscan In-Stock
(Imaging) Sterling VAN
Reconcilliation
NPD Group
Analysis Tool Roadshow
For More Information: See the database Mesa Data Mailbox (Value)
Printer AIG Warranty Guard
S20-Sales
containing information about each Maintenance I13- Auto
Polling
application: Application V4.mdb I15 Hand Scan
Replenishment
I06 - Customer Apps
Printer PO Order
Insertions S01 - Sales
AIS Reports Orders Corrections
AIS Calendar
I06 Warehouse
Due Dates Print Costing
Management
General Invoice App
E13
Broadcast Maintenance
Stores & Mrkts
Fringe PO
E3 Interface
Filter
Smart Plus
M03 - Millennuim 3.0
Smart Plus
S04 - Sales Posting
Launcher
S07 - Cell
I03 Return to
Phones
P16 - Tally Sheet
D01 Post Load Vendor
M02 - Millennium S06 - Credit App
Billing
Equifax
Stock Options
S09 - Digital
I12 Entertainment
P15 EES Employee
Satellite
Software
Change Notice
L02-Resource
System
A04 - Cust L01-Promo
Scheduling
Refund Chks E01-EDI 1
Analysis
(Campbell)
P14 On-line New
Hire Entry
AAS V02-Price
Resumix P01-
Marketing
Washington,
Employee
Support
RGIS,
Masterfile
Ntl Bus Systems
P09 - P17
Cobra Frick S11 - ISP
Cyborg CTO2.Bestbuy.
Co Tracking
I10 Cycle Physical
CTS
com I04 Home Inventory
ACH Deliveries
V04-Sign
Prodigy
System U18 - CTO
I02 -
Banks - ACH and Pos to POS X92-X96
Transfers
Pay
Host to AS400
Communication
Plan Administrators
B01 - Stock
Spec Source
(401K, PCS, Life,
Status
SKU Tracking
Unicare, Solomon I11 Price
Smith Barney) I09 Cycle Counts Testing Supplier
S08 - Vertex
Compliance
S02 -
NPD,
Intercept Sales
E02-Employee Layaways
SoundScan
Tax
Purchase
Spec
I01 PO
Source SKU
Receiving
Scorecard - HR
Performance
V03- Mkt
Reactions L60 MDF
P09 Coop
S03-Polling I05
V01-Price Management SKU Selection
Bonus/HR
Inventory Info
System Tool
I35 - CEI K02
Customer Repair
ASIS Arthur Planning
I35 Early Warning
Tracking
System
I18
Rebate SKU Rep
Transfer
I55 SKU I07 Purchase
Information
Store Order Ad Expense
ELT
Monitor
G02 - General
PowerSuite
Ledger
Store
Scorecard
Sign
Texlon 3.5
System
NARM I14 Count Corrections Store Budget
Reporting
Valley Media
B02 Merchandise
U16-Texlon
CopyWriter's Analysis BMP - Bus
Workspace performance Mngt
EDI
Coordinator
Merch Mngr Approval
Batch Forcasting Journal Entry Tool Kit
AIMS
A05 - AP
Ad Measurement
AIMS Admin
INVENTORY CONTROL APPS - PC INVENTORY CONTROL APPS - PC
Cellular ACCTS REC APPS - PC
Code Alarm DPI/CPI 990COR
Rollover
AIMS Debit Receivings IC Batching
OTHER APPS - PC Bad Debt
Ad S05 - House Devo Sales
Reporting AP - Collections/Credit Inventory Adj/Count Correct Benefical Fees
Display Inventory
TM - Credit Card DB Inventory Control Reports Beneficial Reconcil
Launcher Charges
In Home Inventory Levels JEAXF
Junkouts Inventory Roll JEBFA
US Bank Recon Merchandise Withdrawl Merchandise Withdrawl
Optika JEBKA
PSP File Promo Credits Open Receivings JEDVA
C02 - Capital RTV Accrual PI Count Results JESOA
Shrink PI Time Results from Inv JEVSA
Projects Connect 3 ICMS Credit AP Research - Inv Cntrl Price Protection JEVSF
AP Research-Addl Rpts Sales Flash Reporting NSF
SiteSeer
In-Home Book to Perpetual Inventory Shrink Reporting TeleCredit Fees
Data Warehouse Close Out Reporting SKU Gross Margin
Repair Connect 3
Connect 3 Computer Intelligence Data SKU Shrink Level Detail
(Interfaces to and from the Cash Receipts/Credit
Reports
PDF Transfe Count Corrections USM
Data Warehouse are not F06 - Fixed Cross Ref for VCB Dnlds VCB Downloads
Misc Accounting/Finance Apps - PC/NT
displayed on this diagram) Assets
Warranty Damage Write Off
COBA (Corp office Budget Assistant) Debit Receivings
Billing Star Repair PCBS(Profit Center Budget System) DFI Vendor Database
Cash Over/
System Display Inventory Reconcil
Merchandising Budget
Short Prepared by Michelle Mills
Display Inventory Reporting
Bell Canada Confidential
8

9. Driving a New Architecture: Today’s Challenges
• Support an agile business model
– The marketplace is changing - businesses need to change too
– Many existing IT systems are inhibitors to change: complex and inflexible
– Existing integrations can be inhibitors to change: multiple technologies, point-to-point
integration, inflexible models
• Drive down cost
– Eliminate duplicate systems
– Re-use, don't re-build
– Simplify skills base
• Reduce cycle time and costs for external business processes
– Move from manual transactions with suppliers towards automated transactions
– Facilitate flexible dealings with partners with minimal process or IT impact
• Integrate across the enterprise
– Integrate historically separate systems
– Completion of mergers and acquisitions
– Across physical and technology barriers
Bell Canada Confidential
9

10. Are you ready for change?
Be prepared for change.
It’s the only thing you can count on.
Bell Canada Confidential
10

11. The Vision of SOA
An enterprise whose business processes -- integrated end-to-end
across the company and with key partners, suppliers and customers
-- can respond with speed to any customer demand, market
opportunity or external threat.
A service-oriented architecture provides flexibility to
change; enabling the creation of an on-demand eco-system.
Bell Canada Confidential
11

12. What Is Service Oriented Architecture?
It’s different things to different people
Roles
A set of services that a business wants to expose
to customers and clients
Business
an architectural style which requires a
service provider, requestor and a service
description.
a set of architectural principles and patterns
Architecture
which address characteristics such as
modularity, encapsulation, loose coupling,
separation of concerns, reuse, composable
and single implementation.
A programming model complete with standards,
Implementation
tools, methods and technologies such as web
services.
Bell Canada Confidential
12

13. Design Pattern for an implementation of SOA
The “Factory” Model
• A design pattern used to
implement the services.
Sports Car Factory
Car
Manufacturing
Service
SUV Factory
Raw
Materials
Min-Van Factory
Bell Canada Confidential
13

14. SOA - Service Oriented Architecture Illustrated
Composition: Workflow of services to obtain a business process
Ser2 Ser4
Business
Ser1
Process
Ser3 Ser5
Ser1 Ser2 Ser3 Ser4 Ser5 Services built of components:
-Basic have one component
Services -Composite have multiple
components.
Some Components can come
from existing applications and
Components Cpt1 Cpt2 Cpt3 Cpt4 Cpt5 others can be created from
scratch.
Existing Application Application A Application B
Resources
Bell Canada Confidential
14

15. “Web Services” is the enabling technology for achieving the value
of Service Oriented Architecture in the Enterprise
Business flexibility provided by increased granularity of
processes enabled through services
Business Ability to quickly create business processes and composite
applications to respond to changes in the marketplace
Benefits
Improved customer service using services without having to
worry about the underlying IT infrastructure
Becoming a more responsive IT organization with a secure
and managed integration environment
Decrease development and deployment cycle times through
IT the use of pre-built, reusable services building blocks.
Benefits Reducing complexity and maintenance costs with common
services
Enhancing existing IT systems rather than replacing them
Bell Canada Confidential
15

16. Things you need to realize the vision of SOA
• What to build: Reference Architecture: E.g. SOA
Layered Architecture
• How to build: Service-oriented Modeling Method
• Whether to build: Assessments; Roadmaps; Maturity
• Guidance on Building: Patterns: Architectural and
Design
• Oversight: Governance
• How to Build: Standards
• How to Build: Tools
Bell Canada Confidential
16

17. Organizations can take different paths to eventual adoption of
SOA depending on their business goals and IT constraints
Entry Points
Based On Business
Broad transformation of existing business models or the On Demand
Priorities
deployment of new business models Business
4 Transformation
An architected implementation enabling integration
across business functions throughout an enterprise
Business Value
Enterprise Wide IT
3 Transformation
Integrating services across multiple
applications inside and outside the
enterprise for a business objective
Service Oriented Integration of Business
2
Functions
Creating services
from tasks contained
Implementing Individual Web Services
in new or existing
applications
1
Bell Canada Confidential
17

18. Things to focus on and watch out for during your SOA
project / transformation
• Legacy systems contain a wealth of tangled functionality
that is not easily extricated and componentized without
tools and methods.
• Current tools are only beginning to provide adequate
(“the entire Web services stack”) support for Web
services standards.
• Quality of service is an issue. Security, reliability and
manageability of transactions as well as the performance
of the system as a whole is a major concern for clients.
Bell Canada Confidential
18

19. Evolving to SOA: Conceptual Approach
1. Break down the business into components
2. Decide what is strategically important, and what is just
operations in the value chain domains
Business 3. Analyze the different KPI’s attached to these components
Architecture 4. Prioritize and scope your transformation projects
1. Define a Service Model
2. Identify your services based on your business components
3. Specify the services and components accordingly
Service
4. Make SOA realization decisions based on architectural
Modelling
decisions
1. Implement a Service Model
2. Develop a service-oriented architecture to support the
Componentized Business
SOA 3. Implement service based scoping policy for projects
Realization 4. Implement appropriate governance mechanism
Business-Aligned IT Architecture
Bell Canada Confidential
19

20. Implementing SOA: A Proposed Approach
• Phase II: Pilots and Roll-out planning
• Phase I: SOA Planning
– Pilots Execution
– Readiness Assessment
– CoE setup
– Initial SOA Reference Architecture and
Standards – Detailed SOA Governance, Organization,
Processes, Methods and Policies
– Key Services Identification & Planning
– Defined change management processes
– Initial SOA Governance, Organization,
Processes, Methods and Policies – Updated Services Identification & Planning
– Core Team Identification and Coaching – SOA Adoption planning
– Scoping and planning of pilots • Extended team identification and
education
– SOA Program strategy and Planning
• New Projects enablement strategy
• Oversight committee
• Business Process Improvement
• Program Manager
enablement strategy
• Common Services
– Updated SOA Reference Architecture
• CoE
– Select projects for first roll-out
– Define key services and services packages
for select number of projects
• Phase III: Roll-out to selected projects
• Phase IV: End State SOA
– Apply SOA to selected projects
– SOA applied across all projects
– Update CoE artifacts
– On going services identification, definition
and maintenance – Update service identification
– Updated governance – Plan new initiatives with SOA
Bell Canada Confidential
20

21. Harnessing the benefits from SOA and Web services
Tangible and immediate business benefits
You’ll see Resulting in…
• Faster integration and economy of scale • Improved efficiency
• Reduced costs
• Reduced development time
• Improved consistency and lowered risk
• Simplified process management and automation
• Better communication with customers and partners • Revenue growth
• Customer
• Easier access to internal and external resources
acquisition
• Faster time-to-market
• Better access to business functions • Faster technology
adoption
• More responsive and scalable business
• Increased flexibility
models and IT systems
Bell Canada Confidential
21

22. Summary
• SOA is the architectural response to Business
Agility requirements.
• Service Oriented Architecture is based on a 3-layer
model of “components”, “services” and “processes.
• Several components comprise an SOA framework:
service provider, service consumer, service
definition, service infrastructure, services layer, and
governance.
• SOA principles include modularity, encapsulation,
loose coupling, separation of concerns, reuse,
composable and single implementation.
• Customers will take different adoption paths in their
implementation of SOA.
• SOA benefits to the business are in the ability to
introduce products to market faster, business
transformation, and lower maintenance costs.
References:
http://www.ibm.comConfidential
Bell Canada
22
http://www.bea.com
Forrester Research

23. Questions
?
Bell Canada Confidential
23