More than four years ago, we released the first version of LISA's Service Virtualization capabilities because we saw a fundamental roadblock occurring at almost every one of our enterprise customers. Sure, they were more efficiently automating functional, regression and performance testing with LISA, but inevitably, teams would complain that they still weren't becoming as "Agile" as they hoped. They were losing productivity due to constraints brought on by other parties they were connected to: partners and other dev teams that either didn't complete their delivery yet, or limited access to their systems.
This is why I'm excited to introduce this new paper I wrote for our 4-part joint IT Thought Leaders Whitepaper Series with our partners at Infosys:
Key Capabilities of a Service Virtualization Solution (Download PDF)
Eliminating Software Development and Testing Constraints by Virtualizing Away Dependencies in the Environment
We have to face the fact that no development team can build and test software in isolation anymore, using repurposed client-server tools. Software lifecycles are becoming increasingly composite and service-based, while an increasing number of smaller, agile teams created interdependencies that must be addressed with a new kind of virtualization - something we called Service Virtualization: the simulation of constrained or unavailable systems for continuous availability throughout the software development and testing lifecycle.
Service Virtualization is now maturing into a widely adopted technology, with many technology vendors embedded, and a market to support it. There are key capabilities any advanced enterprise dev and test team will need to have in a "live-like" virtual service environment that is as close to the real thing as it needs to be, without the constraints of excess coding, maintenance and reliance on big-iron systems to deliver new competitive functionality.
This paper is a good read if you are wondering where Service Virtualization technology has advanced over the last few years. It's not just about replacing the "stubs and mocks" developers used to hand-code with more pat request/responses. Today's apps have become far too interdependent, and fast-changing for that to be sufficient. Testers and developers must be able to recreate complex, composite workflows in an environment that looks and acts just like the real thing.
A smart counterpart at Infosys, Vijay Sairam Pratap, just commented on the story with a very compelling, clear anecdote about the level of realism needed from Service Virtualization to enable robust service assurance in his latest blog from an HP conference. We'll talk about that example, and a couple other newer real-world stories in our next post.
Link to Service Virtualization Capabilities whitepaper download page: http://www.itko.com/resources/service_virtualization_solution.jsp

Sun has tried very hard to attract developers, lately, open sourcing as much as they could - but open source is a hard space to compete in because it doesn't generate cash! By hugely funding Eclipse, IBM spoiled the IDE market for Sun and a number of other players.
Still this will be an interesting development to watch, as we are talking about a boatload of innovations and 2 very different cultures that would need to be folded together here."