1、SOMA Workshop SOMA Fundamental Concepts and Overview,2,Agenda,SOA Recap SOMA Overview SOMA Introduction and Context Recap of Migration from 2.4 to 3.1 SOMA 3.1 Features Whats New SOMA 3.1 Method Structure SOMA Disciplines SOMA Delivery Processes SOMA Capability Patterns SOMA Solution Templates Busin
2、ess As Usual Activities SOMA Phases and Work Products SOMA Tooling SOMA Resources,3,Objectives,After completion of this section, you should be able to: SOA Recap Define SOA and Services Discuss objectives of service-oriented modeling SOMA Overview Describe why SOMA is needed Describe how SOMA levera
3、ges IBM SOA Solution Stack Describe how SOMA is related to IBMs SOA offerings Discuss SOMA context with respect to other IBM methods Discuss SOMA 3.1 new features Discuss SOMA 3.1 method structure Describe usages of disciplines, delivery processes, capability patterns, and solution templates Discuss
4、 role of business-as-usual activities in SOMA Describe SOMA phases and key work products Describe SOMA-ME Discuss additional resources on SOMA available to practitioners,4,SOA is Different Things to Different People.,“There are different views of an SOA all requiring design and development”,A set of
5、 services that a business wants to expose/provide to their customers and partners, or other portions of the organization,Business,An architectural style which relates service providers and consumers through a set of service descriptions (interfaces) and policies A set of architectural principles to
6、be used in this relation, patterns, principles 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 patterns, standards, tools, and technolo
7、gies such as Web Services,Implementation,Business analyst,SOA Architect,SOA Architect,SOA Developer, Tester, Composer,SOA involves different aspects for different roles,5,Service-Oriented Architecture Layers and Realization,Service-Oriented Architecture is based on a layered model of “components”, “
8、services”, and “processes”,The SOA services layer can be realized leveraging the Web Services open standard,Data Architecture and Business Intelligence,QoS, Security, Management, and Monitoring Infrastructure Service,Integration (Enterprise Service Bus Approach),consumers,business processes process
9、choreography,services atomic and composite,service components,operational systems,Service Consumer,Service Provider,AJAX,Portlets,WSRP,B2B,Other,OO Application,Custom Application,Packaged Application,Governance,6,6,A Service-Oriented Architecture is an enterprise-scale IT architecture for invoking a
10、nd linking resources as needed (on demand). These resources are represented as business(-aligned) services which can participate and be composed into applications participating in many levels of scope: a value-net, enterprise, or line of business to fulfill business needs. The primary structuring el
11、ement for SOA-based applications is the service; a business capability accessible through a specific architectural style, as opposed to subsystems, systems, or components.,SOA Defined,7,Services Defined,Business Perspective A Service is a well defined, encapsulated, re-usable, business-aligned capab
12、ility. A Service is fully defined via a Service Description A Service Operation is the elementary part of a Service and specifies the associated inputs, purpose (function, duty or obligations), outputs (artefacts, products, outcomes or deliverables) A Service Description is a published document or a
13、rtefact which outlines the overall objective of the Service, inputs, purpose (function, duty or obligations), outputs (artefacts, products, outcomes or deliverables), scope, responsibility, governance, sustainability (provision period, maintenance and repair), and qualities of provision of a Service
14、IT Perspective A service is a discoverable, invokable software resource having a service description/interface and configurable using policies The service description is available for searching, binding, and invocation by a service consumer The service description implementation is realized through
15、a service provider who delivers quality of service requirements for the service consumer,SOMA Tip,8,Operation is an IT term used to designate and invoke an exposed service,Functional Area,Service,Service,WSDL,Service Name,Port Type Name,Operation Name,Operation Name,IT Implementation,Business/Consul
16、ting,Operation Name,Reserve Vehicle,Get Rates,Make Reservation,Operation Name,Operation Name,Service,Operation Name,Service Operation,Service Operation,Service,Service Operation,exposed,exposed,exposed,Service Operation,exposed,exposed,exposed,exposed,Operation Name,Operation Name,Operation Name,exp
17、osed,exposed,SOMA Tip,Example,9,9,“40% of IT spending is on integration.” IDC,“Every $1 for software = $7 to $9 on integration.” Gartner,Architecture and Applications: Disentangling The “Big Ball of Yarn”,Separate layers and Introduce a layer of business services that decouples providers and consume
18、rs - no longer tight coupling,Gradual And partial migration,10,Service-Oriented Modeling Objectives,Just as OOAD is necessary to define object-oriented systems and as component-based development is used to define component-based architectures, service-oriented modeling is necessary to define a servi
19、ce-oriented architecture. While SOA builds on well-established software architecture principles (for example, information hiding, modularization, and separation of concerns), it also adds new concepts and aspects. Thus, service-oriented modeling needs additional techniques for defining and using the
20、se new aspects.,composite,atomic,Typically fine-grained,Typically hard-wired,Flexible, agile, replaceable,11,Services, Service Components and Flows Are SOA Modeling Constructs,SOMA was created to specifically address modeling (analysis, identification, specification, realization, implementation) of
21、all three constructs and associated Information, Composition, Rules & Policies, Context, Events.,Services the main structuring element required by a service consumer, provided by the service provider. Offers functionality and quality of service, both of which are externalized within service descript
22、ions/policy. Services could be atomic or composite,Business Processes represent the flows of activities required to complete a business process. They are compositions of services targeted to achieve business goals,Components that realize not only the functionality of the services they expose but als
23、o ensure their quality of service (the QoS advertised by the Service provider implementing (“realizing”) the services,12,Agenda,SOA Recap SOMA Overview SOMA Introduction and Context Recap of Migration from 2.4 to 3.1 SOMA 3.1 Features Whats New SOMA 3.1 Method Structure SOMA Disciplines SOMA Deliver
24、y Processes SOMA Capability Patterns SOMA Solution Templates Business As Usual Activities SOMA Phases and Work Products SOMA Tooling SOMA Resources,13,Why is there a specific need for Service-Oriented Modeling to build a Service-oriented Architecture?,Models and methods used in the past do not adequ
25、ately cover the abstractions, tasks, workproducts, new roles required for supporting service-oriented solution development. A service-oriented modeling method should have the following characteristics: Focus on services as the basic modeling construct Support services, components and flows Coverage
26、and convergence of business (processes/goals) and IT (components) aspects of a solution Full lifecycle method support starting with solution outline and including the build cycle Guidance on service identification, service specification, realization, and implementation including guidance on leveragi
27、ng existing assets for an SOA as well as custom development,14,SOMA Introduction,Service-Oriented Modeling and Architecture (SOMA) filled the gap in the industry for SOA Methods. It consists of a prescriptive tasks that produce SOA-related artifacts by roles within the lifecycle. SOMA is an end-to e
28、nd SOA development method aimed at enabling target business processes through the identification, specification, realization, implementation, and deployment of business-aligned services that form the Service-Oriented Architecture (SOA) foundation. The SOMA method provides in-depth guidance on how to
29、 move from the business models created through business analysis, such as the output from the IBM Component Business Modeling (CBM), to the IT models required by an SOA. SOMA is flexible and extensible through solution templates which include specific activities and work products, and allow for the
30、fact that SOA solutions can vary greatly and often require a hybrid approach to address client requirements in terms of implementation options (packaged applications, custom development, usage of legacy systems, composite business services/CBS, and so on),15,IBMs SOMA Methodology Provides In-depth G
31、uidance on How to Move from Business Strategy and Analysis to a Successful SOA Implementation,SOA Entry Points,SOA Industry Roadmaps,Regardless of starting point, SOMA allows for the rapid design, development, deployment, and management of a service-oriented architecture,Process,Information,Reuse,Co
32、nnectivity,People,16,SOMA 3.1 is IBMs End-to-End Method for building SOA Solutions Identification, Specification, Realization, and Implementation of Services (Including Information Services), Components and Flows (Processes/Composition),Integrate your clients method and governance processes into SOM
33、A Leverage the outputs of over a hundred SOMA engagements worldwide across industries, with over 3,000 practitioners trained in SOMA basics. SOMA is available in commercial and internal versions: the commercial version, RUP/SOMA 2.4 (leveraging RUP) and SOMA 3.x (leveraging GS Method/ UMF). SOMA int
34、egrates with other assets such as CBM, SIMM, SOA Reference Architecture, etc. to support SOA engagements (TP outlining this is in progress),17,SOMA is all about the identification, specification, realization, implementation, and deployment of services, components, and flows.,The Role of SOMA in SOA
35、Development Is to Provide a Prescriptive Method Necessary to Create an SOA,Data Architecture and Business Intelligence,Integration (Enterprise Service Bus Approach),QoS Layer( Security, Management, and Monitoring Infrastructure Service),Governance,18,SOMA Method Context: SOMA 3.1 Is an End-to-End Me
36、thod,RUP,Solution Startup (WWPMM),Release,Deploy,Build Cycle,Micro Design,Macro Design,Solution Close (WWPMM),Solution Outline,Solution Startup (WWPMM),Assemble,Solution Close (WWPMM),Model,Deploy,GS Method,19,The SOA Strategy How do I get started in SOA? The SOA Diagnostic Ive started with SOA, how
37、 am I doing? What can I do better? Business Process Management on SOA I need to transform my business processes before I SOA-enable them how do I start? The SOA Implementation Planning There is a specific business area I want to improve using SOA how should I approach it? SOA Lifecycle Services Ive
38、done the preliminary planning work, now Im ready to develop and sustain Integration Integrating my systems as per the SOA Strategy. Next Steps Where are we going from here?,IBM SOA Offering Overview What Are the SOA Offerings?,SOMA is an important ingredient to many of the SOA offerings,20,IBM SOA A
39、ssets and Models Support Multiple Types of Client Engagements,SOMA,SOMA,SOMA,SOMA,SIMM,CBM,21,SOMA has evolved based on field experiences and client feedbacks from its initial release SOMA 1.0 to its current release SOMA 3.1,SOMA 1.0 - 2002,SOMA 2.x - 2004,SOMA 3.0 - 2006,SOMA 3.1 - 2007,22,SOMA 3.1
40、 Features Whats New in SOMA 3.1?,SOMA 3.1 is an end-to-end method for SOA solutions to identify, specify, realize, implement (build, assembly, and test), and deploy services. SOMA 3.1 introduces eight new disciplines. SOMA 3.1 introduces many new capability patterns. Solution templates and patterns
41、are significant additions to the flexibility and extension mechanisms for SOMA. SOA solutions often require a hybrid approach, combining various solution templates in order to craft a specific solution for a client. Each of these approaches or solution templates requires a specific set of techniques
42、, method tasks, work products, and roles that are often uniquely integrated into an underlying technology or toolset. For example, Composite Business Services are often tied to the WebSphere Business Services fabric although building composite applications is also possible through the use of WebSphe
43、re Process Server, WebSphere Integration Developer, or other platforms such as SAP enterprise service architecture.,23,SOMA Migration Path from v2.4 to v3.1,SOMA has gone through a series of enhancements and refinements from version 2.4 to 3.1 release: SOMA 2.4 Established the core SOMA techniques w
44、ithin the SOMA Method, including the identification, specification, and realization of services, the components implementing those services, and the flows that orchestrate the services into composite applications SOMA 3.0 = SOMA 2.4 + Extended and enhanced the core concepts of SOMA, expanded realiza
45、tion phase, and added implementation and deployment phases Added additional eight new disciplines Added more capability patterns Added solution templates and patterns to provide flexibility and extensibility Incorporated business-as-usual activities only so far to support services development lifecy
46、cle SOMA 3.1 = SOMA 3.0 + Incorporated the key aspects of overall SOA solution delivery such as requirements gathering, user interface design and development, environment and operations, and project management for overall SOA solution Integrated business-as-usual (BAU) activities/tasks from other IB
47、M methods such as Custom Application Development, IBM Portal Services, WWPMM, e-Business etc. to support these aspects of overall SOA solution,24,SOMA 3.1 Method Building Blocks,Task,Role,Work Product,Building blocks for SOMA Method are: Task Role Work Product A Task is performed by Role (s). To per
48、form a Task one or more work products are needed. A Task generates one or more output work products. Tasks are categorized by Discipline.,input work product *,* output work product,executes,25,SOMA 3.1 Method Structure,26,SOMA 3.1 Method Concepts,Discipline A Discipline is a collection of tasks that
49、 are related to a major area of concern. Separating these tasks into separate disciplines makes the tasks easier to comprehend. Capability Pattern A Capability Pattern is a special process that describes a reusable cluster of tasks in common process areas. Capability Patterns express and communicate
50、 process knowledge for a key area of interest such as a discipline and can be directly used by a process practitioner to guide his work. Capability Patterns are also used as building blocks to assemble Delivery processes or larger capability patterns ensuring optimal reuse and application of the key practices they express. Delivery Process Describes a complete and integrated end-to-end approach for performing a specific type of development project.,
