The current dynamic needs of business and volatile economy have led to organizations demanding CIOs to meet increasing business demands successfully, with shrinking budget allocations. Every CIO has started focusing and analyzing each and every IT division operation, significant investments made and subsequent ROI generated. One of the most significant elements that gets noticed and scrutinized is the QA infrastructure cost. This is because nearly 30 to 50% of servers in the organization are utilized by the QA teams, according to Cloud computing: Innovative solutions for test environments by IBM Global Services. Hence if these assets are underutilized, the investments in them are also underutilized, significantly impacting ROI.
The evolution of cloud has made organizations sit up and start thinking about how they can leverage the advantages of cloud as an infrastructure or as a platform or even as software, to overcome the challenges of today’s dynamic business and IT needs. In Cloud computing: Addressing software QA issues, we discussed the challenges associated with traditional QA environments and how cloud was a solution to overcome these challenges. In this article, we share an in-depth analysis of the various factors and explain the benefits that make QA environment the perfect place for CIOs to begin cloud adoption.
Use case evaluation for cloud adoption
Infosys recently embarked on research which evaluated the popular cloud use cases against parameters like business risk, business value, relative simplicity and cloud technology maturity for cloud adoption. The analysis covers the following cloud use cases in the forms of cloud as a software, platform and infrastructure:
SaaS (Software as a Service): Online collaboration solutions, enterprise applications and business/industry applications
PaaS (Platform as a Service): Web 2.0 applications, databases and middleware
IaaS (Infrastructure as a Service): Storage, server and networks, production custom applications and QA/DEV environments
The table below rates the typical cloud cases as High (H), Medium (M) or Low (L) against each parameter - business risk, business value, relative simplicity and cloud technology maturity.
By evaluating the ratings for each parameter, we will be able to deduce the most optimal use case for cloud adoption, from an overall perspective.
Table 1: The use case evaluation for cloud adoption
The business risk associated with migrating live applications into the cloud right away is quite high for organizations. If a failure occurs, it would have a direct and immediate impact on the business of the organization. However, cloud adoption with QA environments would be far more appropriate for organizations as the business risk associated with such an adoption was found to be comparatively lower when compared with other cloud use cases.
It is quite evident that business value of cloud adoption is quite high with the SaaS model when it covers enterprise applications such as CRM, ERP, etc. Organizations usually stand to gain immediately with SaaS as they get a ready-to-go market solution with a very short turnaround time. However, as per the table (Table 1), organizations also gain significantly with the SaaS model when leveraged in the form of cloud for their QA environment needs. This is because of the increased asset utilization, reduced proliferation, greater serviceability and greater agility with provisioning that cloud is able to provide for QA/Dev environments.
Relative simplicity or ease of implementation
SaaS and PaaS use cases require integration; secure authentication and secure policy enforcement which increases the complications during implementations. However, cloud adoption in QA environments stands out due to the relative ease in implementation.
Cloud technology maturity
Cloud technology has high maturity levels across:
- SaaS in the form of online collaboration solutions
- PaaS in the form of Web 2.0 applications and databases
- IaaS in the form of storage, server and networks and QA environments
The evolution of SalesForce CRM (form of SaaS), Windows Azure (form of PaaS), Amazon EC2 (form of IaaS) implies that cloud technology is mature because of the dynamic convergence of information technology, business model and consumer experience. These use cases are a good place to begin cloud adoption from a cloud technology maturity perspective.
The one use case that stands out distinctly and strongly, across all parameters, is the adoption of cloud in QA/Dev environments. Advantages such as increased asset utilization, reduced proliferation, greater agility in servicing requests and faster release cycle times, position QA environments as the most optimal use case for cloud adoption from an overall recommendation standpoint.
Benefits delivered by cloud-based QA environments
Let us now look into the key benefits delivered by cloud-based QA environments:
Dynamic and scalable provisioning
With cloud-based QA environments, organizations can quickly provision/de-provision virtual machines on demand, drastically reducing the provisioning time from several months to a few minutes. This ability to scale gives organizations an edge with high quality services and diverse QA environment requirements. It also helps business focus on core areas, by reducing the time spent on procurement operations.
Reduced time to market
Test cycles have always been seen as critical paths for release to production. Cloud adoption in a QA environment facilitates faster on-demand provisioning of resources, increase in productivity and shorter lifecycles for application development and testing, which significantly contributes to faster time to market. Interestingly in traditional QA environments, 30% of defects in production phase for an application were primarily due to wrongly configured test environments. Cloud eliminates this, thus reducing time to market immediately.
Greater environment control
With the cloud adoption for QA environments, multiple channels requesting QA environments for various projects are consolidated into a single channel, significantly reducing server and application sprawl. This leads to a better control over the environment.
Reduced TCO and improved resource utilization
The capability to share environments due to virtualization improves resource utilization, thus reducing associated costs of hardware and software licenses. Cloud-based QA environments bring in significant cost savings of almost 50% on IT support costs, helping organizations move from a CAPEX to an OPEX mode.
There is no doubt that the QA environment is an apt place for organizations to begin their cloud adoption journey. It is recommended that organizations explore and evaluate their internal QA environment infrastructure for conversion into a secure private enterprise cloud. In the event of unavailability of internal infrastructure, organizations need to partner and engage with an external cloud service provider, with the ability to provide the infrastructure for QA as a service in a pay-as-you-use model. Cost savings achieved through such infrastructure optimization can be reinvested by the organization into core business projects to bring in the much needed innovation to drive overall enterprise sustainability and market relevance.
Continue reading part three of this article: Determining the cloud model that best meets your business requirements.
How has your organization been using the cloud? Would you agree with the ratings identified in the cloud use case table in this article? Why or why not? Follow us on Twitter at @SoftwareTestTT and let us know what you thought of this article.
About the author:
Vijayanathan Naganathan (Vijayanathan_n@infosys.com) is a Senior Technology Architect with the Independent Validation & Testing Services Practice at Infosys. With 13 years of industry experience, he currently leads the Cloud and Service Virtualization service offerings for QA. His current work includes helping customers adopt cloud for QA environments, defining strategies and executing them for cloud based application validation. Vijay blogs at http://www.infosysblogs.com/testing-services/.
This was first published in February 2012