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 learn
You 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:
test scenario management
Who this book is for
This 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.
Table of contents
- About the Authors
- About the Technical Reviewer
- Prologue: Virtually There at Fedex®
- Chapter 1: Introduction
- Chapter 2: The Business Imperatives: Innovate or Die
- Chapter 3: How We Got Here
- Chapter 4: Constraints: The Enemy of Agility
Chapter 5: What Is Service Virtualization?
- The Other Half of Virtualization
- Creation of a Virtual Service
- Options for Creating and Maintaining Virtual Services
- What Can You Make into a Virtual Service?
- Virtual Environments Are Better than Real Environments for Dev and Test
- Wait a minute—is this Virtual Service Environment replacing the live environment all the way up to production?
- Chapter 6: Capabilities of Service Virtualization Technology
Chapter 7: Where to Start with Service Virtualization?
- IT Executives Must Manage and Incentivize SV, or It Won’t Happen
- A transition may be painful—so how do I break this to my teams?
- Identify Stakeholders (The SV War Council)
- Who Should Use Service Virtualization First?
- Set Real Value Goals for Releases
- How does my company expect to create value from Service Virtualization?
- Avoid Inappropriate Technologies
- SV does not replace your ALM software
- More than a simplistic “record-playback” tool
- Will not require a specific vendor integration or business application platform
- Chapter 8: Best Practice 1: Deliver Faster
- Chapter 9: Best Practice 2: Reduce Your Infrastructure Footprint
- Chapter 10: Best Practice 3: Transform Performance and Scale
- Chapter 11: Best Practice 4: Data Scenario Management
Chapter 12: Rolling Out Service Virtualization
- The Stakes for Service Virtualization are Huge, So Don’t Settle
- But what about the risk? Won’t this create upheaval in my organization?
- Changes to the Software Development Lifecycle Process (SDLC)
- Build New Skills and Roles in a Virtual IT World
- Good Help Is Virtually Always in Demand
- Should We Centralize or Federate?
- Cool Alternative Use: Virtual Training Environments?
- Chapter 13: Service Virtualization and DevTest Cloud
- Chapter 14: Assessing the Value
- Chapter 15: Conclusion
- Afterword: Virtual Confession
- Title: Service Virtualization: Reality Is Overrated
- Release date: September 2012
- Publisher(s): Apress
- ISBN: 9781430246718
You might also like
Building modern distributed applications consisting of many independent, interconnected components puts a real stress on the …
The Three Value Conversations: How to Create, Elevate, and Capture Customer Value at Every Stage of the Long-Lead Sale
The three conversations B2B sale pros must have with customers to control every step of long …
The Government Manager's Guide to the Work Breakdown Structure
The Government Manager's Guide to the Work Breakdown Structure The work breakdown structure (WBS) is a …
Achieving DevOps: A Novel About Delivering the Best of Agile, DevOps, and Microservices
Ben is stuck. A development lead with a strong vision for how the intersection of development …