Advancing the Business/IT linkage with SOA Governance and Service Lifecycle Management May 2007
Governance is critical to overall SOA Success Technical Changes Key Enabling Tools  Enhanced WebSphere Registry & Reposito...
What’s new in SOA Governance and Service Lifecycle Management to support Business and IT alignment   <ul><li>Agenda  </li>...
SOA Governance Lifecycle drives business/IT alignment at the beginning of SOA deployment <ul><li>Design the Governance App...
SOA Governance Model  Skills Infrastructure & Tools Principles, Policies, Standards & Procedures Implemented by Monitors &...
<ul><li>Customer tested SOA Governance Method </li></ul><ul><li>Leverages existing governance model   </li></ul><ul><li>De...
Service Domain Ownership Model helps business and IT cooperation   <ul><li>Service Ownership is one of the most important ...
<ul><li>Important yet difficult processes to implement for SOA. </li></ul><ul><li>Drives a number of SOA benefits and make...
SOA Governance and Management Method vision of success includes the Organizational Change and Change Management  Transitio...
A Governing Body is needed to manage shared services across the business/IT organization  Define High Value Business Servi...
Center of Excellence (CoE) can improve the opportunity for SOA implementation success Assist and support your decision to ...
IBM offers 6 key service offerings to assist in SOA implementations. All supported by SOA Governance  <ul><li>Helps a C-le...
Minimize time and effort to get started  Accelerate acceptance of new SOA paradigm  Create environment for SOA success wit...
Each phase of the SOA Lifecycle has different   challenges   requiring different governance capability Creating the same s...
Governance is supported by a federated set of capabilities to meet the challenges of service lifecycle management  Service...
Successful SOA service strategy requires a deployment tool to manage and control services at runtime  Encourage Reuse Find...
Reduce huge maintenance costs by enabling a flexible infrastructure Address the IT pain point of poor reuse and duplicatio...
Service Development and Delivery Management focuses on creation and updating services as assets   SOA Lifecycle Infrastruc...
Development and delivery asset management tracks IT assets needed to implement an SOA  <ul><li>Uses Reusable Asset Specifi...
An Asset Manager supports development and delivery management of services and composite business services <ul><li>Rational...
Registries and Repositories can work separately or federated together based on the business/IT SOA requirements   <ul><li>...
Development-time Deployed / Run-time Federated  Search & Publish ClearQuest ClearCase Software Architect Generic Client (....
<ul><li>Unify disparate development teams </li></ul><ul><li>Enable reuse and eliminate rework </li></ul><ul><li>Accelerate...
Service Lifecycle Management tools enhance each team members ability to be successful Discover services for reuse / publis...
Key Takeaways <ul><li>Adopt an end-to-end framework to support a long-term approach toward service orientation </li></ul><...
Governance should not an &quot;afterthought&quot;; it matters because without it success is not achievable <ul><li>Focus o...
Upcoming SlideShare
Loading in...5
×

SOA Governance and SLM.ppt

2,659

Published on

1 Comment
0 Likes
Statistics
Notes
  • Be the first to like this

No Downloads
Views
Total Views
2,659
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
235
Comments
1
Likes
0
Embeds 0
No embeds

No notes for slide
  • Main Point: SOA Governance and Service Lifecycle Management will be a key requirement for successful SOA Implementations and good business/IT alignment. This presentation continues the advancement IBM is making in improving customers ability to be successful with new services and enabling tools.
  • Main point : Governance is critical to the success of your projects. There are two elements of governance to consider: the technical side whereby you have the infrastructure to encourage the re-use of deployed services, as well as the orgnizational aspect by which your organisation develops and fosters a culture of reuse. Techincal Changes Encourage Reuse Enhance Connectivity Help optimize service performance Enable Governance Technology working together: Service Development-Rational asset manager Service Management- Tivoli CCMDB Service Deployment-WSRR Cultural Changes Re-use top of mind Design for longevity Enforce policies
  • Main Point: Focus initially on the Organizational Change and Services aspects of SOA Governance and then discuss the new and enhanced enabling tools
  • Important Points On This Slide: SOA governance should be implemented within a lifecycle to take advantage of iterative improvement. Our lifecycle has four main phases: plan (assess the need for governance and gather inputs), define (define the governance model), enable (implement the governance model), and measure (use defined KPI’s to measure the governance model’s effectiveness) Speaker Notes: This slide shows the SOA Foundation and the various phases of the service lifecycle – model, assemble, deploy and manage. We are not going to go too deep into the service lifecycle, since you have seen this already. &lt;NOTE – a pre-req for the customer being briefed on SOA governance is for them to be briefed on SOA where they will get their fill of the lifecycle.&gt; The SOA foundation shows governance as the bottom layer and this layer supports all phases of the lifecycle. This is important point – an effective governance model will govern ALL phases of the service lifecycle and need to transcend all phases of the services lifecycle. Each phase will have a series of quality gates of checkpoints that the service needs to comply with before it graduates to the next phase of the lifecycle. IBM has also defined the lifecycle for SOA governance. Similar to the lifecycle of a service, the lifecycle for SOA governance has 4 main phases of plan, define, enable, and measure. Also, like the services lifecycle, the SOA governance lifecycle is iterative. We will now go into the phases and describe their significance. Plan – The plan phase is used to asses the need for governance. It is in this phase where you understand the organizational context that is crucial to defining a governance model that will be accepted by the enterprise. In this phase, you examine the following things: What is the current operational model? Does the enterprise have an IT governance model? What are the current IT governance mechanisms (ie Architectural Review Board)? How does the company make IT decisions? How do those decisions get disseminated across the org? What were some of the enterprise wide initiatives that the company has taken on and why did they succeed of fail? How effective is the current IT governance model? What needs to change? What are the current IT standards, best practices, policies, and principles? Define – In the define phase, you define the governance model. In this phase, you define all 5 elements of the governance model that we covered earlier (see slide 4). When defining the model, you will need to define such things as the organizational mechanisms, the decision rights, the metrics to measure the effectiveness of the governance model, what key processes are you going to govern (ie versioning process, testing process, etc.), business domains, owners to those domains, etc. You will decide if you want to establish a CoE in conjunction with your governance model. You will also define an education, mentoring, communication and transition plan to help map out the implementation of the governance model. Enable – In the enable phase, you implement the governance model as outlined in the transition plan. Everything that you just defined in the last phase will need to be enabled. The definition of a transition plan is crucial here since the transition plan should give you the plan of attack for implementing these various elements and phase this work in such a way that hedges the greatest amount of risk. Measure – Finally the measure phase answers the question of how effective is the governance model? Given the key metrics you defined in the define phase, the measure phase will aggregate data based on those metrics and understand if the governance initiative is effectively meeting its objectives.
  • A key to successful SOA and SOA Governance implementations is a focus on organizational change and change management. Moving to SOA creates a significantly new environment for both Business and IT, and there will need to be a focus on the impacts of this new environment. Going with the overall SOA Governance plan there will need to be a group supporting an overall organization change plan. In IBM, that group is called the Center of Excellence.
  • COE Offering from IBM Increase your opportunity for success Typical CoE Activities and Responsibilities SOA Architecture Workshop Create the reference architecture and project plans to implement the planned architectural change. SOA Architecture Review Workshop Review existing architectural artifacts for compliance with existing IBM best practices and industry trends Define and Document Infrastructure Architecture for your development, QAT and production environment Environment Installation and Configuration Evaluate your environment to ensure only the correct technologies are implemented for efficiency and project focus Install and Configure the required technologies Skills Transfer and Best Practices Provide mentoring and best practices to enable the client  
  • IBM recommends creating a Center of Excellence. A SOA Center for Excellence (CoE) combines the expertise and assets from across IBM. It helps clients who have made an enterprise-wide commitment to architectural change speed the adoption of that change, mitigate risk, and align the transformation with industry best practices. The SOA CoE accomplishes these goals by leveraging assets and best-practices developed from experience across IBM with similar enterprise transformations. In essence, the CoE is designed to supply a set of services to assist in implementing an SOA Center of Excellence to support the SOA Governance customization and implementation for a customer. The capabilities that a CoE can supply is: Assist in customizing the SOA Governance and Management Method for the unique client environment. Conduct SOA Architecture workshops and review a clients current Service Oriented Architecture IBM can also supply you with training and mentoring
  • Main Point: IBM continues to enhance SOA Governance focused capability. SOA Governance will be key to getting started and being successful with SOA.
  • Main Point. At each phase of the SOA Lifecycle there are different challenges that require different governance capabilities. IBM has different approaches and enabling tools at each phase.
  • Main Point: IBM’s Registry/Repository Strategy incorporates the concept of federation, since it is not possible to have a single repository that will be able to handle all the functionality needed across Service Lifecycle Management.
  • Main point: Introducing the WebSphere Service Registry and Repository The WebSphere Service Registry and Repository is a integrated service metadata repository that helps you govern and manages services through the service lifecycle. It enables you to store, access, and manage information about the services (commonly referred to as service metadata) in your SOA. This information is used to select, invoke, govern, and reuse services as part of a successful and dynamic SOA. B y promoting visibility, consistency, and reducing redundancy in SOA and by managing the service lifecycle, WebSphere Service Registry and Repository helps you get the most business value from SOA. Definition (FYI) Service metadata is anything used to talk about services - such as descriptions, owner etc. Artifacts are files such as XML docs or XSDs or WSDL docs.  Metadata is a generic concept, ie information about an artifact: a service, a wsdl, an xml schema, a policy etc. WebSphere Service Registry and Repository includes: • A service registry that contains information about services, such as the service interfaces, its operations, and parameters • A metadata repository that has the robust framework and extensibility to suit the diverse nature of service usage Key Features 1) The Publish and Find Capabilities helps improve visibility, reduce redundancy, and encourage reuse The WSRR allows you to publish and find services and related metadata through all stages of the SOA lifecycle It also integrates with other registries to allow publish and find with other standards registries 2) The WSRR enriches SOA runtime interactions to add dynamism to SOA The WSRR enables dynamic and efficient service interactions at runtime by… Optimizing access to service metadata Managing service policies This capability is supported by CICS and key WebSphere products such as the ESB 3) The WSRR also enables SOA governance to help maximize the business value of SOA Managing service lifecycle states with guards for state transitions Enables impact analysis to determine the impact of service introduction, deletion or alteration Also provides for roles based access and versioning
  • Reduce software development and operational costs by facilitating the reuse of all types of software development related assets, including service assets used in Service Oriented Architecture (SOA) development. Improve quality by facilitating the reuse of approved &amp; proven assets. (Re)using requirements, design, construction, test, and deployment assets allows customers to leverage software investments in packaged, existing, and new applications. Integrated with other Rational and SWG tools, such as IBM Rational ClearCase, IBM Rational ClearQuest and IBM Rational’s Architecture Management Solutions, including IBM Rational Application Developer and IBM Rational Software Architect. In addition, IBM Rational Asset Manager, a development-time asset repository, is closely integrated with IBM WebSphere Service Registry and Repository for management of runtime SOA assets.
  • In understanding the SOA Governance environment, there are two components that need to be taken into consideration. The two components of the SOA Governance environment are the development of the SOA Governance processes and the Service Lifecycle Management using the governance process. Once the Governance decision making has been established, it is then about executing (automating) the process and managing and monitoring the results. In the case there are two types of results. The services that come out of the development process and the decisions that are made related to the service. The SOA Governance processes are monitored via the SOA Governance framework, while the released services are managed via the Manage component of the SOA Lifecycle. The first is the SOA Governance framework. Plan, Define, Enable and Measure are all about establishing the end-to-end SOA Governance processes. This will involve Vertical Management Decision Making processes as well as Horizontal SOA Lifecycle Management processes. The SOA Lifecycle then has the SOA Governance as the driver for the overall process. How decisions are made and the policies for the SOA Lifecycle are developed in SOA Governance. The Service Lifecycle is only one of the processes governed, but is the key process for the development and management of Services. Services are created with the Model, Assemble Deploy sections of the SOA Lifecycle, and then once deployed, they are controlled in the Manage section of the SOA Lifecycle. The overall process is a closed loop, since Services can be updated during the life, so they would go back into the Model phase again. The Service Development and Delivery Management works with the Model, Assemble and Deploy components to create or update and deploy services. Governance is involved in making sure that the governance process is enforced when services are developed and/or delivered. Once a service has been deployed and is in the Manage phase, governance is about monitoring the operational policies established by the SOA Governance and Management Method.
  • Main Point: RAM is a development time asset management repository, that supports the OMG standard of RAS An asset is a collection of related artifacts that provide a solution to a problem for a specific context. The contexts describe the intended environment the asset is expecting to be applied within. For example, development context, deployment context, business context, etc.. An asset may be relevant to one or more contexts. Asset artifacts are workproducts from the software development process (e.g., requirements and use cases, design models, component specifications, components, source code, test cases, test drivers, test data, etc.). In other words, an asset artifact may be a business process model, data model, source code, binary file, document, script, etc. Reduces operational costs by ensuring assets confirm with IT middleware and operational facilities for IT organizations. For systems developer ensures the same asset is compatible with products and their components and by reducing the number of variations of components that provide similar capabilities in different products.
  • Accessing service asset details like what artifacts where used to create the service If I do a search there will be a combined search results that don’t duplicate results. One asset per service because otherwise you could end up with multiple services results one from dev, test &amp; production. Coordination is key to benefits of 2 repositories.
  • Not every deployed service is a reusable asset and not every reusable asset is a deployed service Managing development of assets vs. operational metadata for services. Each provides a unique set of functionality. For example IBM Rational has systems development customers like Bosch who are not implementing services but are reusing other software components and want to take advantage of the unique capabilities offered by Rational Asset Manager. There are some customers who aren’t reusing components but are reusing services and want to take advantages of the unique runtime service mediation capabilities in WSRR. Confusion sometimes arises around when to use these two products together when service is the type of component that a customer wants to reuse. The reason is because there is a small set of similar functionality around search, categorization, access control, metadata and workflow Although there is some overlapping functionality it applies to different use cases and content for each product. I’ll describe when these products have to interact later which should help understand the differences in their function. Other WSRR Key Functions Notify clients of changes Information about metadata service interaction endpoints Discover services and metadata from other registries Publish newly developed services and artifacts Asset Notifications can optionally occur when: An asset is submitted / updated Review state of an asset is changed Search subscriptions are also supported Notified periodically of search results
  • Reduce software development and operational costs by facilitating the reuse of all types of software development related assets, including service assets used in Service Oriented Architecture (SOA) development. Improve quality by facilitating the reuse of approved &amp; proven assets. (Re)using requirements, design, construction, test, and deployment assets allows customers to leverage software investments in packaged, existing, and new applications. Integrated with other Rational and SWG tools, such as IBM Rational ClearCase, IBM Rational ClearQuest and IBM Rational’s Architecture Management Solutions, including IBM Rational Application Developer and IBM Rational Software Architect. In addition, IBM Rational Asset Manager, a development-time asset repository, is closely integrated with IBM WebSphere Service Registry and Repository for management of runtime SOA assets.
  • Main Point: With the focus in SOA on Business/IT relationship, there are key roles in both the business group and the IT organization supplying the support for the business in every phase of the SOA Lifecycle. This is not just about testing. It is an iterative and continuous process that will be have to deal with services that may be a multiple levels of the lifecycle. In the model phase of the SOA Lifecycle, the business team, in the form of business executive, with business analyst or managers, develop the goals and objectives for the new or updated service. At the same time the IT Executive is working to establish the overall, end-to-end quality Management process, using the SOA Governance and Management method plug-in and the Tivoli Unified Process from Rational Method Composer. Once the functional and performance requirements are established in the Model phase they can go to Development to create using a number of Rational development tools. Going to Deploy, Rational has two new test tools to support SOA Quality Management. In production, during the Manage phase, the service is tracked and reported on with ITCAM This then becomes and iterative, continuous process for creating and updating services.
  • Main point: SOA Governance is not an &amp;quot;afterthought&amp;quot;; it matters because the success of your SOA projects depend on adhering to proven methods and best practices. SOA Governance is needed in this more complex SOA environment. Services are involved in both Business and IT across all the Lines of Business horizontally across the organization. With SOA Governance, it allows the business to obtain the expected benefits from service reuse across the LOBs. Governance is about risk management and maximizing control of the processes. In addition, with structured decision making it allows the teams to make decisions quicker and more effectively. A major part of governance is risk mitigation. With a good governance approach there is less risk and improved quality. With good governance, everyone understands their role and responsibility in the overall process. This allows the right people to make the right decisions at the right time. This allows for improved control and consistency. When everyone understands how the process works between all the involved business and IT organizations, it allows for much better teamwork. There is less arguing about who makes what decisions.
  • SOA Governance and SLM.ppt

    1. 1. Advancing the Business/IT linkage with SOA Governance and Service Lifecycle Management May 2007
    2. 2. Governance is critical to overall SOA Success Technical Changes Key Enabling Tools Enhanced WebSphere Registry & Repository New Rational Asset Manager Fostering a culture of reuse SOA Governance and Mgmt Method GBS SOA Services Cultural Changes * NEW! * NEW!
    3. 3. What’s new in SOA Governance and Service Lifecycle Management to support Business and IT alignment <ul><li>Agenda </li></ul><ul><li>SOA Governance and Management Method </li></ul><ul><li>SOA Center of Excellence and Services </li></ul><ul><li>SOA Governance Registry and Repository Strategy </li></ul><ul><li>Service and Asset Management </li></ul>
    4. 4. SOA Governance Lifecycle drives business/IT alignment at the beginning of SOA deployment <ul><li>Design the Governance Approach </li></ul><ul><ul><li>Define/modify governance processes </li></ul></ul><ul><ul><li>Design policies and enforcement mechanisms </li></ul></ul><ul><ul><li>Identify success factors, metrics </li></ul></ul><ul><ul><li>Identify owners and funding model </li></ul></ul><ul><ul><li>Charter/refine SOA Center of Excellence </li></ul></ul><ul><ul><li>Design governance IT infrastructure </li></ul></ul><ul><li>Put the Governance Model into Action </li></ul><ul><ul><li>Deploy governance mechanisms </li></ul></ul><ul><ul><li>Deploy governance IT infrastructure </li></ul></ul><ul><ul><li>Educate and deploy on expected behaviors and practices </li></ul></ul><ul><ul><li>Deploy policies </li></ul></ul><ul><li>Manage & Monitor the Governance Processes </li></ul><ul><ul><li>Monitor compliance with policies </li></ul></ul><ul><ul><li>Monitor compliance with governance arrangements </li></ul></ul><ul><ul><li>Monitor IT effectiveness metrics </li></ul></ul><ul><li>Scope the Governance Need </li></ul><ul><ul><li>Document and validate business strategy for SOA and IT </li></ul></ul><ul><ul><li>Assess current IT and SOA capabilities </li></ul></ul><ul><ul><li>Define/Refine SOA vision and strategy </li></ul></ul><ul><ul><li>Review current Governance capabilities and arrangements </li></ul></ul><ul><ul><li>Layout governance plan </li></ul></ul>
    5. 5. SOA Governance Model Skills Infrastructure & Tools Principles, Policies, Standards & Procedures Implemented by Monitors & Metrics Governance Mechanisms Managed by Monitored by SOA Vision Organizational Change Management Governed Processes Service Design Service Transition Service Strategy Service Operation SOA Strategy Service Modeling Service Design Service Testing Service Deployment Service Delivery Service Architecture Define Service Funding Security Management Service Assembly Service Domain Owners Event Management & Service Monitoring Service Support Supported by Communication Exception/Appeals Vitality Compliance
    6. 6. <ul><li>Customer tested SOA Governance Method </li></ul><ul><li>Leverages existing governance model </li></ul><ul><li>Detailed governance process guidance </li></ul><ul><li>Comprehensive framework and processes span lifecycle of SOA governance </li></ul><ul><li>Methodology to help clients establish SOA Centers of Excellence </li></ul>SOA Governance and Management Method aligns business and IT strategy for successful SOA implementation Determine the Governance Focus Plan Continuous SOA Governance Process Measurement & Improvement Define Enable Measure Define the SOA Governance Model Implement the SOA Governance Model Refine the SOA Governance Model Define and refine governance processes Define IT changes in SOA development Implement the transition plan Initiate SOA Org Changes Launch the SOA Center of Excellence Implement infrastructure for SOA Measure effectiveness governance processes Measure effectiveness of organization change Review and refine operational environment Define organizational change Tailor method for goals / environment Understand current Governance model Define scope of governance Identify ‘Reuse’ elements Define Metrics and Measures for success
    7. 7. Service Domain Ownership Model helps business and IT cooperation <ul><li>Service Ownership is one of the most important yet difficult processes to implement for SOA. </li></ul><ul><li>The Domain Ownership Model should align with the businesses structure but Political and Cultural issues increases the difficulty to adopt and implement. </li></ul><ul><li>Commitment throughout the organization but especially at higher levels in the organization will make this less difficult. </li></ul><ul><li>This process will make possible a number of SOA benefits and drive the adoption of other processes like the Funding Process which is closely linked to Domain Ownership </li></ul>Identify Service ( Domain ) Owners Business Model , Industry Model , SOMA , Service Domain Ownership Model Initial Creation Request for New or Restructured Domain ( s ) Determine Impacts on Service Domains and or Architecture Communicate Domain Ownership Decision Define Service Domain Structure & Scope Map to Domains & Determine Overlaps Appeal Assess and Nominate Owner Change of Ownership Impact Resolved by appropriate groups ( ARB , CoE , Governance Board ( s ) , etc .) Inputs No Yes Consolidate or Split ? Overlap Exists ? Impact Exists ? Yes No Yes Owner Approved by Stakeholders Yes Update SDOM Pass No No or Acceptable Service Domain Impacted ? Trigger Compliance & Vitality Check Unacceptable Fail Candidate List , Suitability Assessment Appeal to Steering Committee Process Exit Capture Governance Process Metrics & Harvest Reusable Assets T 1 T 2 T 4 T 3 T 5 G 1 G 2 G 3 G 4 G 5 G 6 G 8 I 1 I 2 A 1 A 2 A 3 Updated Service Domain Ownership Model Process Output O 1 Other Candidates Exist Appeal Owner Rejection No Yes G 7 LEGEND I = Input T = Task A = Assessment G = Governance Step O = Output P = Process S = Policy Define Service Focus Service Funding Service Identification Triggers No P 1 P 2 P 3
    8. 8. <ul><li>Important yet difficult processes to implement for SOA. </li></ul><ul><li>Drives a number of SOA benefits and make SOA adoption possible. </li></ul><ul><li>Diagram addresses service funding definition and the governance of a defined model, but not the funding model. </li></ul><ul><ul><li>Funding Model should address funding of initial projects but more importantly day to day funding of services, their use, maintenance, development and versioning. </li></ul></ul>Incentive to align is driven by the Define Service Funding Model Define Service Funding Candidate Services , SDOM , Current Funding Model , Business Goals and Drivers , SOA Strategy , Approved SOA Opportunities Decision to Implement SOA or Decision to change funding model Analyze Existing Funding Model Define To Be Funding Model Trigger Inputs Stakeholder Approval ? Yes Allocate Costs Based on Funding Model Project ( s ) Initiation or Funding Change Identified or Plan Cycle Start Align New Funding Model to SOA Objectives No Estimate Service TCO & Estimate Usage The funding model , Project Description , Project Plan , Approved SOA Opportunities , Exception Request Inputs Steering Committee Appproval Communicate Decision Yes No Capture Governance Process Metrics & Harvest Reusable Assets Process Exit Perform Portfolio Analysis Evaluate Reason For Rejection and ReRoute Compliance Pass Fail Identify Service Domain Owner if New Domain I 1 I 2 T 3 T 2 T 1 G 1 T 4 T 5 G 2 T 6 T 7 T 8 G 3 G 4 G 6 Compliance and Vitality G 5 LEGEND I = Input T = Task A = Assessment G = Governance Step O = Output P = Process S = Policy P 2 Service Domain Ownership Model P 2 Define Service Focus P 1 Service Specification Triggers P 2
    9. 9. SOA Governance and Management Method vision of success includes the Organizational Change and Change Management Transition State Target State Change Management Goals: “ Help ensure that people impacted by the changes…. <ul><li>Understand </li></ul><ul><li>Accept </li></ul><ul><li>Are Prepared for, and </li></ul><ul><li>Are Committed to </li></ul>The Change Management Pattern will: <ul><li>Mitigate risks with appropriate oversight & control </li></ul><ul><li>Increase reuse & buy-in promoting the use of Services </li></ul><ul><li>Speed Adoption of the Governance model enabling a successful implementation </li></ul><ul><li>Facilitate the achievement of program benefits </li></ul>the changes that will affect them.” Current State
    10. 10. A Governing Body is needed to manage shared services across the business/IT organization Define High Value Business Services Provide Architectural Authority Conduct Architecture Reviews and Workshops Measure and Track KPIs Provide Architecture Vitality & Thought Leadership Manage the Service Lifecycle Establish Decision Rights Provide Skills Transfer & Early Proof of Concepts Governing Body
    11. 11. Center of Excellence (CoE) can improve the opportunity for SOA implementation success Assist and support your decision to implement SOA and SOA governance Delivery: Enables successful delivery of your business strategy with establishment of technical resources. Customization: Assist in customization of SOA Governance Method to meet unique requirements <ul><li>Capabilities: </li></ul><ul><li>SOA Architecture Workshop </li></ul><ul><li>SOA Architecture Design and Customization </li></ul><ul><li>SOA Architecture Review </li></ul><ul><li>Software environment installation and configuration </li></ul><ul><li>Education and Skills Transfer </li></ul>Knowledge: A CoE serves to supply the expertise to the organization for SOA implementation and execution SOA on your terms and our expertise Governance Method supplies templates to create CoE Center of Excellence
    12. 12. IBM offers 6 key service offerings to assist in SOA implementations. All supported by SOA Governance <ul><li>Helps a C-level exec layout a complete SOA Strategy, Architecture and Roadmap to transformation organization and systems towards a service oriented model. </li></ul>SOA Strategy SOA Diagnostic SOA Implementation Planning SOA Design, Development, and Integration Services SOA Management Business Process Management Enabled by SOA SOA Governance <ul><li>Helps an organization ensure that the required processes, controls, responsibilities and activities are deployed to successfully manage SOA solutions </li></ul><ul><li>It is a discipline that enables effective management of core business processes across an organization . </li></ul><ul><li>Helps a Line of Business or Application Group define future business process, the high impact services and the corresponding solution architecture </li></ul><ul><li>The core implementation of an SOA solution. It is designed to be a follow-on from an early BPM or SOA planning phase. </li></ul><ul><li>For clients that have already started their SOA transformation but want IBM to evaluation how they are doing and make improvement recommendations. </li></ul>
    13. 13. Minimize time and effort to get started Accelerate acceptance of new SOA paradigm Create environment for SOA success with expertise and customized approach Getting started with SOA Governance is faster and easier with SOA Governance Method, a CoE and Services Use Proven Best Practices Approach Develop customized processes faster Improve Organization Change capability SOA requires not just technical, but organizational education supplied with SGMM V2 documentation Detailed usage and process maps allow for faster development of SOA Governance environment Creation of a COE and use of GBS expertise allows fast start based on initially supplied expertise
    14. 14. Each phase of the SOA Lifecycle has different challenges requiring different governance capability Creating the same service multiple times Service compliance important but difficult Dynamic service reporting complex Poor communication and collaboration within teams Service Development Service Deployment Service Management Enforcement of policies needed on-the-fly Need to control and eliminate and “rogue services” Optimizing service interactions to business process Testing service interactions complex Developing a governance approach requires corporate commitment
    15. 15. Governance is supported by a federated set of capabilities to meet the challenges of service lifecycle management Service Development Service Deployment Service Management <ul><li>Service Discovery </li></ul><ul><li>Service Development Lifecycle </li></ul>Other Service Endpoint Registries / Repositories <ul><li>Runtime Repository </li></ul><ul><li>Runtime Discovery </li></ul><ul><li>Operational Efficiency & Resilience </li></ul><ul><li>Configuration Data Discovery </li></ul><ul><li>Managing change </li></ul>Service Asset Manager Service Registry & Repository Change and Configuration Management UDDI Registries Info based Services Other External Reg / Rep Development Registries Version Control Asset Development Management
    16. 16. Successful SOA service strategy requires a deployment tool to manage and control services at runtime Encourage Reuse Find and reuse services for building blocks for new composite applications. Enhance Connectivity Enable dynamic and efficient interactions between services at runtime. Enable Governance Govern services throughout the service lifecycle Help optimize service performance Enable enforcement of policies. Versioning. Impact analysis WebSphere Service Registry and Repository Publish Find Enrich Govern Manage Publish Find Enrich Govern Manage
    17. 17. Reduce huge maintenance costs by enabling a flexible infrastructure Address the IT pain point of poor reuse and duplication Eliminate lack of ownership and misalignment of activities with business initiatives Service management and control will require the functionality in a federated registry/repository strategy Enriches SOA runtime interaction Enables better control of SOA with governance Promotes reuse and eliminate redundancies <ul><li>Publish and find services and related metadata through all stages of SOA </li></ul><ul><li>Integration and federation with other standard registries and repositories </li></ul><ul><li>Enable optimized access to service metadata </li></ul><ul><li>Manage service interactions and policies </li></ul><ul><li>Facilitates SOA focused service lifecycle management </li></ul><ul><li>Analyze impacts of service introduction, retirement or alteration by maintaining relationships </li></ul>
    18. 18. Service Development and Delivery Management focuses on creation and updating services as assets SOA Lifecycle Infrastructure and Management In Support of SOA Monitor and control operational policies Service Development and Delivery Management Enforce, execute, automate process and policies SOA Governance and Management Method Establish Process, Policies and Organizational Change Service Lifecycle Management SOA Governance
    19. 19. Development and delivery asset management tracks IT assets needed to implement an SOA <ul><li>Uses Reusable Asset Specification (RAS) to describe/classify assets </li></ul><ul><li>Handles multiple types of assets </li></ul><ul><ul><li>Services, source code, documentation, presentations, patterns, process flows </li></ul></ul><ul><ul><ul><li>(Collections of artifacts associated with a particular business requirement) </li></ul></ul></ul><ul><li>Benefits: </li></ul><ul><ul><li>Reduce software development and operational costs </li></ul></ul><ul><ul><li>Improve quality by facilitating the reuse of approved & proven assets </li></ul></ul><ul><ul><li>Integrated with other Rational, Websphere and Tivoli products </li></ul></ul><ul><ul><li>Federated with Websphere Service Registry and Repository (WSRR) </li></ul></ul>Classifier .doc, .uml .ppt, .doc .xml Artifact Reusable Asset Specification (RAS) Asset
    20. 20. An Asset Manager supports development and delivery management of services and composite business services <ul><li>Rational Asset Manager (RAM) is a collaborative software development asset management solution for: </li></ul><ul><ul><li>Design </li></ul></ul><ul><ul><li>Development </li></ul></ul><ul><ul><li>Consumption </li></ul></ul><ul><li>of services as part of an SOA initiative or other development environments </li></ul>Define Search/ Retrieve Create/ Modify Govern Measure Rational Asset Manager
    21. 21. Registries and Repositories can work separately or federated together based on the business/IT SOA requirements <ul><li>Rational Asset Manager (RAM) </li></ul><ul><ul><li>Key requirement is tracking assets in a development environment </li></ul></ul><ul><ul><li>Beginning to be interested in creating services new asset </li></ul></ul><ul><ul><li>Converting current applications into Services </li></ul></ul><ul><li>WebSphere Service Registry and Repository (WSRR) </li></ul><ul><ul><li>Bringing in Services to implement SOA </li></ul></ul><ul><ul><li>Web based environment moving to SOA </li></ul></ul><ul><ul><li>Managing Services in an operational environment </li></ul></ul><ul><ul><li>Services being used from many sources and/or repositories </li></ul></ul>Publish Find Enrich Govern Manage WebSphere Service Registry and Repository Define Search/ Retrieve Create/ Modify Govern Measure Rational Asset Manager
    22. 22. Development-time Deployed / Run-time Federated Search & Publish ClearQuest ClearCase Software Architect Generic Client (.Net or other) Development and deployment of services in SOA will have different requirements within the Lifecycle Service traceability to versioned assets and referenced artifacts Asset based development change, notification and review process Ensures services are developed consistently & in compliance with architecture CICS Datapower Business Services Fabric, ITCAM for SOA WebSphere ESB, Message Broker, Process Server Mediations based on WSRR Lookup for dynamic endpoint selection and binding Any CICS Web services provider program publish & read capability Web services client can publish and search <ul><ul><li>Not every deployed service is a reusable asset and not every reusable asset is a deployed service </li></ul></ul><ul><ul><li>A service will be one of many types of assets managed by Rational Asset Manager </li></ul></ul>Optimized service metadata access on WSRR Lookup for dynamic endpoint selection and binding Publish Find Enrich Govern Manage WebSphere Service Registry and Repository Define Search/ Retrieve Create/ Modify Govern Measure Rational Asset Manager
    23. 23. <ul><li>Unify disparate development teams </li></ul><ul><li>Enable reuse and eliminate rework </li></ul><ul><li>Accelerate delivery </li></ul><ul><li>Increase quality </li></ul><ul><li>Improve reliability </li></ul><ul><li>Enforce and govern architectural standards </li></ul><ul><li>Control access and utilization of assets. </li></ul>Improve business flexibility and service reuse within SOA development and deployment by adding Asset Manager Promote cross project communication of reusable assets Manage compliance and govern multi-platform development assets to Improve quality while reducing development cost and time <ul><li>Managing and facilitate software reuse of assets, including Services </li></ul><ul><li>Drive improvements in end-to-end service quality </li></ul><ul><li>Promote reusable asset sharing </li></ul><ul><li>implement a cross org workflow </li></ul><ul><li>Faster delivery of assets </li></ul><ul><li>Enforce and monitor integrity </li></ul><ul><li>Definable and auditable processes </li></ul><ul><li>Incorporated in overall SOA Governance </li></ul>
    24. 24. Service Lifecycle Management tools enhance each team members ability to be successful Discover services for reuse / publish service WSRR Rational Asset Manager Developer Deployment Manager Track service information Tivoli ITCAM DataPower IT Executive Establish quality management process Rational Method Composer Align key business goals Rational RequisitePro Manage and build run time assets Rational ClearCase and Build Forge Business Executive Track Service Development Rational Portfolio Manager Model business goals Websphere Business Modeler Identify key business goals Websphere Integration Developer Tester Test Changes Rational Tester for SOA Quality Rational Performance Tester Extension for SOA Quality Ensure signoff and create audit trail for change Rational ClearQuest Iterative & continuous PROCESS Create/Govern New Services RBDe Rational Software Architect
    25. 25. Key Takeaways <ul><li>Adopt an end-to-end framework to support a long-term approach toward service orientation </li></ul><ul><li>Implement a Stakeholders Management & Communication Strategy to gain adoption of ESB and service orientation </li></ul><ul><li>Communicate clear roles and responsibilities, including job impacts, at various levels of the organization </li></ul><ul><li>Establish Governance Scenarios to promote an “enterprise view” on shared services </li></ul><ul><li>Integrate the Services Lifecycle into the current SDLC or systems delivery process </li></ul><ul><li>Apply lessons learned from previous enterprise effort to build momentum and gain support from management </li></ul>6
    26. 26. Governance should not an &quot;afterthought&quot;; it matters because without it success is not achievable <ul><li>Focus on business benefits </li></ul><ul><li>Add flexibility to business process </li></ul><ul><li>Improve time to market </li></ul><ul><li>Mitigate risk and regain control </li></ul><ul><li>Maintain quality of service </li></ul><ul><li>Ensure consistency of service </li></ul><ul><li>Improve team effectiveness </li></ul><ul><li>Measure the right things </li></ul><ul><li>Communicate clearly between business and IT </li></ul>Professional investors are willing to pay premiums of 18-26% for stock in firms with high governance. (McKinsey Quarterly) Lack of working governance mechanisms in midsize-to-large (greater than 50 services) post-pilot projects will be the most common reason for project failure (0.8 probability). (Gartner) Governance isn't optional- it's imperative. Without it, ROI will be low and every project out of pilot phase will be at risk. (Gartner)
    1. A particular slide catching your eye?

      Clipping is a handy way to collect important slides you want to go back to later.

    ×