Service Virtualization [electronic resource] : Reality Is Overrated /
Michelsen, John.author.
English, Jason.author.
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. Service Virtualization is a method to emulate the behavior of  components in heterogeneous applications such as "Service-Oriented Architectures" (SOA). 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.
Title Page; Copyright Page; Table of Contents; About the Authors; About the Technical Reviewer; Acknowledgments; PROLOGUE Virtually There at FedEx®; CHAPTER 1 Introduction; Service Virtualization Defined; You Make the Transformation Happen; About This Book; Signposts in the Book; CHAPTER 2 The Business Imperatives: Innovate or Die; Consumers Have No Mercy; Business Demands Agile Software Delivery; Increased Change and Complexity Are Inevitable; Business Software Cannot Sustain without Simulation; CHAPTER 3 How We Got Here; From Monolithic to Composite Apps
Today's Complex Service EnvironmentsFrom Waterfall to Agile Development; CHAPTER 4 Constraints: The Enemy of Agility; In-Scope vs. Out-of-Scope; Unavailable Systems and Limited Capacity; Conflicting Delivery Schedules; Are developers coding in the blind?; Data Management and Volatility; Third-Party Costs and Control; Stubs and Mocks Are Not Enough; 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 TestWait a minute-is this Virtual Service Environment replacing the live environment all the way up to production?; CHAPTER 6 Capabilities of Service Virtualization Technology; "Live-Like" Development Environment; Expected Capabilities; Automation Eliminates Manual Stubbing and Maintenance; Virtual Service, Heal Thyself; Expected Capabilities; Enables Parallel Dev and Test; 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?; Involve experienced resources for starters.; 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; Intermission; CHAPTER 8 Best Practice 1: Deliver Faster
Reducing Wait Time through Virtual PrivacyKill Stubs Now, or Pay Later; Sprint: Putting Shift-Left in Practice; CHAPTER 9 Best Practice 2: Reduce Your Infrastructure Footprint; Finding Over-Utilized Resources; Mainframe Development Needs Virtualization Too; Avoiding Big IT Outlays; Customer Example: Dodging a Wave; CHAPTER 10 Best Practice 3: Transform Performance and Scale; Virtualizing Performance Environments: Are You Waiting to Fail?; Component-Level Performance Budgeting; Informing Performance from Production; Setting Thresholds to Move Performance Even Farther Left Than We Ever Imagined
Performance Testing by Design
Includes index.
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. Service Virtualization is a method to emulate the behavior of  components in heterogeneous applications such as "Service-Oriented Architectures" (SOA). 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.
Computer input-output equipment.
Special purpose computers.
Hardware and Maker.
Special Purpose and Application-Based Systems.