Enterprise Architecture Diagrams

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 diagram example was drawn on the base of the figure illustrating the webpage "ISE Enterprise Architecture Framework 2007" from the Semantic Community website. "The ISE Enterprise Architecture Framework.
As Figure ... depicts, the Federal Enterprise Architecture (FEA) Reference Models (RMs) provide the basis for the ISE EAF. All elements of the ISE EAF are mapped back to elements of the FEA RMs with the FEA management processes applied by the OMB leveraged in support of implementing the ISE. The four ISE EAF partitions are mapped to the five FEA RMs to enable tracking the development of the ISE EAF across agencies using standardized OMB policies and processes that structure EA development and budgeting processes. The ISE EAF also provides an overarching mapping of the ISE into not only Federal civil systems, but also national security systems. ...
Two primary views are used to describe the ISE EAF: 1) the Architect’s View and 2) the Implementer’s View. While the term “view” is typically used to refer to different aspects of an architecture, the OMB suggested the term “partition” rather than the more common terms “architecture” or “view” to differentiate the ISE approach as a framework from the approach typically used in departmental and agency EAs. The Architect’s View comprises four partitions:
1) Business,
2) Data,
3) Application and Service, and
4) Technical.
The Architect’s View is used to provide structural alignment of the ISE architectural components into the FEA structure to ensure strategies, business processes, investments, data, systems, and technologies within the ISE are integrated and compatible with those across the Federal government."
[semanticommunity.info/ Information_ Sharing_ Environment/ ISE_ Enterprise_ Architecture_ Framework_ 2007#Figure_ ES-2._ The_ ISE_ Enterprise_ Architecture_ Framework_ Is_ Defined_ by_ Two_ Views_ and_ Four_ Partitions]
The diagram example "The ISE 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 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.

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.