Сервисно-ориентированная архитектура (СОА). Теория и практика интеграционных проектов

1. Сервисно-ориентированная архитектура (СОА).Теория и практика интеграционных проектов ВЫСШАЯ ШКОЛА МЕНЕДЖМЕНТА Санкт-Петербургского государственного университета 28 апреля 2008 г.

2. Сущность и цели подхода СОА

3. Architectural Evolution in the Enterprise • The Path to a Modern Services-Based Architecture Future 1980’s to Mid 1990’s Mid 1990’s to Early 2000’s Pre 1980 Today Client-Server Architecture Monolithic Architecture Network Centric Architecture Service Oriented Architecture / Web Services Dynamically Re-configurable Architecture • Service Oriented Computing • Web Services Architecture • Open Standards • Mainframe • Visual Basic • PowerBuilder • eBusiness • eCommerce

4. SOA Business Integration Built on a Foundation of SOA Achieving Better Business Results by Increasing Your Service Orientation Business Flexibility Dynamic Business Processes Using Composite Applications for IT Transformation Leveraging an ESB for Service-Oriented Integration Implementing Individual Web services

5. SOA Value Proposition Increase Revenue Create new routes to market; create new value from existing systems Provide a Flexible Business Model React to market changes more quickly Reduce Cycle Times and Cost for External Business Partners Move from manual to automated transactions; facilitate flexible dealings with business partners Integrate across the Enterprise Integrate historically separate systems; facilitate mergers and acquisitions of enterprises Reduce Risk and Exposure Improve visibility into business operations Drive down Cost Eliminate duplicate systems; build once and leverage; improve time to market

6. Pain Points Addressed by SOA Solution

7. Observed Business Pain Points Leading to SOA Projects The projects were driven by business reasons, not technology implementation preferences Need for Technology Change • Obsolete/legacy systems • Insufficient capacity/low reliability • Rigid systems that were difficult to change Demand for Collaboration • Need to share information and services with partners, suppliers, distributors, and clients Competitive Pressures • Competitors adopting faster, more flexible solutions • Enabling deployment of products and services • Improving customer service Mandates • Compliance with government or company mandates Supplier/Distributor Demand • Demand for improved connectivity • Move away from proprietary, point-to-point solutions Enter New Markets • Use exposed services to create new lines of business

8. Benefits Resulting from SOA Solution All clients interviewed cited improved flexibility as a benefit of SOA, and most experienced profitability impact

9. Characteristics of an SOA • Strong Business-IT alignment – ability to clearly articulate and optimise business value of technology • Agility - Changing business requirements can rapidly be supported • Build on existing investments – no need to re-implement components every time a new technology comes along • Enterprise level focus – avoid duplication of function, achieve consistency, joined up business processes

10. Business expertise Business expertise Technical expertise Technical expertise Business and IT Work Much More Closely and in Partnership Users Define/refine business processes Users Define/refine business processes Application Developers Assemble and configure building blocks into processes Extensive overlap Limited overlap Service Developers Create application building blocks - patterns, templates, and components Developers Program the applications

11. The Transforming Development Model From To • Function-oriented • Build to last • Prolonged development cycles • Process-oriented • Build to change • Incrementally built and deployed • Application silos • Tightly-coupled • Structuring applications using components and objects • Known implementation • Orchestrated solutions • Loosely-coupled • Structuring applications using services • Abstraction and virtualization

12. Определение СОА

13. Terms of SOA … service orientation? A way of integrating your business as linked servicesand the outcomes that they bring … a service? A repeatable business task – e.g., check customer credit; open new account … a composite application? A set of related & integrated services that support a business process built on an SOA … service oriented architecture (SOA)? An IT architectural style that supports service orientation

14. SOA Means Many Things Based on Your Perspective “SOA in context …” • A set of services that a business wants to expose to their customers and partners, or other portions of the organization Business • An architectural style which requires a service provider, requestor, and a service description • A set of architectural principles, patterns, and criteria which address characteristics such as modularity, encapsulation, loose coupling, separation of concerns, reuse, composability, and single implementation Architecture • A programming model complete with standards, tools, and technologies such as Web Services Implementation

15. ... And What SOA Is Not • SOA is not: • Something you can buy out of the box • A product • WebSphere • Using an ESB (Enterprise Service Bus) • EAI (Enterprise Application Integration) • WSDL/SOAP • Software component reuse • Tied to a proprietary technology • An IT only initiative • Primarily a cost saving approach

16. Aspects of SOA: Architecture • Service Consumer • Service Provider • Service Description • Service Broker • Service Registry invokes 1..* «realize» «use» Service Consumer Service Description Service provider + binding + findService ( ) + invokeService ( ) + bindToService ( ) + bindToService ( ) + Operations ( ) + invokeService ( ) + provisionService ( ) * «contains» «described in» + monitorService ( ) Service Broker + findService ( ) 1..* 1..* Service Registry searches publishes 1..*

17. Service Consumer consumers 6 8 9 5 7 JService Portlet WSRP B2B QoS, Security, Management & Monitoring Infrastructure Service Data Architecture & Business Intelligence Governance 4 Integration Architecture (Enterprise Service Bus) business processes process choreography 3 business services atomic and composite services Service Provider 2 components enterprise components 1 Custom Application Package operational existing application resources Composite service Atomic service Key Aspects of SOA: Services, Components, Composition, and Choreography

18. Сервисно-ориентированный подход является результатом развития методов интеграции

19. Complexity is a problem

20. Target Application Source Application Transport Interaction Logic Process Logic Business Rules Application Code Point-to-Point Integration • High coupling, low cohesion, and no encapsulation • No reuse • Difficult to change • Rising cost per interface keeps

21. Point-to-Point Integration Approach • Low overhead to get started. • P2P can be the best approach for connecting a few applications where few changes are expected. Financials Sales Force Automation Mainframe/VSAM Marketing NT/Oracle NT/Sybase ERP Order Entry Unix /Oracle Unix/Oracle Credit Card Call Center Mainframe/VSAM Unix /Oracle e-Business Unix/Oracle

22. Translation Mapping Target Application Source Application Routing Augmenting Interaction Logic Process Logic Business Rules Application Code EAI without SOI • Lower coupling, higher cohesion, and some encapsulation • Impairs reuse • Complicates change • Makes cost per interface more consistent

23. Consumer Touchpoint Consumer Touchpoint Batch Batch POSUpdates FOSUpdates Store Ope. Store Ope. Continuous Supply Continuous Supply Integration & Process Flow Hub Date Warehouse Date Warehouse Loyalty Program Loyalty Program Ordering Ordering Financial Sycs Financial Sycs Planning Planning COS COS Marketing Marketing Marketing & Merchandising Marketing & Merchandising Clearing Clearing Partners & Suppliers Partners & Suppliers Enterprise Application Enterprise Application Comparison of P2P and EAI Point-to-Point Integration EAI Hub-and-Spoke Integration The right integration infrastructure can help customers reduce costs, improve flexibility, and provide greater visibility into business transactions.

24. Declarative Rules Integration Services Routing Translation Augmenting Mapping Source Application Target Application Service Sequencing Boundary Services Interaction Logic Process Logic Business Rules Application Code SOI Uses a Layered Architecture • Low coupling, high cohesion, and encapsulation • Increases productivity • Eases change • Improves reuse

25. Enterprise Service BusTying Disparate Applications Together … Synchronous RPC Web Services Asynchronous Messages Publish/ Subscribe Managed FTP COBOL Copybook XML FIX SWIFT HIPPA HL7 ebXML AL3 ACORD EDI-X.12 EDI-FACT Custom Formats Word/Excel/PDF RPG Disparate platforms, devices, & protocols Disparate Programming languages Disparate Data formats

26. Implementing an SOI style integration layer provides a foundation for implementing an SOA. Service-Oriented Integration Application of service-oriented architecture principles to build a service-oriented integration layer: • An architectural style which requires a service provider, a service requestor, and a service description • A set of architectural principles, patterns, and criteria which address characteristics such as modularity, encapsulation, loose coupling, separation of concerns, reuse, and composability • A programming model complete with standards, tools, and technologies such as Web Services

27. SOI – Four Architecture Principles • Boundary services • Encapsulate and isolate the industry, LOB, and regional requirements • Integration services • Separate the services which perform routine integration activities, which are stateless and context-free, so they can be called in any sequence or not at all • Declarative programming model • Separate the business rules from the implementation of SOI services • External sequencing of services • Separate the process logic from the integration and boundary services

28. Справочная модель СОА

29. The IBM SOA Reference Model is a shared view of the Components that make up an SOA Business Services Facilitates better decision-making with real-time business information Interaction Services Enables collaboration between people, processes, and information Process Services Orchestrates and automates business processes Information Services Manages diverse data and content in a unified manner DevelopmentServices IT ServiceManagement Facilitates communication ESB between services Integrated environment for design and creation of solution assets Manages and secures services, applications, and resources Partner Services Connects with trading partners Business App Services Builds on a robust,scaleable, and secure services environment Access Services Facilitates interactions with existing information and application assets Apps & Info Assets Infrastructure Services Optimizes throughput, availability and performance

30. Подход к построению СОА

31. SOA does not happen by magic • SOA will not arise spontaneously • It requires organisational change and a top down approach • Business and IT must work closely together • The service portfolio must be managed as an asset • New governance structures needed • Requires incentives for reuse

32. Step 2: Define a Service Model • Service Oriented Modelling and Architecture • Identify your business services based on your business components • Identify your business processes • Specify the services, processes and components accordingly • Make SOA realization decisions based on architectural decisions • Step 3: Implement a Service Model • Develop a service-oriented architecture to support the Componentized Business • Implement service based scoping policy for projects • Implement appropriate governance mechanism Business-Aligned IT Architecture SOA steps • Step 1: Break down your business into components • Component Business Modeling • Decide what is strategically important, and what is just operations in the value chain domains • Analyze the different KPIs attached to these components • Prioritize and scope your transformation projects CBM Strategy SOMA Modeling SOA Realization

33. Шаг 1. Построение Компонентной модели бизнеса (CBM)

34. Business Administration New Business Development Relationship Management Servicing & Sales Product Fulfillment Financial Control and Accounting Direct Control Execute On the first step business is breaking down into top level components Columns are Business Competencies, defined as large business areas with characteristic skills and capabilities, for example, product development or supply chain. A Business Component is a part of an enterprise that has the potential to operate autonomously, for example, as a separate company, or as part of another company. An Operational Level characterizes the scope of decision making. The three levels used in CBM are direct, control and execute. • Direct is about strategy, overall direction and policy • Control is about monitoring, managing exceptions and tactical decision making • Execute is about doing the work Account Planning Portfolio Planning Business Planning Sales Planning Fulfillment Planning Sector Planning Business Unit Tracking Sector Management Relationship Management Sales Management Fulfillment Planning Compliance Reconciliation Product Management Credit Assessment Staff Appraisals Staff Administration Customer Accounts Product Directory Credit Administration Sales Product Fulfillment Marketing Campaigns Customer Dialogue Document Management General Ledger Production Administration Contact Routing

35. IT Customer Relationship Management IT Business Management Business Resilience Information and Knowledge Management Service and Solution Development Service and Solution Deployment Service Delivery and Support Deployment Strategy Services Delivery Strategy Business Resilience Strategy Information Management Strategy Business Enablement Service & Solution Strategy Business Technology Strategy Development Strategy Directing Enterprise Architecture Regulatory Compliance Strategy Knowledge Management Strategy IT Support Strategy Portfolio Management Integrated Risk Strategy Technology Innovation Business Performance Planning Information Architecture Operations Planning Change Planning Financial Management Continuous Business Operations Services and Solutions Lifecycle Planning Controlling Regulatory Compliance Information Resource Management Business Technology Performance & Value Demand Management Infrastructure Resource Planning Release Planning Services and Solutions Architecture Integrated Risk Management Communications Planning Support Services Planning Knowledge Resource Management Human Resources Management Security, Privacy And Data Protection Change Implementation IT Financial Management Business Resilience Data and Content Management Service and Solution Creation Business Performance Mgmt Support Services Management Executing Staff Administration & Development Infrastructure Resource Management IT Service and Solution Marketing Knowledge Capture And Availability Release Implementation Regulatory Compliance Remediation Service and Solution Maintenance Supplier and Contract Administration Infrastructure Operations CBM – whole business on one list of paper

36. Business Administration Financial Management Product/ Process Production Supply Chain Marketing & Sales Service & Aftersales Supply Chain Strategy & Planning Customer Relationship Strategy Post Vehicle Sale Strategy Corporate/LOB Strategy & Planning FinancialPlanning & Forecasting Portfolio Strategy & Planning Production Strategy Direct Organization & Process Policies Research & Development Master Production Planning Demand Planning Sales & Promotion Planning Capital Appropriation Planning Supplier Relationship Planning Alliance Strategies Design Rules & Policies Production Rules & Policies Brand Management Warranty Management Human Capital Management Risk Management & Internal Audit Program Management Production Scheduling Supply Chain Performance Monitoring Relationship Monitoring The Value Chain Administration Administration Administration Administration Asset Mgmt & Asset Mgmt & Development Development Management Management Customer Customer Business Business Marketing Marketing Business Business Product Product Sales & Sales & Channel Channel Service Service Contract Contract Finance Finance New New Configuration Management Business Control Legal & Regulatory Demand Forecast & Analysis Activity Level Production Monitoring Treasury Supplier Management Planning Accounting Manufacturing Operations Business Analysis & Distribution &Finance Planning Planning Planning Planning Refinement Planning DesignValidation Quality Management Financial Alliance Service Control Human Business Performance Management Campaign Management Monitor and Resource Channel Asset & Managemen Manage Managemen Liability t Product t Managemen Managemen Management Operational t t Manual Control Dealer Management Advisor/ Claims Trading End - Quality Management Intermediary End - customer processing Tax Management Logistics Management Consumer Contact Administratio marketing Sales Advisor/ Servicing Contract & n Product Change Management Intermediar Policy Setup Developmen Inforce y Setup Campaign Intellectual Property t Funds Processing Regulatory Execution Management Customer Reporting Conservation Execution and Profile Contract (S)TP Training Wholesales Administratio General Intelligent n Ledger Council Routing Sales Product Profile Services Contact Support Fees & Implementatio Repository Systems & Check Commission n Facilities Correspondenc Processing s Helpdesk e Knowledge & Learning Accounting & General Ledger Mechanical/ Electrical Design Plant Operations Inventory Management Lease Management Parts Management The Value Chain Administration Administration Administration Administration Asset Mgmt & Asset Mgmt & Development Development Management Management Customer Customer Business Business Marketing Marketing Business Business Product Product Sales & Sales & Channel Channel Service Service Contract Contract Finance Finance New New Business In-vehicle System Design Activity Level Execute Building/Facilities & Equipment Planning Accounting Manufacturing Operations Transportation Management Order Management Vehicle Service Business Analysis & Distribution &Finance Planning Planning Planning Planning Refinement Planning Financial Cost Management Process Design Alliance Service Control Human Management Campaign Management Monitor and Resource Channel Asset & Managemen Manage Managemen Liability Product t Managemen Managemen Management Operational t t Manual Control Maintenance Management Advisor/ Claims Trading End - Intermediary End - customer processing Consumer Contact Administratio marketing Sales Procurement Customer Relationship Management End-of-Life Vehicle Advisor/ Servicing Contract & n Product IT Systems & Operations Intermediar Policy Setup Developmen Inforce Tool Design & Build y Setup Campaign Funds Processing Regulatory Execution Management Customer Reporting Conservation Execution and Profile Contract (S)TP Training Wholesales Administratio General Intelligent n Ledger Council Routing Sales Product Profile Services Contact Support Fees & Implementatio Repository Systems & Check Commission n Facilities Correspondenc Processing s Helpdesk e IBM analyzed the business impact of a Service Oriented Architecture, through the use of CBM Business Component “Heat Maps” Strategic Filters Goal: Reduce time-to-market • Investigate critical components for new services (bv. Electronic Ticketing) Combining of lenses led to: • Detailed insight • Prioritized ‘hot’ components • Basis for Service Model NSComponent Business Model Goal: Reduce process elapse time • Investigate process bottlenecks • Map process bottlenecks on CBM Goal: Reduce maintenance costs • Map maintenance costs of IT applications and interfaces on CBM

37. A Business Component is a logical view of part of an enterprise that includes functions, resources, people, technology necessary to deliver business value • Business component • A logical view of a part of an enterprise • Has the potential to operate independently (even as part of another company) • Has discrete boundaries, defined by the business services that it offers and uses • Includes the resources, people, technology and know-how necessary to deliver some value • Viewed as a ‘black box’ in that the users don’t need to see or be aware of the business activities that are inside • Characterized by attributes, such as cost, revenue, importance to the business, etc. • Business services • are goods or services that a business component offers to other business components and/or to external parties Note: A Business Component need not correspond to any existing organizational structure. Component Name Market Segment Planning Description To analyze markets and derive targets Services Offered Services Used “In the CBM view, an enterprise is simply a collection of business components that are networked together”

38. A business process can be represented as collaboration among components. They use each others services. • Improvements efforts are focused at the level of the component —the strategic capabilities that enable them and the relationships between components, rather than the detailed activities inside — in fact, each component is essentially a “black box”

39. Шаг 2. Построение сервисно-ориентированной модели

40. SOMA is … • Service-Oriented Modeling and Architecture (SOMA) is a modeling and design method aimed at enabling target business processes through the identification, specification, and realization of business-aligned services that form the Service-Oriented Architecture (SOA) foundation. • The SOMA method provides in-depth guidance on how to move from the business models created through the IBM Component Business Modeling (CBM) or similar business analysis techniques, to the IT models required by an SOA. • SOMA leverages the IBM Global Services method (The Method) execution models, work product descriptions (WPDs) and techniques.

41. Flexible Business Composable Processes (IBM Component Business Modeling) Transformation Business Process Outsourcing Mergers, Acquisitions, and Divestitures Requires SOMA Flexible IT On Demand Operating Environment Composable Services (SOA) Services Oriented Architecture (SOA) Development Infrastructure Management Software Development Infrastructure Management Integration Flexible Business Requires Flexible IT

42. << Input from: Business Componentization /Analysis >> SOMA <<Output to: SOA Implementation >> SOMA Links Business Intent and IT Implementation • SOMA gets inputs from business componentization and analysis activities, and produces outputs necessary for SOA implementation. • The analysis and modeling performed during SOMA is technology and product agnostic, but establishes a context for making technology and product specific decisionsin later phases of the lifecycle.

43. <<Object>> <<Object>> <<Object>> SOA Modeling Constructs Business Processes (Flows) Services Atomic and Composite Service Components SOMA was created to specifically address modeling (analysis, identification, and specification) of all three constructs.

44. <<component>> << Input from: Business Componentization / Analysis >> DialogueControl <<component>> <<component>> SecurityProcessing AccountProcessing <<component>> AccountMgr <<component>> <<component>> RelationalDBMS ApplicationServer <<component>> STEP 1 STEP 2 STEP 3 STEP 4 STEP 5 STEP 6 SecurityMgr Architecture Vision /Planning Insight Investment SOMA IT Infrastructure Assessment Interpret Business Strategy Business Process Analysis Opportunities Definition Define Business Component Model Investment Roadmap Application Systems Analysis Service Portfolio Service Hierarchy (Core) System to Business Component Overlay Leading Business Practices Business Strategy Summary List of Opportunities and Recommendations [Rationalization] Project Prioritization Criteria Component Business Model with Components and Services Description Service Exposure Systems and Information Shortfall Assessment Goals, [ KPI’s Metrics] Multi- Generational Investment Plan As-Is Level 1 Process Model (within BC) Service Dependencies Business Component Collaborations Service Model ARC 101 Architecture Overview Diagram Service Composition Elements of Current IT Environment Level 1 As-Is Process State Assessment Service NFRs “Heat” Map Hygiene Factors [NFR] Level 1 to-beBusiness Process Service Messages Realization Decisions Process Gap Analysis Service Component Model ARC119 Non-Functional Requirements State Management Decisions << Output to: SOA Implementation >> Business Componentization Provides Essential SOMA Inputs Note: Although CBM inputs are depicted, SOMA can be used with other business analysis techniques.

45. Service Consumer << Input from: Business Componentization/Analysis >> JService Portlet WSRP B2B Other consumers Identification of Candidate Services and Flows business processes process choreography Service Provider Specification of Services, Components, and Flows Integration (Enterprise Service Bus Approach) services atomic and composite QoS, Security, Management, and Monitoring Infrastructure Service Data Architecture and Business Intelligence Realization Decisions service components Custom Application OO Application operational systems Packaged Application << Output to: SOA Implementation >> Composite Service Atomic Service Registry SOMA Activities Are Grouped into Three Major Steps At the heart of SOMA is the identification and specification of services, components, and flows.

46. Description SOMA Step Service Model • Candidate services discovered during SOMA service identification activities Domain Decomposition Goal-Service Modeling Existing Asset Analysis • Candidate services organized using a business significant categorization scheme to make evaluation more manageable Domain Decomposition Goal-Service Modeling Existing Asset Analysis Service Portfolio Identification Service Hierarchy Service Specification:: Service Litmus Test Service Specification:: Exposure Decisions • Decisions of why a given candidate service or group of services was exposed Service Exposure Service Dependencies • Dependencies between services in the model Service Specification:: Service Dependencies Specification Service Composition Service Specification:: Service Composition Service Specification:: Flow • Choreography of services to form a composite service Service NFRs Service Messages Service Specification:: Service Non-Functional Requirements • Non-functional requirements of the service State Management Realization Service Specification:: Service Message Specification • Messages that are exchanged between service consumer and service provider Realization Decisions Service Specification:: State Management Decisions • State management architectural decisions • Architectural decisions about service realization, such as buy, build, and subscribe Service and Component Realization Decisions The Service Model Captures Information about Services

47. Governance Startup Selection of Solution Templates, Method Adoption Domain Decomposition Existing Asset Analysis Goal-Service Modeling Identification Component Flow Specification Service Flow Specification Subsystem Analysis Service Specification Specification Component Specification Information Specification Message & Event Specification Realization Decisions Realization Technical Feasibility Exploration Detail SOA Solution Reference Architecture Solution Template & Pattern Selection and Instantiation Build/Assembly Assembly Integration Generation Implementation Construction Unit Testing Integration Testing User Acceptance Testing Testing Deployment (Packaging/Provisioning) Deployment Close Monitoring & Management Governance SOMA 3.1 Identificationof candidate services and flows, existing assets Specificationof services to be exposed, flows, and components (for realization of services) Arrows signify incremental iteration RealizationCapture realization decisions (concurrently with first two phases), explore feasibility of realization scenarios, instantiate SOA Reference Architecture ImplementationImplement service components and services Deployment Package and provision

48. Service Litmus Tests Universal (out-of-the-box) Business Alignment Composability Externalized Service Description Redundancy Elimination/Reusability Feasibility of Implementation Business Entity based Services (for Information Services only) Custom Client/Project Defined SLTs Service Service Service Service Apply SLTs (Standard and Custom) Apply Priority, Weight & Calculate Service Rating for each litmus test Make exposure decisions Service Service Service Litmus Tests (SLTs) Are Gating Criteria Used to Determine If a Candidate Service Should Be Exposed Candidate Services Determine Exposure Scope Exposed Services Exposure Scope Department/Division Line-of- Business Enterprise Eco-system

49. Шаг 3. Внедрение сервисно-ориентированной модели

50. IBM tools to implement different components of SOA