Azure Storage

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.

"Microsoft SharePoint is a Web application platform developed by Microsoft. First launched in 2001, SharePoint has historically been associated with intranet, content management and document management, but recent versions have significantly broader capabilities.
SharePoint comprises a multipurpose set of Web technologies backed by a common technical infrastructure. By default, SharePoint has a Microsoft Office-like interface, and it is closely integrated with the Office suite. The web tools are designed to be usable by non-technical users. SharePoint can be used to provide intranet portals, document & file management, collaboration, social networks, extranets, websites, enterprise search, and business intelligence. It also has system integration, process integration, and workflow automation capabilities.
Enterprise application software (e.g. ERP or CRM packages) often provide some SharePoint integration capability, and SharePoint also incorporates a complete development stack based on web technologies and standards-based APIs. As an application platform, SharePoint provides central management, governance, and security controls for implementation of these requirements. The SharePoint platform integrates directly into IIS - enabling bulk management, scaling, and provisioning of servers, as is often required by large organizations or cloud hosting providers." [Microsoft SharePoint. Wikipedia]
The AWS architecture diagram example "SharePoint server reference architecture for public-facing website scenario" was created using the ConceptDraw PRO diagramming and vector drawing software extended with the AWS Architecture Diagrams solution from the Computer and Networks area of ConceptDraw Solution Park.

This work flow chart sample was redesigned from the picture "Weather Forecast" from the article "Simulation Workflows".
[iaas.uni-stuttgart.de/ forschung/ projects/ simtech/ sim-workflows.php]
"(1) The weather is predicted for a particular geological area. Hence, the workflow is fed with a model of the geophysical environment of ground, air and water for a requested area.
(2) Over a specified period of time (e.g. 6 hours) several different variables are measured and observed. Ground stations, ships, airplanes, weather balloons, satellites and buoys measure the air pressure, air/ water temperature, wind velocity, air humidity, vertical temperature profiles, cloud velocity, rain fall, and more.
(3) This data needs to be collected from the different sources and stored for later access.
(4) The collected data is analyzed and transformed into a common format (e.g. Fahrenheit to Celsius scale). The normalized values are used to create the current state of the atmosphere.
(5) Then, a numerical weather forecast is made based on mathematical-physical models (e.g. GFS - Global Forecast System, UKMO - United Kingdom MOdel, GME - global model of Deutscher Wetterdienst). The environmental area needs to be discretized beforehand using grid cells. The physical parameters measured in Step 2 are exposed in 3D space as timely function. This leads to a system of partial differential equations reflecting the physical relations that is solved numerically.
(6) The results of the numerical models are complemented with a statistical interpretation (e.g. with MOS - Model-Output-Statistics). That means the forecast result of the numerical models is compared to statistical weather data. Known forecast failures are corrected.
(7) The numerical post-processing is done with DMO (Direct Model Output): the numerical results are interpolated for specific geological locations.
(8) Additionally, a statistical post-processing step removes failures of measuring devices (e.g. using KALMAN filters).
(9) The statistical interpretation and the numerical results are then observed and interpreted by meteorologists based on their subjective experiences.
(10) Finally, the weather forecast is visualized and presented to interested people." [iaas.uni-stuttgart.de/ forschung/ projects/ simtech/ sim-workflows.php]
The example "Workflow diagram - Weather forecast" was drawn using the ConceptDraw PRO diagramming and vector drawing software extended with the Workflow Diagrams solution from the Business Processes area of ConceptDraw Solution Park.