NIH IT enterprise architecture framework

This enterprise architecture diagram sample was redesigned from the illustration of the NIH Enterprise Architecture website. [enterprisearchitecture.nih.gov/ Pages/ Framework.aspx]
"Enterprise architecture is a comprehensive framework used to manage and align an organization's Information Technology (IT) assets, people, operations, and projects with its operational characteristics. In other words, the enterprise architecture defines how information and technology will support the business operations and provide benefit for the business.
It illustrates the organization’s core mission, each component critical to performing that mission, and how each of these components is interrelated. These components include:
(1) Guiding principles,
(2) Organization structure,
(3) Business processes,
(4) People or stakeholders,
(5) Applications, data, and infrastructure,
(6) Technologies upon which networks, applications and systems are built.
Guiding principles, organization structure, business processes, and people don’t sound very technical. That’s because enterprise architecture is about more than technology. It is about the entire organization (or enterprise) and identifying all of the bits and pieces that make the organization work." [enterprisearchitecture.nih.gov/ Pages/ what.aspx]
The example "NIH IT enterprise architecture framework" was created using the ConceptDraw PRO diagramming and vector drawing software extended with the Enterprise Architecture Diagrams solution from the Management area of ConceptDraw Solution Park.

This Azure cloud architecture pattern diagram template was created on the base of figure in the article "Valet Key Pattern" from the Microsoft Developer Network (MSDN) website.
"Valet Key Pattern.
Use a token or key that provides clients with restricted direct access to a specific resource or service in order to offload data transfer operations from the application code. This pattern is particularly useful in applications that use cloud-hosted storage systems or queues, and can minimize cost and maximize scalability and performance. ...
Client programs and web browsers often need to read and write files or data streams to and from an application’s storage. ...
Data stores have the capability to handle upload and download of data directly, without requiring the application to perform any processing to move this data, but this typically requires the client to have access to the security credentials for the store.
... applications must be able to securely control access to data in a granular way, but still reduce the load on the server by setting up this connection and then allowing the client to communicate directly with the data store to perform the required read or write operations. ...
To resolve the problem of controlling access to a data store where the store itself cannot manage authentication and authorization of clients, one typical solution is to restrict access to the data store’s public connection and provide the client with a key or token that the data store itself can validate.
This key or token is usually referred to as a valet key. It provides time-limited access to specific resources and allows only predefined operations such as reading and writing to storage or queues, or uploading and downloading in a web browser. Applications can create and issue valet keys to client devices and web browsers quickly and easily, allowing clients to perform the required operations without requiring the application to directly handle the data transfer. This removes the processing overhead, and the consequent impact on performance and scalability, from the application and the server." [msdn.microsoft.com/ ru-RU/ library/ dn568102.aspx]
The Azure cloud system architecture diagram template "Valet key 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.