Enterprise Architecture Diagrams

This enterprise architecture diagram sample was drawn on the base of the figure illustrating the webpage "Enterprise Architecture" from the United States Department of Agriculture (USDA) website.
"The USDA's Enterprise Architecture program strategically partners with all agencies to provide value to USDA's mission areas, business processes, and Information Technology (IT) capabilities.
Introduction.
The USDA Enterprise Architecture (EA) helps make sure information technology investments align with the mission and goals of the Department. It defines how information and technology should support USDA’s strategic goals and benefit the business.
Purpose.
The intent of the USDA Enterprise Architecture is to help make the information technology (IT) expenditures more effectively serve the mission and goals of the organization. Enterprise architecture defines how information and technology support USDA’s strategic planning to benefit our business. There are many ways to organize the information and diagrams that make up the architecture."
[ocio.usda.gov/ about-ocio/ governance-and-strategic-investment-gsi/ enterprise-architecture]
The enterprise architecture diagram example "USDA's Enterprise Architecture" 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 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 enterprise architecture (EA) metamodel diagram example was redesigned from the illustration of article " helicopters and metamodels take 2".
"This is a “helicopter” level view – meant as a consulting and conversation guide for senior managers to help them place enterprise architecture appropriately in their strategic thinking."
www.achurchassociates.com/ 2012/ 10/ 16/ helicopters-and-metamodels-take-2/
from the website www.achurchassociates.com , with the kind permission of Ric Hayman.
The example "Enterprise architecture diagram" 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 enterprise architecture diagram sample was redesigned from the Wikimedia Commons file: Enterprise Architecture Domains Subdomains.jpg.
[commons.wikimedia.org/ wiki/ File:Enterprise_ Architecture_ Domains_ Subdomains.jpg]
An enterprise architecture’s landscape is usually divided into various domains based on the attributes of the environment and the logical grouping based on Industry EA Frameworks.
Enterprise Architecture consists of 5 domains: Business, Application, Information, and Technical (Infrastructure and Telecom).
The example "Enterprise architecture domains" 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 enterprise architecture diagram sample was redesigned from the Wikipedia file: TEAF Work Products for EA Direction, Description, and Accomplishment.jpg. [en.wikipedia.org/ wiki/ File:TEAF_ Work_ Products_ for_ EA_ Direction,_ Description,_ and_ Accomplishment.jpg]
"Treasury Enterprise Architecture Framework (TEAF) was an Enterprise architecture framework for treasury, based on the Zachman Framework. It was developed by the US Department of the Treasury and published in July 2000. May 2012 this framework has been subsumed by evolving Federal Enterprise Architecture Policy as documented in "The Common Approach to Federal Enterprise Architecture".
The material presented here is obsolete and only useful for historical reference and is not the current policy in use by the Department of the Treasury." [en.wikipedia.org/ wiki/ Treasury_ Enterprise_ Architecture_ Framework]
The enterprise architecture diagram example "Resources and TEAF Work Products for EA Direction, Description, and Accomplishment" 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.