Step chart - Cloud testing steps

This step diagram example shows cloud testing steps. It was redesigned from the Wikimedia Commons file: Cloud Testing steps.png. [commons.wikimedia.org/ wiki/ File:Cloud_ Testing_ steps.png]
This file is licensed under the Creative Commons Attribution-Share Alike 3.0 Unported license. [creativecommons.org/ licenses/ by-sa/ 3.0/ deed.en]
"Cloud testing is a form of software testing in which web applications use cloud computing environments (a "cloud") to simulate real-world user traffic. ...
Cloud Testing uses cloud infrastructure for software testing. Organizations pursuing testing in general and load, performance testing and production service monitoring in particular are challenged by several problems like limited test budget, meeting deadlines, high costs per test, large number of test cases, and little or no reuse of tests and geographical distribution of users add to the challenges. Moreover ensuring high quality service delivery and avoiding outages requires testing in one's datacenter, outside the data-center, or both. Cloud Testing is the solution to all these problems. Effective unlimited storage, quick availability of the infrastructure with scalability, flexibility and availability of distributed testing environment reduce the execution time of testing of large applications and lead to cost-effective solutions." [Cloud testing. Wikipedia]
The step chart example "Cloud testing steps" was created using the ConceptDraw PRO diagramming and vector drawing software extended with the Marketing Diagrams solution from the Marketing area of ConceptDraw Solution Park.

This example of cloud computing system architecture diagram was created on base of the figure "Workflow to distribute workitems to pooled VMs" in the article "Azure Batch technical overview" from the Microsoft Azure website.
"Workitems workflow.
Figure 4 shows a you how to submit an application to a pool where it's distributed for processing. This uses the Batch API. ...
1. Upload input files (such as source data or images) required for a job to an Azure storage account. These files must be in the storage account so that the Batch service can access them. The Batch service loads them onto a TVM when the task runs.
2. Upload the dependent binary files to the storage account. The binary files include the program that is run by the task and the dependent assemblies. These files must also be accessed from storage and are loaded onto the TVM.
3. Create a pool of TVMs, specifying the size of the TVMs in the pool, the OS they run, and other properties. When a task runs, it is assigned a TVM from this pool.
4. Create a workitem. A job will be automatically created when you create a workitem. A workitem enables you to manage a job of tasks.
5. Add tasks to the job. Each task uses the program that you uploaded to process information from a file you uploaded.
6. Run the application and monitor the results of the output." [azure.microsoft.com/ en-us/ documentation/ articles/ batch-technical-overview/ ]
The diagram example "Workitems workflow diagram" was created using ConceptDraw PRO diagramming and vector drawing software extended with the Azure Architecture solution from the Computer and Networks area of ConceptDraw Solution Park.

This Azure cloud architecture pattern diagram template was created on the base of figure in the article "Health Endpoint Monitoring Pattern" from the Microsoft Developer Network (MSDN) website.
"Health Endpoint Monitoring Pattern.
Implement functional checks within an application that external tools can access through exposed endpoints at regular intervals. This pattern can help to verify that applications and services are performing correctly. ...
It is good practice—and often a business requirement—to monitor web applications, and middle-tier and shared services, to ensure that they are available and performing correctly. However, it is more difficult to monitor services running in the cloud than it is to monitor on-premises services. ...
Implement health monitoring by sending requests to an endpoint on the application. The application should perform the necessary checks, and return an indication of its status.
A health monitoring check typically combines two factors: the checks (if any) performed by the application or service in response to the request to the health verification endpoint, and analysis of the result by the tool or framework that is performing the health verification check. The response code indicates the status of the application and, optionally, any components or services it uses. The latency or response time check is performed by the monitoring tool or framework." [msdn.microsoft.com/ ru-RU/ library/ dn589789.aspx]
The Azure cloud system architecture diagram template "Health endpoint monitoring pattern" for the ConceptDraw PRO diagramming and vector drawing software is included in the Azure Architecture solutin from the Computer and Networks area of ConceptDraw Solution Park.

This example of cloud computing system architecture diagram was created on the base of picture in the article "What is StorSimple?" by Sharon Smith from the Microsoft Azure website.
"Microsoft Azure StorSimple is an efficient, cost-effective, and manageable solution that eliminates many of the issues and expense associated with enterprise storage and data protection. It uses a proprietary device (the Microsoft Azure StorSimple device) and integrated management tools to provide a seamless view of all enterprise storage, including cloud storage." [azure.microsoft.com/ en-us/ documentation/ articles/ storsimple-overview/ ]
The diagram example "Microsoft Azure StorSimple architecture" was created using ConceptDraw PRO diagramming and vector drawing software extended with the Azure Architecture solution from the Computer and Networks area of ConceptDraw Solution Park.