Software drives innovation and success in todayas business world. Yet critical software projects consistently come in late, defective, and way over budget. So whatas 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 worldas 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 industriesafrom aviation to medicineaalready understand the power of simulation to solve real-world constraints and deliver new products to market better, faster, and cheaper. Now itas time to apply the same thinking to our software. For more information, see servicevirtualization.com. What youall 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 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 ContentsForeword by Burt Klein Chapter 1. Introduction a Service Virtualization Briefly Defined a Key Practices Enabled by SV aa Shift-Left aa Infrastructure Availability aa Performance Readiness aa Test Scenario Management a Navigating This Book Chapter 2. The Business Imperative: Innovate or Die a Consumers Have No Mercy a Business Demands Agile Software Delivery a Increased Change and Complexity for IT a Simulation Is Not Just for Other Industries Chapter 3. How We Got Here a From Monolithic to Composite Apps a Todayas Complex Service Environments a From Waterfall to Agile Development Chapter 4. Constraints: The Enemy of Agility a Unavailable Systems and Environments a Conflicting Delivery Schedules a Data Management and Volatility a Third Party Costs and Control Chapter 5. What is Service Virtualization? a The Opposite of Server Virtualization a Creation of a Virtual Service a Maintaining Virtual Services a What Kinds of Things You Can virtualize a Virtual Service Environments (VSEs) Chapter 6. Where to Start with SV? a Pick a Hairy Problem a Identify Stakeholders a Set Real Value Goals for Releases a Avoid Inappropriate Technologies Chapter 7. Capabilities of Service Virtualization Technology a Live-Like Development Environment a Automation Eliminates Manual Stubbing and Maintenance a Enables Parallel Dev and Test aa No more Availability Problem aa Platform-Neutrality Chapter 8. Best Practice #1: Shift-Left a Reducing Wait Time a Early Component and System Testing aa Define SV from Capture aa Define Incomplete SV from Requirements a Expected Results a Customer Example Chapter 9. Best Practice #2: Infrastructure Availability a Finding Over-Utilized Resources a Virtualizing Mainframes a Avoiding Big IT Outlays a Expected Results a Customer Example Chapter 10. Best Practice #3: Performance Readiness a Virtualizing Performance Environments a Informing Performance from Production a Expected Results a Customer Example Chapter 11. Best Practice #4: Test Scenario Management a Managing Big Data a Shielding Teams from Volatility a Massively Parallel Regression Testing a Expected Results a Customer Example Chapter 12. Rolling out Service Virtualization a Who Pays for Service Virtualization? a Overcoming Organizational Challenges aa Who Manages a VSE? aa Should I Have More Than One? a Key Skills and Roles in a Virtual IT World Chapter 13. Service Virtualization in the DevTest Cloud a Constraints of Cloud Dev and Test a Achieving Elastic Cloud Environments Chapter 14. Assessing the Value a Key Metrics for Success a Areas for Improvement Chapter 15. Conclusion a The Industrialized Software Supply Chain a Innovate and Thrive a Whatas Next for SV? Glossary About the AuthorsSchedule conflicts make Agile become Waterfall Dev 1 Dev 1a l I I (a)alt;(aagt; | l Integration I Performance 5 UAT a#39;, a#39;F a#39;, aquot;v a#39;ra#39; ... Teams I 1 release I : Dev 2 to I : appear at I I waiting for I l l iL affects Dev 1 I i complete I L Integratlon I : environments Ianbsp;...
|Author||:||John Michelsen, Jason English|
|Publisher||:||Apress - 2012-09-26|