In my previous post, we talked about tools in software engineering being either strategic purchases OR cost controllers (I’m ignoring the case of the folks who are in status quo and don’t want to do anything to improve their software engineering processes). This post will talk about how you can make the case for virtual lab automation (VLA) to be a strategic purchase in your software lab.
Rationalization for VLA as a Strategic Purchase in Your Software Engineering Environment
VLA is a strategic tool for consideration in your environment if:
- There is a pressing need in your industry to bring software products/systems to market and users faster. OR
- There is a pressing need in your industry to roll out high quality software everytime, i.e., there is a low tolerance for bugs reported in the field.
If you are faced with either of these challenges in your software development process and are looking for strategic purchase options, then read on.
Justifying VLA as a Strategic Purchase For Your Software Engineering Process
So, what do VLA tools offer that can help you address strategic concerns around your software engineering process?
Strategic Concern #1 — Pressing need to bring software to market faster
What VLA Offers to address Concern #1
- Allow software engineers and testers to self serve their virtual environments — on demand from the private cloud. Here is another post that talks about self serve IT
- Rapidly create virtual environments — in a completely automated manner (including setting up the software stack in the machines)
- Allow software engineering teams to collaborate and share virtual machines and other lab infrastructure
Strategic Concern #2 — Low tolerance for bugs reported in the field and a Pressing need for high quality software to be shipped
What VLA Offers to address Concern #2
- Leverage the ability to create virtual test environments rapidly and easily — to dramatically improve the number of test cases that you can execute. Don’t waste time creating and re-creating test environment infrastructure
- Leverage VLA tool integrations with test tools like HP Quality Center and IBM Rational Quality Manager etc. These tools rely on VLA for the creation and management of virtual environments in which the test cases are executed
- Bring the field environments in! That is, don’t wait to test on field like environments. Use VLA to replicate field like conditions (including the networking setup etc.) to test your software. That way there are fewer surprises in terms of bugs reported from the field
In my next post, we’ll talk about how VLA can be a significant cost controller as well.
- Business Geeks: Automated Software Testing as Competitive Advantage
- Poor software testing hits companies in the pocket – article in Infoworld and Network World