The document discusses the need for enterprise agile development to utilize service virtualization and virtual environments. It notes that increasing complexity from interconnected systems and components has made achieving agile goals like rapid iterations and releases difficult due to realities like schedule conflicts between teams. Service virtualization provides simulated services that allow development to proceed independently of dependencies, avoiding delays. This allows teams to shift testing activities earlier in the development cycle for faster delivery and fewer defects. Examples of how service virtualization has helped customers reduce infrastructure costs and development cycles are also provided.

1. Reality is Overrated:
Enterprise Agile Requires a
Virtual World
John Michelsen
CTO, CA Technologies

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?
Copyright © 2012 CA. All rights reserved.

3. changes in software development
Constraints Composite
Complexity (Custom Applications,
Costs SOA, Cloud)
Client/Server
(Packaged Apps such as SAP, Siebel, Oracle…)
Mainframe
… 1980 … 1985 … 1990 … 1995 … 2000 … 2005 … 2010 … 2015
Copyright © 2012 CA. All rights reserved.

4. Change and Complexity Increasing
CRM Routing Help
App Collaboration Web Service Engine
Portal Virtual Web/WAP BI Tools
App Interface Service Interface
External Partners Cloud
Content
Database
Business EJB
SOAP Rules
ESB
Data Internal
Warehouse
Legacy BPMS File
Products System
Infrastructure
Messaging
Financials
Service RMI Objects
Mainframe
# of Interconnected # of Heterogeneous
# of Interdependent Teams Rate of Change
Components Technologies

5. I said REALLY complex

6. Agile goals move out of reach due to reality
Agile Goal: Faster iterations and releases
Dev 1 (Goal: rapid releases and
Integration check-ins, faster delivery)
Dev 2 Performance
UAT
Dev 3
Reality: Schedule conflicts make Agile become Waterfall
Dev 1 Dev 1a
Dev 2 Integration Performance UAT
Dev 3
New Dev 33
New Dev Waiting for
Waiting for Conflicts
Conflicts Teams
Teams
release
release Dev 22to
Dev to appear at
appear at waiting for
waiting for
affects Dev 11
affects Dev complete
complete Integration
Integration environments
environments

7. the big problem: constraints
INCOMPLETE
DEVELOPMENT
ESB
ACCESS FEES
SYSTEM MAINFRAME DATA LEGACY EXTERNAL
UNAVAILABLE
INVALID DATA
“I can’t do anything until I have everything… and I never have everything!”
Copyright © 2012 CA. All rights reserved.

8. solution: service virtualization
ESB
MAINFRAME DATA LEGACY EXTERNAL
Copyright © 2012 CA. All rights reserved.

9. Meditation: Service Virtualization is like…
 The Holodeck in Star Trek
 A fake Wild West Town
 Complete with stuntmen to shoot at
 An Electronics Test Harness
But our favorite is…
Patagonia, Argentina 2008. Photo: Jason English

10. Flight and avionics simulation

11. service virtualization
how does it work?
1. Capture 2. Model 3. Simulate
Record conversation Client App
Client App Assign context with service virtualization
data, protocols used, to data, behavior as a “stand in” for
response times & performance development dependencies
App Current
App Current App Under
App Under
Version
Version Development
Development
Dev/Test teams
Listen to Live traffic
Listen to Live traffic
vMF1 vSaaS
Mainframe
Mainframe SaaS
Use SV for development
Use SV for development
Structured Conversations Heuristics Sophisticated Behavior
Observe & Understand Analytics Dynamic Properties (Dates, values, etc.)
Protocol-Level Algorithms Scenario Support
 Recorded traffic State Test Data Sanitation
 Design specs – e.g. WSDL Compiled Model vs. Stubs
 Sample RR pairs, byte code, logs, etc. Automatic Healing
11
Copyright © 2012 CA. All rights reserved.

12. where do we start?
3 common applications
Integration
Mergers and Acquisitions
“Business-in-a-Box”
Application Modernization
Deadline Critical
Value Release
SDLC Optimization Opportunities
Parallel Development
Performance Engineering
Hardware Reduction
Confidence in Application Scalability
12
Copyright © 2012 CA. All rights reserved.

13. constraint: schedule conflicts
“shift-left” the SDLC
Without LISA Uncertain delivery schedule – defects persist until UAT
Dev Dev Dev Dev Dev Dev Dev Dev
1 2 1 2 1 3 2 3 System Test Integration
With CA LI SA more effort Typical composite app today waits
moved sooner in the lifecycle for whole assembly to begin
With LISA
Dev1
Dev2
Dev3 Reduction in SDLC
Faster Rollout
System
Integration
Performance
UAT
Copyright © 2012 CA. All rights reserved.

14. sample report card: Shift-Left at Sprint
wk5 wk6 wk7 wk8 wk9 wk10 wk11 wk12 wk13 wk14 wk15 wk16 wk17 wk18 wk19
Project Phases
Setup Shakeout
Integrated System Test UAT Pass 1
Dev Unit System Test UAT Pass 2
Mainframe ST
80 Virtual Service back
80 Virtual Service back Automated shakeout
Automated shakeout Earlier test phases with
Earlier test phases with
MF Delivery ends delivered for ST happens 2 weeks
happens 2 weeks fewer defects to fix
fewer defects to fix
ends delivered for ST
earlier
earlier
Targeted Release Cycle
• 2-week system test and Integration test savings in first project
• 400% more effective defect elimination due to early coverage of
environment
Copyright © 2012 CA. All rights reserved.

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

16. constraint: system availability
Performance readiness
BEFORE AFTER
Shared
Mainframe
Service
Or similar
heavy-weight
implementation
environment
 Constraints affecting performance team
productivity, with inability to isolate flaws  One customer achieved 300% more
performance coverage and avoided $30+
 High costs to build and maintain stubs with million in new infrastructure investment
only limited functionality
Copyright © 2012 CA. All rights reserved.

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

18. customer successes
Large US Telco – Popular cell phone launch
Reduced software release cycle time by 33%
400% increase in defects identified
4 weeks to achieve 100%+ ROI – $1.6M
Major US Financial Services Company – 3rd Party Access
Avoided $700k investment in additional hardware on 1st project
Avoided 95% of non-production 3rd party access fees
Eliminated delays related to 3rd party dependencies from SDLC
8 weeks to 100%+ ROI
Major US Bank – Performance Engineering
8 days to replace 2 years of custom-coded stubs
Avoided $30M Y1 in lab upgrades, >$90M to date
Increased quality from 3.7 to 5.1 Sigma in single release.
Reduced outsourced testing headcount from 45 to 7.
Increased team scalability from supporting 5 apps to 140.

19. Nirvana: Agile, continuous delivery has to be application
lifecycle oriented
App1-Dev
App1-Dev App1-ST
App1-ST
SIT
SIT
App2-Dev
App2-Dev App2-ST
App2-ST PROD
PROD
PERF
PERF
App3-Dev
App3-Dev App3-ST
App3-ST
 Follows the customer’s development cycle (Dev, SysTest, Integration, Prod)
 Supports Environment contents that are different by stage and by Team
 Allows for Environment Refresh and Environment Promotion
 Allows for coordination/synchronization of promotions
 Provides full auditability, rollback, reproduction, and redeployment
 Deploys to any/all possible targets: existing, Cloud Provisioning, Run Book

20. Service Virtualization: Reality is Overrated
 Get your copy at the CA Tap & Brew
(Booth 101 Moscone South – while supplies last)
 Signing 11:30 AM – 1:00 PM today!
 Updates and more at the SV community, see
http://ServiceVirtualization.Com/book
Copyright © 2012 CA. All rights reserved.

21. Notices
Copyright © 2012 CA. All rights reserved. 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 CA software 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.
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.

22. Thank you