Apress, 2012. - 152 p.
ISBN: 1430246715
Software drives innovation and success in today’s business world. Yet critical software projects consistently come in late, defective, and way over budget. So what’s the problem?
Get ready for a shock, because the answer to the problem is to avoid reality altogether. A new IT practice and technology called Service Virtualization (SV) is industrializing the process of simulating everything in our software development and test environments. Yes, fake systems are even better than the real thing for most of the design and development lifecycle, and SV is already making a huge impact at some of the world’s biggest companies.
Service Virtualization: Reality Is Overrated is the first book to present this powerful new method for simulating the behavior, data, and responsiveness of specific components in complex applications. By faking out dependency constraints, SV delivers dramatic improvements in speed, cost, performance, and agility to the development of enterprise application software.
Writing for executive and technical readers alike, SV inventor John Michelsen and Jason English capture lessons learned from the first five years of applying this game-changing practice in real customer environments. Other industries — from aviation to medicine — already understand the power of simulation to solve real-world constraints and deliver new products to market better, faster, and cheaper. Now it’s time to apply the same thinking to our software.
For more information, see servicevirtualization.com.
What you’ll learnYou will learn why, when, where, and how to deploy service virtualization (SV) solutions to mitigate or eliminate the constraints of an unavailable or unready service system by simulating its dependent components in order to deliver better enterprise software faster and at lower cost. In particular, you will learn step-by-step why, when, where, and how to deploy the following SV solutions:
shift-left
infrastructure availability
performance readiness
test scenario management
Who this book is forThis book is not only for IT practitioners on engineering, testing, and environments teams engaged in the development and delivery of enterprise software, but also for executives of companies in all sectors who need to understand and implement emergent opportunities to improve the time to market and overall competitiveness of any outward-facing business strategy that has a software application component.
John Michelsen is the chief technology officer and cofounder of ITKO/Ca Technologies. Before forming ITKO, he was director of development at Trilogy Inc. He is the chief architect of the LISA service virtualization and automated validation platform and a leading industry advocate and consultant for lifecycle optimization of enterprise applications. His clients include Xerox, Cendant Financial, Microsoft, American Airlines, Union Pacific, Raima, Sabre, and Nielsen Market Research. Michelsen holds numerous patents in such areas as service-oriented architectures, object-oriented database management systems, middleware, model-driven architectures, and cloud. He presents regularly at IT and software development events, including SOA World, Infoworld SOA Summit, STAReast, Better Software, IBM Impact, SD West, TUCON, SoftwareAG Integration World, Cloud Computing Summit, TD Summit, and Software Test & Performance. Michelsen contributes frequently to IT publications, such as Virtualization Journal, SD Times, Software Test & Performance, SIGNAL DoD Monthly, Dr. Dobb’s, and Software Development.
Jason English is vice president of marketing communications at ITKO/CA Technologies. He was previously an executive producer at i2 Technologies and an information architect for such Fortune 500 clients as HP, IBM, EDS, Delphi, TaylorMade, Sun, Realm, Adaptec, Motorola, and Sprint. He has designed and scored computer games and produced conventional advertising and television commercials. English contributes to many IT publications and presents at IT and software development events, including iqnite Australia, STARwest, BEAworld, Java Developer Summit, and Retail Supply Chain Forum.
Foreword by Burt Klein
● Service Virtualization Briefly Defined
● Key Practices Enabled by SV
●● Shift-Left
●● Infrastructure Availability
●● Performance Readiness
●● Test Scenario Management
● Navigating This Book
The Business Imperative: Innovate or Die
● Consumers Have No Mercy
● Business Demands Agile Software Delivery
● Increased Change and Complexity for IT
● Simulation Is Not Just for Other Industries
How We Got Here
● From Monolithic to Composite Apps
● Today’s Complex Service Environments
● From Waterfall to Agile Development
Constraints: The Enemy of Agility
● Unavailable Systems and Environments
● Conflicting Delivery Schedules
● Data Management and Volatility
● Third-party Costs and Control
What is Service Virtualization?
● The Opposite of Server Virtualization
● Creation of a Virtual Service
● Maintaining Virtual Services
● What Kinds of Things You Can virtualize
● Virtual Service Environments (VSEs)
Where to Start with SV?
● Pick a Hairy Problem
● Identify Stakeholders
● Set Real Value Goals for Releases
● Avoid Inappropriate Technologies
Capabilities of Service Virtualization Technology
● Live-Like Development Environment
● Automation Eliminates Manual Stubbing and Maintenance
● Enables Parallel Dev and Test
●● No more Availability Problem
●● Platform-Neutrality
Best Practice #1: Shift-Left
● Reducing Wait Time
● Early Component and System Testing
●● Define SV from Capture
●● Define Incomplete SV from Requirements
● Expected Results ● Customer Example
Best Practice #2: Infrastructure Availability
● Finding Over-Utilized Resources
● Virtualizing Mainframes
● Avoiding Big IT Outlays
● Expected Results
● Customer Example
Best Practice #3: Performance Readiness
● Virtualizing Performance Environments
● Informing Performance from Production
● Expected Results ● Customer Example
Best Practice #4: Test Scenario Management
● Managing Big Data
● Shielding Teams from Volatility
● Massively Parallel Regression Testing
● Expected Results
● Customer Example
Rolling out Service Virtualization
● Who Pays for Service Virtualization?
● Overcoming Organizational Challenges
●● Who Manages a VSE?
●● Should I Have More Than One?
● Key Skills and Roles in a Virtual IT World
Service Virtualization in the DevTest Cloud
● Constraints of Cloud Dev and Test
● Achieving Elastic Cloud Environments
Assessing the Value
● Key Metrics for Success
● Areas for Improvement
● The Industrialized Software Supply Chain
● Innovate and Thrive
● What’s Next for SV?