20120716 l2 soa for enterprise-og-wsh-conf

464 views

Published on

Presentation at Open Group Conference in Washington DC on July 16th, 2012 on LEGACY EVOLUTION TO SOA for Global Enterprise based on OPEN GROUP Project L2SOA

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

  • Be the first to like this

No Downloads
Views
Total views
464
On SlideShare
0
From Embeds
0
Number of Embeds
20
Actions
Shares
0
Downloads
13
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • Enterprise Integration Patterns(EIP) are the Design Patterns that facilitate the system integration framework for Legacy to SOA evolution. Each EIP pattern has different cost and complexity measures. SOA initiative have impact on existing organizational policies, process and resource planning. The Open Group SOA Governance Framework’s goal is to enable organizations to define and deploy their own focused and customized SOA governance model.SOA as a loosely-coupled architecture, requires a solid and robust security model.
  • 20120716 l2 soa for enterprise-og-wsh-conf

    1. 1. Evolving the Enterprise IT Legacy to SOASundar RamanathanJuly 16, 2012
    2. 2. Presenter Profile  Sundararajan Ramanathan – Enterprise Architect @ Capgemini since June 2006  TOGAF 9 & Capgemini IAF Certified Architect - http://www.opengroup.org/togaf9/cert/protected/certuploads/30487.pdf  10 years at Compuware, Detroit, Michigan  5 years at Informix Software, California  Education  B.Sc (Physics), B.E (Indian Institute of Science), MBA (Wayne State University, Michigan)  Open Group  Co-Author: Legacy Evolution to SOA Guide  Chair: SOA for Business Technology Project  NIST  Contributor – Cloud Computing Forum – Taxonomy, Reference Architecture and Roadmap In collaboration with Legacy Evolution to SOA 2 © Copyright Capgemini 2011 All Rights Reserved
    3. 3. Agenda Drivers for Legacy Key SOA PrinciplesL2SOA Modernization Organization and ProcessProject Overview Approach to Enable Metrics for L2SOAProject Team L2SOA EngagementModernization StrategiesEIP Pattern-Based SIApproach SOA Governance Case Study AEIP Patterns: Cost & Reference Model SummaryComplexity Analysis Legacy & Security Q&A In collaboration with Legacy Evolution to SOA 3 © Copyright Capgemini 2011 All Rights Reserved
    4. 4. L2SOA Project OverviewLeverage the collective experiences of L2SOA practitioners to develop legacyevolution best practices and lessons learned to improve the success ofL2SOA implementations. The content is therefore based on real projects. Current state problems and issues Key concepts, principles, and considerations related to L2SOA A high-level (general) approach to enable L2SOA Consolidated best practices, including metrics, architecture styles, technologies, governance, etc. Historical case studies providing insight into how some of the concepts described in the document are currently being applied L2SOA Project Overview Project Team In collaboration with Legacy Evolution to SOA 4 © Copyright Capgemini 2011 All Rights Reserved
    5. 5. L2SOA Project Team Authors  Xinfeng Chen, Hewlett-Packard  Sundararajan Ramanathan, Capgemini  Mukund Srinivasan, Capgemini  Joost Van Der Vlies, Hewlett-Packard (Project Chair)  Tejpal (TJ) Virdi, The Boeing Company (Project Chair) Reviewers  Ramagopal Allampalli, Cognizant Technology Solutions  Jim Basler, Oracle  Carleen Christner, Hewlett-Packard  Pascal Dussart, LoQutus  Ed Harrington, Architecting-the-Enterprise  Venkata Kona, Wipro  Martin Neuhard, Hewlett-Packard  Carol Wang, Hewlett-Packard L2SOA Project Overview Project Team In collaboration with Legacy Evolution to SOA 5 © Copyright Capgemini 2011 All Rights Reserved
    6. 6. Drivers for Legacy Modernization Silo Architecture, Complex or No High Sustain Costs, Less Agility, Interoperability, redundant /duplicate No Business Metrics Information storage/processing, Less scope for Automation BUSINESS FUNCTIONAL Tightly Coupled Applications, Outdated Poor User Experience, Lack of SSO and Technology , Protocols with no support, Integration to new UI/ Presentation Embedded Logic and Complex Configuration platforms/devices USABILITY TECHNOLOGY Maintenance costs are getting higher and higher Control over the application landscape and its dependencies is difficult The business needs to change faster than IT can support. Drivers for Legacy Modernization Approach to Enable L2SOA In collaboration with Legacy Evolution to SOA 6 © Copyright Capgemini 2011 All Rights Reserved
    7. 7. Approach to Enable L2SOA •L2SOA Business case, •SOA maturity ROI Combining TOGAF ADM and assessment •Principle decision on TOGAF SOA Guide with •Legacy expertise extend or re* important L2SOA aspects •Current state legacy •Application Portfolio Rationalization •Legacy Organization Management of change •SOA Infrastructure versus Apps •SOA maturity as input in legacy modernization planning Drivers for Legacy •Legacy transformation phases Modernization •Solution Building Blocks - SBBs •Vendor/tool selection Approach to Enable L2SOA In collaboration with Legacy Evolution to SOA 7 © Copyright Capgemini 2011 All Rights Reserved
    8. 8. Key SOA Principles Well-Defined Service Contract  Loosely-Coupled Services Define Services with Appropriate Granularity  Design Services for Stateless  Ensure Services have Appropriate Security Enforcement Standards  Adopt SOA Ontology/Vocabulary Standard Key SOA Principles Organization and Process Metrics for L2SOA Engagement In collaboration with Legacy Evolution to SOA 8 © Copyright Capgemini 2011 All Rights Reserved
    9. 9. Organization and Process Managed Transformation Program  Work across Business Boundaries(Business, Technology ) and Service Ownership ROI Analysis based on Metrics andImpact of Current IT Operations and KPIsChange Management & LegacyProcesses  Skill Development and Training plan for Employees & Partners Risk Analysis on lack of adoption and adaptability Key SOA Principles Organization and Process Metrics for L2SOA Engagement In collaboration with Legacy Evolution to SOA 9 © Copyright Capgemini 2011 All Rights Reserved
    10. 10. Metrics for L2SOA Engagement Metrics provide a baseline measurement to justify an L2SOA engagement. Metrics should be measured at appropriate intervals and reported for continues improvement and measure the overall performance. Key Metrics Application Usage Cost Reduction Functional Re-use Quality of Service Revenue-generated Time-to-Market Key SOA Principles Security KPIs (data protection-related KPIs) Organization and Process Metrics for L2SOA Engagement In collaboration with Legacy Evolution to SOA 10 © Copyright Capgemini 2011 All Rights Reserved
    11. 11. Modernization Strategies Modernization strategies to enable the process of modernizing legacy applications using SOA Enterprises need to select one or more strategies, after in- depth evaluation. Key Modernization Strategies • Approach • Problem Solved/Value-Add  Service Enablement • Risks and Mitigations  Language Conversion • Architecture Building Blocks Involved  Re-Architect  Re-hosting of Applications Modernization Strategies EIP Pattern-Based SI Approach EIP Patterns: Cost & Complexity Analysis In collaboration with Legacy Evolution to SOA 11 © Copyright Capgemini 2011 All Rights Reserved
    12. 12. Modernization Strategies (Continued)Strategy Approach Problem Solved/ Risks & Mitigations Architecture Building Value Add Blocks InvolvedService Enablement Host Services with Re-use Assets, Improve Difficult to identify useful Information: New Information Integration Platforms Core Value, Automated functionality, Poor Services Business Process Documentation, System Technology: Legacy Integration Disruption Platforms, Hosting Service ContainersLanguage Conversion Convert to Modern Reduce Total Cost of Impossible to provide Information & Technology Platforms/ Languages Ownership(TCO), Time autonomous Services (Re- Frameworks To Market (TTM), Adapt Architect), Unsupported functions to SOA in new language/environment, SkillsRe-Architect (New Environment) Restructure Functions and Potential to fix old Budget and Architecture New ABB’s and SBB’s Code problems and introduce approach discussions new functionsRe-Architect (Old Environment) Restructure mainframe Reuse Business Old Documentation, Code / Data Integration Solution patterns – source to specific functions Functionality and changes, Need additional testing leverage SBB’s and expose with Legacy SOA Intellectual Property (IP) adaptorsRe-hosting of Applications Platform Change, Needs Business Logic Preserve existing investments, Virtualization – Architecture Building combination of other preserved, Agile Legacy Integration Platform Blocks and reusable SBB’s strategies Integration to Legacy, complexity Reduce TTM, Improve Xabilities Modernization Strategies EIP Pattern-Based SI Approach EIP Patterns: Cost & Complexity Analysis In collaboration with Legacy Evolution to SOA 12 © Copyright Capgemini 2011 All Rights Reserved
    13. 13. EIP Pattern-Based SI ApproachEnterprise Integration Patterns(EIP) Design Patterns Facilitate the system integration framework for Legacy to SOA evolution Complex enterprise systems Leverage a combination of EIP approaches Provide the capabilities to modernize their architecture. Common Patterns Enterprise Integration (Service Bus) Queue-based Mediation Service Enablement Screen Scraping Re-design Modernization Strategies EIP Pattern-Based SI Approach EIP Patterns: Cost & Complexity Analysis In collaboration with Legacy Evolution to SOA 13 © Copyright Capgemini 2011 All Rights Reserved
    14. 14. EIP Patterns: Cost & Complexity AnalysisThe directly SOA related patterns have a high cost and medium-to-high complexity.High costs can be spread across many service-enabled applications – both legacy and new, than web-service Modernization Strategies based pattern as Screen-scraping EIP Pattern-Based SI Approach EIP Patterns: Cost & Complexity Analysis In collaboration with Legacy Evolution to SOA 14 © Copyright Capgemini 2011 All Rights Reserved
    15. 15. SOA Governance Reference ModelThe Open Group SOA Governance Framework’s goal is to enable organizations to define anddeploy their own focused and customized SOA governance model.. (*) See also the patterns SOA Governance (**) This needs to be explicitly taken into account as an architectural deliverable. Reference Model Legacy & Security In collaboration with Legacy Evolution to SOA 15 © Copyright Capgemini 2011 All Rights Reserved
    16. 16. Legacy and SecurityLegacy System security Concerns for L2SOA transformation: Outdated technology and software Vulnerable to newer technologies Closed Encryption An ingenious manual administration of user names and passwords Session definition in the legacy system, especially in connect of SSOApproach: Leverage Open Group Security Project frameworkThe Open Group Security for the Cloud and SOA project, describestwo sets of principles largely:  A set of 20 generic security principles common to all designs aiming to assure a secure IT architecture, ranging from “security by design” to “data protection lifecycle”.  A specific set of principles regarding assuring security in architecting the cloud and the SOA environment, mainly focused on policies, data protection and privacy, and cloud specific principles. SOA Governance Reference Model Legacy & Security In collaboration with Legacy Evolution to SOA 16 © Copyright Capgemini 2011 All Rights Reserved
    17. 17. Case Study A – Legacy Supply Chain Evolution to SOA Case Study A Summary Q&A In collaboration with Legacy Evolution to SOA 17 © Copyright Capgemini 2011 All Rights Reserved
    18. 18. Summary Business, Functional Usability and Technology are key drivers for Legacy to SOA initiated modernization. The TOGAF (ADM) combined with TOGAF SOA Guide provides stepwise approach for L2SOA transformation engagements. SOA initiative has to be measured for ROI and other performance concerns, using industry standard metrics. Organization can adapt single or more modernization strategies based on the system requirement. Meetings for the Legacy Evolution to SOA Working Group for next iteration. For more details, Please read: The Open Group Guide : Legacy Evolution to SOA https://www2.opengroup.org/ogsys/publications/viewDocument.html?publicationid=12590&documentid=11481 Refer to the L2S0A Working Group - https://collaboration.opengroup.org/projects/soa-legacy/protected/ Download L2SOA Tutorial based on published L2SOA Guide https://collaboration.opengroup.org/projects/ssdg/documents.php?action=show&dcat=14&gdid=26417 Case Study A Summary Q&A In collaboration with Legacy Evolution to SOA 18 © Copyright Capgemini 2011 All Rights Reserved
    19. 19. Questions ? Case Study A Summary Q&AIn collaboration with Legacy Evolution to SOA 19 © Copyright Capgemini 2011 All Rights Reserved

    ×