10 Steps to Simplify and Improve Service-Oriented Architecture Governance

4,848 views

Published on

Even after engaging in years of SOA efforts, many companies still suffer from SOA governance problems including funding issues, process inefficiencies, and operational problems.
Too many companies look to software to solve their SOA governance issues when SOA governance is more about people and process than technology.

Join Perficient to examine the 10 steps to improved SOA governance:
1. Align SOA projects with business goals
2. Develop a collaborative organization for SOA governance
3. Define organizational roles and responsibilities
4. Establish the SOA lifecycle process and policies
5. Adjust your software development lifecycle for SOA
6. Define SOA foundational standards
7. Define run-time processes
8. Determine the role of technology in your governance processes
9. Establish SOA measurements and monitoring techniques
10. Evolve and improve SOA governance over time
We will also take a pragmatic look at SOA governance to help you:
• Understand SOA Governance best practices
• Identify gaps in your SOA Governance processes
• Define next steps to improve SOA Governance

Published in: Technology, Business
0 Comments
5 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
4,848
On SlideShare
0
From Embeds
0
Number of Embeds
717
Actions
Shares
0
Downloads
188
Comments
0
Likes
5
Embeds 0
No embeds

No notes for slide

10 Steps to Simplify and Improve Service-Oriented Architecture Governance

  1. 1. 10 Steps to Simplify SOA Governance February 29, 2012
  2. 2. Agenda <ul><li>Introduction </li></ul><ul><li>SOA Governance Overview </li></ul><ul><li>Ten Steps to Simplify SOA Governance </li></ul><ul><ul><li>Align SOA projects with business goals </li></ul></ul><ul><ul><li>Develop a collaborative organization for SOA governance </li></ul></ul><ul><ul><li>Define organizational roles and responsibilities </li></ul></ul><ul><ul><li>Establish the SOA lifecycle process and policies </li></ul></ul><ul><ul><li>Adjust your software development lifecycle for SOA </li></ul></ul><ul><ul><li>Define SOA foundational standards </li></ul></ul><ul><ul><li>Define run-time processes </li></ul></ul><ul><ul><li>Determine the role of technology in your governance processes </li></ul></ul><ul><ul><li>Establish SOA measurements and monitoring techniques </li></ul></ul><ul><ul><li>Evolve and improve SOA governance over time </li></ul></ul>Steps are non-linear Eric Roch Chief Technologist
  3. 3. About Perficient Perficient is a leading information technology consulting firm serving clients throughout North America. We help clients implement business-driven technology solutions that integrate business processes, improve worker productivity, increase customer loyalty and create a more agile enterprise to better respond to new business opportunities.
  4. 4. Perficient Profile <ul><li>Founded in 1997 </li></ul><ul><li>Public, NASDAQ: PRFT </li></ul><ul><li>2010 Revenue of $215 million </li></ul><ul><li>Major market locations throughout North America </li></ul><ul><ul><li>Atlanta, Austin, Charlotte, Chicago, Cincinnati, Cleveland, Columbus, Dallas, Denver, Detroit, Fairfax, Houston, Indianapolis, Los Angeles, Minneapolis, New Orleans, Northern California, Philadelphia, San Francisco, San Jose, Southern California, St. Louis and Toronto </li></ul></ul><ul><li>Global delivery centers in China, Europe and India </li></ul><ul><li>1,700+ colleagues </li></ul><ul><li>Dedicated solution practices </li></ul><ul><li>85% repeat business rate </li></ul><ul><li>Alliance partnerships with major technology vendors </li></ul><ul><li>Multiple vendor/industry technology and growth awards </li></ul>
  5. 5. Our Solutions Expertise & Services <ul><li>Business-Driven Solutions </li></ul><ul><li>Enterprise Portals </li></ul><ul><li>SOA and Business Process Mgmt </li></ul><ul><li>Business Intelligence </li></ul><ul><li>User-Centered Custom Applications </li></ul><ul><li>Interactive Design </li></ul><ul><li>CRM Solutions </li></ul><ul><li>Enterprise Performance Management </li></ul><ul><li>Customer Self-Service </li></ul><ul><li>eCommerce & Product Information Management </li></ul><ul><li>Enterprise Content Management </li></ul><ul><li>Management Consulting </li></ul><ul><li>Industry-Specific Solutions </li></ul><ul><li>Mobile Technology </li></ul><ul><li>Security Assessments </li></ul>Perficient brings deep solutions expertise and offers a complete set of flexible services to help clients implement business-driven IT solutions <ul><li>Perficient Services </li></ul><ul><li>End-to-End Solution Delivery </li></ul><ul><li>IT Strategic Consulting </li></ul><ul><li>IT Architecture Planning </li></ul><ul><li>Business Process & Workflow Consulting </li></ul><ul><li>Usability and UI Consulting </li></ul><ul><li>Custom Application Development </li></ul><ul><li>Offshore Development </li></ul><ul><li>Package Selection, Implementation and Integration </li></ul><ul><li>Architecture & Application Migrations </li></ul><ul><li>Education </li></ul><ul><li>Interactive Design </li></ul>
  6. 6. IT Governance <ul><li>Asset and Portfolio Management </li></ul><ul><li>Business Technology Optimization </li></ul><ul><li>Performance and Service Management </li></ul><ul><li>Security and Access Control </li></ul><ul><li>Enterprise Architecture </li></ul><ul><li>Project lifecycle management </li></ul>IT already practices governance such as quality control, change management and service level agreements.
  7. 7. IT Governance Frameworks <ul><li>The IT Infrastructure Library (ITIL) is a detailed framework with hands-on information on how to achieve a successful governance of IT, developed and maintained by the United Kingdom's Office of Government Commerce, in partnership with the IT Service Management Forum. </li></ul><ul><li>Control Objectives for Information and related Technology (COBIT) is another approach to standardize good information technology security and control practices. This is done by providing tools to assess and measure the performance of 34 IT processes of an organization. The ITGI (IT Governance Institute) is responsible for COBIT </li></ul><ul><li>The ISO/IEC 27001 (ISO 27001) is a set of best practices for organizations to follow to implement and maintain a security program. It started out as British Standard 7799 ([BS7799]), which was published in the United Kingdom and became a well known standard in the industry that was used to provide guidance to organizations in the practice of information security. </li></ul><ul><li>The Information Security Management Maturity Model ISM3 is a process based ISM maturity model for security. </li></ul><ul><li>AS8015-2005 Australian Standard for Corporate Governance of Information and Communication Technology </li></ul>We have a wealth of knowledge and processes to leverage for SOA.
  8. 8. What is SOA governance? <ul><li>Because services are intrinsically distributed and reusable they introduce new governance challenges </li></ul><ul><li>SOA governance is an extension of IT governance that focuses on: </li></ul><ul><ul><li>lifecycle of services and composite applications </li></ul></ul><ul><ul><li>the decision rights for the development, deployment and management of new services </li></ul></ul><ul><ul><li>monitoring and reporting processes for capturing and communicating SOA results and process improvement </li></ul></ul><ul><li>SOA governance mission: To create policies, principles, standards, procedures and processes that will realize the full business benefit of service orientation </li></ul><ul><li>Perficient’s SOA governance design goals: </li></ul><ul><ul><li>Keep the process and deliverables lightweight </li></ul></ul><ul><ul><li>To manage change, build consensus and roll out governance processes iteratively shifting software-engineering culture over time </li></ul></ul><ul><ul><li>Mature SOA governance over time through measurements and process improvement </li></ul></ul>Keep the process and deliverables lightweight, easy to follow and add value.
  9. 9. SOA Governance Framework <ul><li>Managing the portfolio of services: planning development of new services and updating current services </li></ul><ul><li>Managing the service lifecycle : meant to ensure that updates of services do not disturb current service consumers </li></ul><ul><li>Using policies to restrict behavior: rules can be created that all services need to apply to, to ensure consistency of services </li></ul><ul><li>Establish performance monitoring of services: because of service composition, the consequences of service downtime or underperformance can be severe. </li></ul>Create, communicate and enforce governance policies
  10. 10. SOA Governance Lifecycle <ul><li>Governance is the combination of people, policies, and processes that an organization leverages to achieve desired behaviors </li></ul><ul><li>SOA governance is about achieving the desired behavior associated with SOA adoption  </li></ul><ul><li>Project governance - the behaviors span the normal software development efforts </li></ul><ul><li>Run-time governance - the interaction between service consumers and service providers in production environments </li></ul><ul><li>Pre-project governance - processes associated with the proposal, approval, and funding of projects </li></ul><ul><li>During each of these efforts, people, policies, and processes must be established and leveraged to ensure that the changes to the culture are successful </li></ul>Source: SOA Governance by Todd Biske (book)
  11. 11. Governance Process and Artifacts <ul><li>Policies and Decision Rights </li></ul><ul><ul><li>Set of guidebooks to address SOA Governance </li></ul></ul><ul><li>Strategy and roadmap </li></ul><ul><ul><li>Core Services </li></ul></ul><ul><ul><li>Roadmap: Projects and timeline </li></ul></ul><ul><ul><li>People and process impact </li></ul></ul><ul><ul><li>Technology enablement </li></ul></ul><ul><li>Organization </li></ul><ul><ul><li>SOA Steering Committee and Competency Center </li></ul></ul><ul><ul><li>Create, approve, communicate and enforce the governance framework </li></ul></ul><ul><ul><li>Interrelationships and dependences </li></ul></ul><ul><ul><li>SOA measurement criteria and process </li></ul></ul><ul><li>SOA Architecture </li></ul><ul><ul><li>Documented standards </li></ul></ul><ul><ul><li>Design review process and checklists </li></ul></ul><ul><li>SOA Lifecycle </li></ul><ul><ul><li>Design to deploy methodology </li></ul></ul><ul><ul><li>Deliverable templates, checklists and samples </li></ul></ul><ul><ul><li>Release management </li></ul></ul><ul><li>SOA Operations </li></ul><ul><ul><li>Policy based monitoring and management </li></ul></ul><ul><ul><li>Security policies </li></ul></ul><ul><ul><li>Build and deploy standards and process </li></ul></ul><ul><ul><li>Administration documentation and processes </li></ul></ul>Governance should flow smoothly within a lifecycle with everyone working together.
  12. 12. Quick Start Rulebook™ Methodology <ul><li>Develops SOA strategy and roadmap </li></ul><ul><li>Establishes the SOA competency center organizational and maturity model </li></ul><ul><li>Define governance model for design, asset management and operations </li></ul><ul><li>Develops SOA reference architecture </li></ul><ul><li>Addresses SOA project orientated methodology </li></ul><ul><li>Establishes the operations and quality assurance strategy processes and procedures </li></ul><ul><li>Supported by design patterns and reusable components </li></ul><ul><li>Codify common design patterns – e.g. the Exception Handler </li></ul><ul><li>Optimize the operational environment </li></ul>
  13. 13. Step 1: Business Alignment <ul><li>A top-down view of business services by domain identifies core services </li></ul><ul><li>Project alignment simplifies funding ensures ROI </li></ul><ul><li>Start a SOA program in the context of projects in the portfolio </li></ul><ul><li>Identify projects that will benefit from SOA: </li></ul><ul><ul><li>Integration </li></ul></ul><ul><ul><li>Process automation and improvement </li></ul></ul><ul><ul><li>Information access </li></ul></ul><ul><ul><li>Multi-channel </li></ul></ul><ul><ul><li>APIs </li></ul></ul>
  14. 14. Business Alignment Case Study <ul><li>Six iterations delivered through the end of 2012 </li></ul><ul><li>Automates sales role in the overall order process </li></ul><ul><li>Features: Visibility to product availability, automated cost estimates, collaborative (with customer) proposal process, capture of information to eliminate downstream duplicate data entry and facilitate process hand-offs </li></ul><ul><li>Key benefits: Process improvement and automation results in time savings for sales leads to increased sales </li></ul><ul><li>Cost estimate: $$$$ </li></ul>
  15. 15. Business Alignment Case Study
  16. 16. Step 2: Organizational Structure <ul><li>Develop a formal organization for the SOA discipline </li></ul><ul><li>Build processes, best practices & internal competencies to best utilize resources </li></ul><ul><li>Architect and advise SOA project activities </li></ul><ul><li>Standardization of architecture and product roles </li></ul><ul><li>Provide a governance role for reusable services </li></ul><ul><li>Coordinate with PMO to manage the SOA project lifecycle (process and deliverables) </li></ul><ul><li>Through process, standards and governance create continuous and measurable improvements </li></ul><ul><li>Accomplish enterprise wide integration through iterations based on reusable artifacts </li></ul><ul><li>Evangelize SOA within the IT organization </li></ul>
  17. 17. Governance People, Process, Technology CMDB Plan Lifecycle Roles Disciplines Tools Portfolio Management Visual Modeling Repository Registry Projects & Assets Versioned Source Business Processes & Rules BPM Metrics & History ESB BPM Source Control SOA Management Policy Audit SLA XSD Authoring App Server Registry Release Management Lifecycle Management Policy Management SOA Contract Management Portfolio Mgt Support & Infrastructure SOA Steering Committee Competency Center Enterprise Architecture Business Leaders Application Development Quality Assurance Administration & Operations Specify Provision Orchestrate Test Deploy Run IT Steering Committee Test Tools
  18. 18. Organization Case Study <ul><li>Structure </li></ul><ul><li>Standards </li></ul><ul><li>Responsibilities </li></ul><ul><li>Escalations </li></ul><ul><li>Process Coordination </li></ul><ul><li>Collaboration </li></ul><ul><li>Change management </li></ul><ul><li>Consensus </li></ul><ul><li>Long-term manage SOA infrastructure </li></ul><ul><li>Work with SOA CC for capacity planning and SLAs </li></ul><ul><li>Build business services with SOA CC </li></ul><ul><li>Domain/Data subject matters experts </li></ul><ul><li>Consult with development to build business services </li></ul><ul><li>Support – Monitor Business Services Infrastructure </li></ul><ul><li>Liaison business services and technical deployment </li></ul><ul><li>Manage infrastructure until formal turnover </li></ul>
  19. 19. Organization Case Study <ul><li>Long-term manage SOA infrastructure </li></ul><ul><li>Work with ICC for capacity planning and SLAs </li></ul><ul><li>Build business services with ICC </li></ul><ul><li>Domain/Data subject matters experts </li></ul><ul><li>Consult with development to build business services </li></ul><ul><li>Support – Monitor Business Services Infrastructure </li></ul><ul><li>Liaison business services and technical deployment </li></ul><ul><li>Manage infrastructure until formal turnover </li></ul>Legend – R Responsible, A Approve, C Consulted, I Informed Systems Development Teams ICC Systems Administration Applications R C Subsystems R C Business Services R C Application Service & Adapters R A Orchestration C R Common Components I R Metadata I R Logical Bus I R Broker A R BPM Engine A R Physical Bus A R SOA Infrastructure A R Capacity Planning A R Service Level Agreements A R Platforms C R OS C R RDBMS C R Networks C R
  20. 20. Step 4: SOA Lifecycle Process and Policies Reference: SOA for Profit
  21. 21. Lifecycle Case Study – Trouble Spots
  22. 22. What’s in the SDLC to build services? <ul><li>Contracts are packages of structured and unstructured assets -interfaces, conditional elements, and documentation </li></ul><ul><li>Operations available, along with the associated abstract payload definition (both inbound and outbound) </li></ul><ul><li>List of potential exception conditions </li></ul><ul><li>Functional semantics such as pre- and post-conditions </li></ul><ul><li>Business semantics and invariants related to the service </li></ul><ul><li>Synchronous or asynchronous access, and other message exchange patterns </li></ul><ul><li>Security requirements, including supported credentials, encryption, and signatures </li></ul><ul><li>Other important contextual information such as Quality of Service (QoS) that describes performance and availability metrics </li></ul>
  23. 23. Step 5: SDLC Adjustments Add a very simple SOA deliverable templates early and gates to trigger the SOA lifecycle * Note: The Feasibility Phase Project Architecture has a section for conceptual architecture Service Requirements Business Services In Feasibility Architecture* Service Certification
  24. 24. Step 5: SDLC Adjustments Add a very simple SOA deliverables to the Agile approach Business Service Solution Architecture Service Design Test Cases
  25. 25. Step 6: SOA Standards <ul><li>Architecture Guide </li></ul><ul><ul><li>SOA product roles within the organization </li></ul></ul><ul><ul><li>Service Decomposition and Design </li></ul></ul><ul><ul><li>SOA Design Patterns </li></ul></ul><ul><ul><li>SOA Registry Repository </li></ul></ul><ul><ul><li>Utility services – e.g. auditing, error handling, transaction monitoring </li></ul></ul><ul><ul><li>Non-functional requirements and strategy to meet requirements </li></ul></ul><ul><ul><li>Security standards </li></ul></ul><ul><ul><li>WSDL, XML and REST standards </li></ul></ul><ul><li>Developers Guide </li></ul><ul><ul><li>Environment setup </li></ul></ul><ul><ul><li>Product usage guidelines </li></ul></ul><ul><ul><li>Guidelines for reuse </li></ul></ul><ul><ul><li>Common schema usage guidelines </li></ul></ul><ul><ul><li>Naming standards </li></ul></ul><ul><ul><li>Pattern implementation </li></ul></ul><ul><ul><li>QA strategy and tools </li></ul></ul><ul><ul><li>Version management strategy </li></ul></ul><ul><li>Systems Administration Guide </li></ul><ul><ul><li>Build documents </li></ul></ul><ul><ul><li>Monitoring and management </li></ul></ul><ul><ul><li>Environment management – change control and migration </li></ul></ul><ul><ul><li>Directory structure and security </li></ul></ul>Services are certified to meet standards
  26. 26. Case Study: SOA Standards <ul><li>JAD Sessions Customize Guidebook Content </li></ul><ul><li>Pilot Verifies Guidebooks </li></ul><ul><li>Pilot Introduces Methodology </li></ul>
  27. 27. Run-Time Management <ul><li>The distributed, cross-boundary nature of services and access to them presents new performance, availability and security risks that need to be managed </li></ul><ul><li>The rapid deployment and loose coupling of services along with their virtualized application flows present new complexities in key processes </li></ul><ul><li>The need to effectively handle the performance and prioritization of virtualized services while efficiently utilizing available resources </li></ul>
  28. 28. SOA Infrastructure and Management <ul><li>Network Components Configuration: Load balancing, Firewalls, Routers </li></ul><ul><ul><li>Impact of messaging </li></ul></ul><ul><ul><li>Configurations for application servers, messaging, ESBs, BPM </li></ul></ul><ul><li>Virtualization of SOA Components </li></ul><ul><ul><li>Virtualized provisioning for fault-tolerance and capacity </li></ul></ul><ul><li>Monitoring and Management </li></ul><ul><ul><li>SOA management integrated with enterprise management </li></ul></ul><ul><ul><li>Exception management and auditing as a service </li></ul></ul><ul><ul><li>Scripted ping and alert, shut down and restart </li></ul></ul><ul><li>Application servers setup, capacity planning and tuning </li></ul><ul><ul><li>Platform for most Portals, ESBs, and BPM software suites </li></ul></ul><ul><ul><li>Configuration for load-balancing, fault tolerance, tuning and capacity </li></ul></ul><ul><li>SOA Software Suites configuration and automation </li></ul><ul><ul><li>Standardized environments with scripted build and deploy </li></ul></ul><ul><ul><li>Scripted monitoring and management </li></ul></ul><ul><ul><li>Documented administration and operations guides </li></ul></ul>Everything has to work together !
  29. 29. SOA Run-time Governance and ITIL <ul><li>The Information Technology Infrastructure Library ( ITIL ) is a set of concepts and policies for managing information technology (IT) infrastructure, development and operations.. ITIL gives a detailed description of a number of important IT practices with comprehensive checklists, tasks and procedures that can be tailored to support SOA concepts and artifacts. </li></ul><ul><li>Service Support </li></ul><ul><ul><li>Service Desk / Service Request Management </li></ul></ul><ul><ul><li>Incident Management </li></ul></ul><ul><ul><li>Software Asset Management </li></ul></ul><ul><ul><li>Problem Management </li></ul></ul><ul><ul><li>Configuration Management </li></ul></ul><ul><ul><li>Change and Release Management </li></ul></ul><ul><li>Service Delivery </li></ul><ul><ul><li>Service Level Management </li></ul></ul><ul><ul><li>Capacity Management </li></ul></ul><ul><ul><li>Availability Management </li></ul></ul><ul><ul><li>Financial Management for IT Services </li></ul></ul><ul><li>Service Level Management </li></ul><ul><ul><li>Capacity Management </li></ul></ul><ul><ul><li>IT Service Continuity Management </li></ul></ul><ul><ul><li>Availability Management </li></ul></ul><ul><ul><li>Financial Management for IT Services </li></ul></ul><ul><li>ICT (Information and Communication Technology) Infrastructure Management </li></ul><ul><ul><li>ICT Design and Planning </li></ul></ul><ul><ul><li>ICT Deployment Management </li></ul></ul><ul><ul><li>ICT Operations Management </li></ul></ul><ul><ul><li>ICT Technical Support </li></ul></ul>
  30. 30. Step 6: Run Time <ul><li>Involve operations early in a SOA program – organizational structure </li></ul><ul><li>Monitoring and Management are SOA standards </li></ul><ul><li>Properly plan for infrastructure cost, time, deliverables and dependences as part of the SOA roadmap and project plans </li></ul><ul><li>Put the vendor on the hook to support the sizing, architecture, configuration and performance of the infrastructure </li></ul><ul><li>Dedicate and train an administrator to the SOA infrastructure early in the project to work with the vendor though the installation, configuration and testing </li></ul><ul><li>Do a capacity test on the production environment before deployment and maintain a capacity baseline </li></ul><ul><li>Include deployment and the testing of deployments as part of the process and deliverables </li></ul><ul><li>Track your systems dependencies and include them in an operations guide as part of project transition </li></ul>
  31. 31. Step 8: Governance Technology <ul><li>The registry repository supports SOA lifecycle development and run-time management </li></ul><ul><li>Evaluation of the registry repository should be on the SOA roadmap </li></ul><ul><li>The SOA lifecycle management should fit into your SDLC </li></ul><ul><li>The SOA run-time management should fit into your architecture standards </li></ul>
  32. 32. SOA Governance Case Study <ul><li>Activities </li></ul><ul><ul><li>Requirements for governance - steps, policies, metadata </li></ul></ul><ul><ul><li>Map metadata and SOA design deliverable templates requirements to registry taxonomy </li></ul></ul><ul><ul><li>Customization of the SOA design templates </li></ul></ul><ul><ul><li>Definition of Policy Manager and Policy Agents </li></ul></ul><ul><ul><li>Configuration of the registry - set up of taxonomy and service entries (for PoC) </li></ul></ul><ul><ul><li>To be tested with PoC project lifecycle </li></ul></ul><ul><li>Deliverables </li></ul><ul><ul><li>SOA design templates for Registry and Policy Manager </li></ul></ul><ul><ul><li>Defined and configured Registry and Policy Manager entries (Per POC needs) </li></ul></ul>
  33. 33. Step 9: Measurements and Monitoring <ul><li>COE Services </li></ul><ul><ul><li>Architecture effectiveness </li></ul></ul><ul><ul><ul><li>Time required for process change, service reuse, metadata (reuse, coverage, quality, depth) </li></ul></ul></ul><ul><ul><li>Service Reuse </li></ul></ul><ul><ul><li>Resource demand </li></ul></ul><ul><ul><li>Deprecated interfaces </li></ul></ul><ul><ul><li>Service Level Agreements (SLA) </li></ul></ul><ul><ul><li>Software quality </li></ul></ul><ul><li>Finance </li></ul><ul><ul><li>ROI for the SOA/integration software </li></ul></ul><ul><ul><li>Project cost savings </li></ul></ul>Source: SOA Governance by Todd Biske (book)
  34. 34. Case Study – Measures / Maturity Models
  35. 35. Step 10: Evolve Over Time <ul><li>Program Management </li></ul><ul><li>Technical Architecture </li></ul><ul><li>Business Architecture </li></ul><ul><li>Implementation </li></ul><ul><li>Quality Assurance </li></ul><ul><li>Operations </li></ul><ul><li>Support </li></ul>A SOA Program Requires Activities and Deliverables in the following categories:
  36. 36. Case Study – SOA Program Iterations 1.1 Business Service Specification Analysis Ready for Design Activity Deliverable Milestone Ready for Testing Program Foundation Pilot (GetProvider) Ready for Deployment Business Process Model Non-Functional Requirements Design Architecture Design (Service) Detail Design Construction Test Implementation Technical Architecture Program Management Operations Future State Architecture Standards Templates Support Process Processes Communications Architecture Audit, Logging , & Exception Handling Security Standards Design Patterns Design Operations Repository SLA QA Service Testing Strategy Operations SLA Program Management SLA Prototype 1.2 1.3 Data Virtualization
  37. 37. A Path to SOA Maturity SOA is an incremental journey
  38. 38. Perficient SOA Health Check <ul><li>Engagement Structure </li></ul><ul><ul><li>Get SOA projects on target with actionable and prioritized recommendations </li></ul></ul><ul><ul><li>2 Perficient Consultants for 1 week </li></ul></ul><ul><ul><li>Fluid engagement pre-planned and coordinated with the client </li></ul></ul><ul><li>Facilitated sessions </li></ul><ul><ul><li>Document as-is architecture and make best practices recommendations </li></ul></ul><ul><ul><li>Review… </li></ul></ul><ul><ul><ul><li>IT strategy for SOA including completed projects to date </li></ul></ul></ul><ul><ul><ul><li>Organization and governance </li></ul></ul></ul><ul><ul><ul><li>Solution architecture and design </li></ul></ul></ul><ul><ul><ul><li>Enterprise and reference architecture </li></ul></ul></ul><ul><ul><ul><li>Service monitoring, auditing, and exception handling practices </li></ul></ul></ul><ul><ul><ul><li>Current staffing roles to support SOA </li></ul></ul></ul><ul><ul><ul><li>Existing service level agreements and escalation procedures </li></ul></ul></ul><ul><ul><ul><li>Testing and quality assurance </li></ul></ul></ul><ul><ul><ul><li>Current change control process </li></ul></ul></ul><ul><li>Key deliverables </li></ul><ul><ul><li>Findings Presentation </li></ul></ul><ul><ul><li>Recommendations Document </li></ul></ul><ul><ul><ul><li>Findings, Best Practices, Recommendations, Priorities </li></ul></ul></ul>

×