Service Virtualization CA LISA introduction. Jim Dugger CA LISA Product Marketing Manager Steve Mazzuca CA LISA Public Sector Alliances Director

Transcription

1 Service Virtualization CA LISA introduction Jim Dugger CA LISA Product Marketing Manager Steve Mazzuca CA LISA Public Sector Alliances Director

2 innovate or die The Product is the entire brand and customer experience Service oriented products are delivered late, over budget and with questionable quality WHY?

3 changes in software development Constraints Complexity Costs Composite (Custom Applications, SOA, Cloud) Client/Server (Packaged Apps such as SAP, Siebel, Oracle ) Mainframe

4 Current development nightmare App1 App1 ST System Integration Testing User Acceptance Testing Production App2 App2 ST Performance Testing App3 App3 ST 4 Steps to closing the Gap 1. Multiple streams 2. Push right 3. Environment constraints 4. Lack of Automation 1. Shift Left 2. Decouple 3. Automate 4. Learn

5 & Test Cloud Lab Constraints Wires hanging out of the Virtual Lab for App Goals: Elastic Capacity & Rapid Provisioning Issue: Wires Hanging Out of your Cloud System Dependencies Remain Unanswered Mainframe SaaS DB System of Record Cloud Environment Provision Requests Order Mgr CRM Test Virtual Lab Manager VM Catalog App Server Virtual Machines

6 the big problem: constraints INCOMPLETE DEVELOPMENT SYSTEM UNAVAILABLE MAINFRAME DATA LEGACY EXTERNAL INVALID DATA ACCESS FEES I can t do anything until I have everything and I never have everything!

7 solution: service virtualization MAINFRAME DATA LEGACY EXTERNAL

8 constraint: schedule dependencies 1 shift left the SDLC Without LISA Uncertain delivery schedule defects persist until UAT System Test Integration With CA LISA more effort moved sooner in the lifecycle Typical composite app today waits for whole assembly to begin With LISA System Test Reduction in SDLC Faster Rollout Integration UAT

9 constraint: infrastructure availability 2 infrastructure requirements reduction AFTER BEFORE MAINFRAME DATA LEGACY EXTERNAL MAINFRAME DATA LEGACY EXTERNAL 1 n Integration 1 n Contention for access between on shore and off shore teams Constrained mainframe and complex coordination cycles stunted agility MAINFRAME DATA LEGACY EXTERNAL Virtual Environments for /Integration/Test/Pre Prod MAINFRAME DATA LEGACY EXTERNAL MAINFRAME DATA LEGACY EXTERNAL Test 1 n Pre Prod 1 n Environments not realistic and require manual data and maintenance Mainframe access Mainframe access required for any testing Eliminates need for enterprise systems ((mainframe, CRM, ERP, etc.) in many cases,,, ) y One customer avoided $30M infrastructure cost by eliminating test lab expansion Copyright 2012 CA. All rights reserved.

10 constraint: system availability 3 performance readiness BEFORE AFTER Shared Mainframe Service Or similar heavy weight implementation environment Constraints affecting performance team productivity, with inability to isolate flaws High costs to build and maintain stubs with only limited functionality One customer achieved 300% more performance coverage and avoided $30+ million in new infrastructure investment

11 constraint: data volatility 4 data & scenario management Before App data complex and volatile Lengthy lab set up times Activities often delayed to integration and UAT Input Data Many dependent data sets reduced down to App4 only those that directly connect. App1 App5 App2 App7 Stable, consistent inputs cover happy paths, edge and error conditions elegantly with lower upkeep. System Under Test Users App6 One Customer ss Outcome: 30 day sprints for this implementation were reduced by % Data setup time reduced by 68% by providing smart data Out of Scope Dependencies Deal with the data at the application level, not outof scope data models. App8

12 Notices All trademarks, trade names, service marks and logos referenced herein belong to their respective companies. No unauthorized use, copying or distribution permitted. Certain information in this publication may outline CA s general product direction. However, CA may make modifications to any CA product, software program, method or procedure described in this publication at any time without notice, and the development, release and timing of any features or functionality described in this publication remain at CA s sole discretion. CA will support only the referenced products in accordance with (i) the documentation and specifications provided with the referenced product, and (ii) CA s then current maintenance and support policy for the referenced product. Notwithstanding anything in this publication to the contrary, this publication shall not: (i) constitute product documentation or specifications under any existing or future written license agreement or services agreement relating to any CA software product, or be subject to any warranty set forth in any such written agreement; (ii) serve to affect the rights and/or obligations of CA or its licensees under any existing or future written license agreement or services agreement relating to any CAsoftware product; or (iii) serve to amend any product documentation or specifications for any CA software product. This document is for your informational purposes only and CA assumes no responsibility for the accuracy or completeness of the information contained herein. To the extent permitted by applicable law, CA provides this document as is without warranty of any kind, including, without limitation, any implied warranties of merchantability, fitness for a particular purpose, or noninfringement. In no event will CA be liable for any loss or damage, direct or indirect, from the use of this document, including, without limitation, lost profits, business interruption, goodwill or lost data, even if CA is expressly advised in advance of the possibility of such damages. A l id d i thi t ti f ill t ti l d t il fl ti f th Any examples provided in this presentation are for illustrative purposes only and are not necessarily reflective of the results you can be expected to achieve.

13 Thank you