企业架构框架

此词条暂由彩云小译翻译，翻译字数共3712，未经人工整理和审校，带来阅读不便，请见谅。

文件:NIST Enterprise Architecture Model.jpg

NIST Enterprise Architecture Model initiated in 1989, one of the earliest frameworks for enterprise architecture.

An enterprise architecture framework (EA framework) defines how to create and use an enterprise architecture. An architecture framework provides principles and practices for creating and using the architecture description of a system. It structures architects' thinking by dividing the architecture description into domains, layers, or views, and offers models - typically matrices and diagrams - for documenting each view. This allows for making systemic design decisions on all the components of the system and making long-term decisions around new design requirements, sustainability, and support.

An enterprise architecture framework (EA framework) defines how to create and use an enterprise architecture. An architecture framework provides principles and practices for creating and using the architecture description of a system. It structures architects' thinking by dividing the architecture description into domains, layers, or views, and offers models - typically matrices and diagrams - for documenting each view. This allows for making systemic design decisions on all the components of the system and making long-term decisions around new design requirements, sustainability, and support.

企业架构框架(EA 框架)定义了如何创建和使用企业架构。体系结构框架为创建和使用系统的体系结构描述提供了原则和实践。它通过将架构描述划分为域、层或视图来构建架构师的思维，并提供模型(通常是矩阵和图表)来记录每个视图。这允许对系统的所有组件做出系统的设计决策，并围绕新的设计要求、可持续性和支持做出长期的决策。

Overview

Enterprise architecture regards the enterprise as a large and complex system or system of systems. To manage the scale and complexity of this system, an architectural framework provides tools and approaches that help architects abstract from the level of detail at which builders work, to bring enterprise design tasks into focus and produce valuable architecture description documentation.

Enterprise architecture regards the enterprise as a large and complex system or system of systems.The Open Group (2008) TOGAF Version 9. Van Haren Publishing, 1 nov. 2008.p. 73 To manage the scale and complexity of this system, an architectural framework provides tools and approaches that help architects abstract from the level of detail at which builders work, to bring enterprise design tasks into focus and produce valuable architecture description documentation.

企业架构将企业视为一个庞大而复杂的系统或系统。公开组(2008) TOGAF 第9版。范哈伦出版社，2008年11月1日。73. 为了管理这个系统的规模和复杂性，架构框架提供了工具和方法，帮助架构师从建造者工作的详细程度中抽象出来，使企业设计任务成为焦点，并产生有价值的架构说明文件。

The components of an architecture framework provide structured guidance that is divided into three main areas:

• Descriptions of architecture: how to document the enterprise as a system, from several viewpoints. Each view describes one slice of the architecture; it includes those entities and relationships that address particular concerns of interest to particular stakeholders; it may take the form of a list, a table, a diagram, or a higher level of composite of such.
• Methods for designing architecture: processes that architects follow. Usually, an overarching enterprise architecture process, composed of phases, broken into lower-level processes composed of finer grained activities. A process is defined by its objectives, inputs, phases (steps or activities) and outputs. It may be supported by approaches, techniques, tools, principles, rules, and practices.
• Organization of architects: guidance on the team structure and the governance of the team, including the skills, experience, and training needed.

The components of an architecture framework provide structured guidance that is divided into three main areas:Stephen Marley (2003). Architectural Framework. NASA /SCI. At Webarchive.org, retrieved 3-04-2015.

• Descriptions of architecture: how to document the enterprise as a system, from several viewpoints. Each view describes one slice of the architecture; it includes those entities and relationships that address particular concerns of interest to particular stakeholders; it may take the form of a list, a table, a diagram, or a higher level of composite of such.
• Methods for designing architecture: processes that architects follow. Usually, an overarching enterprise architecture process, composed of phases, broken into lower-level processes composed of finer grained activities. A process is defined by its objectives, inputs, phases (steps or activities) and outputs. It may be supported by approaches, techniques, tools, principles, rules, and practices.
• Organization of architects: guidance on the team structure and the governance of the team, including the skills, experience, and training needed.

架构框架的组件提供了结构化的指导，这些指导分为三个主要领域: Stephen Marley (2003)。架构框架。NASA/SCI.在 Webarchive.org，检索到3-04-2015。

• 体系结构描述: 如何从多个角度将企业作为一个系统编制文档。每个视图描述体系结构的一个部分; 它包括那些处理特定涉众感兴趣的特定问题的实体和关系; 它可以采用列表、表格、图表的形式，或者这些实体和关系的更高层次的组合。
• 架构设计方法: 架构师遵循的过程。通常，由阶段组成的总体企业架构流程分解为由更细粒度的活动组成的较低层次的流程。流程由其目标、输入、阶段(步骤或活动)和输出来定义。它可能得到方法、技术、工具、原则、规则和实践的支持。
• 架构师的组织: 关于团队结构和团队治理的指导，包括所需的技能、经验和培训。

History

文件:Evolution of Enterprise Architecture Frameworks.jpg

Overview of Enterprise Architecture Frameworks evolution (1987–2003). On the left: The Zachman Framework 1987, NIST Enterprise Architecture 1989, EAP 1992, TISAF 1997, FEAF 1999 and TEAF 2000. On the right: TAFIM influenced by POSIX, JTA, JTAA, TOGAF 1995, DoD TRM and C4ISR 1996, and DoDAF 2003.

The earliest rudiments of the step-wise planning methodology currently advocated by The Open Group Architecture Framework (TOGAF) and other EA frameworks can be traced back to the article of Marshall K. Evans and Lou R. Hague titled "Master Plan for Information Systems" published in 1962 in Harvard Business Review.

The earliest rudiments of the step-wise planning methodology currently advocated by The Open Group Architecture Framework (TOGAF) and other EA frameworks can be traced back to the article of Marshall K. Evans and Lou R. Hague titled "Master Plan for Information Systems"Evans, M. K. and Hague, L. R. (1962) Master Plan for Information Systems, Harvard Business Review, Vol. 40, No. 1, pp. 92-103. published in 1962 in Harvard Business Review.Kotusev, Svyatoslav (2021) The Practice of Enterprise Architecture: A Modern Approach to Business and IT Alignment (2nd Edition). Melbourne, Australia: SK Publishing.

目前由开放组织架构框架(TOGAF)和其他 EA 框架所倡导的分步规划方法的最早的雏形可以追溯到 Marshall K。 Evans 和 Lou R。 Hague 题为“信息系统的总体规划”的文章。40，不。1页。92-103.1962年发表在《哈佛商业评论》上。Kotusev，Svyatoslav (2021)《企业架构的实践: 业务和 IT 一致性的现代方法》(第2版)。澳大利亚墨尔本: SK 出版社。

Since the 1970s people working in IS/IT have looked for ways to engage business people – to enable business roles and processes - and to influence investment in business information systems and technologies – with a view to the wide and long term benefits of the enterprise. Many of the aims, principles, concepts and methods now employed in EA frameworks were established in the 1980s, and can be found in IS and IT architecture frameworks published in that decade and the next.

Since the 1970s people working in IS/IT have looked for ways to engage business people – to enable business roles and processes - and to influence investment in business information systems and technologies – with a view to the wide and long term benefits of the enterprise. Many of the aims, principles, concepts and methods now employed in EA frameworks were established in the 1980s, and can be found in IS and IT architecture frameworks published in that decade and the next.Graham Berrisford (2008-13) "A brief history of EA: what is in it and what is not " on grahamberrisford.com, last update 16/07/2013. Accessed 16/07?2003

自20世纪70年代以来，从事信息系统/信息技术工作的人们一直在寻找让业务人员参与进来的方法——使业务角色和流程成为可能——并影响对业务信息系统和技术的投资——以期为企业带来广泛和长期的利益。现在在 EA 框架中使用的许多目标、原则、概念和方法都是在20世纪80年代建立的，并且可以在那个十年和下一个十年发布的 IS 和 IT 架构框架中找到。格雷厄姆 · 贝里斯福德(2008-13)“电子艺界的简史: 什么在里面，什么不在里面”grahamberrisford.com ，最后更新于2013年7月16日。2003年7月16日

By 1980, IBM's Business Systems Planning (BSP) was promoted as a method for analyzing and designing an organization's information architecture, with the following goals:

1. understand the issues and opportunities with the current applications and technical architecture;
2. develop a future state and migration path for the technology that supports the enterprise;
3. provide business executives with a direction and decision making framework for IT capital expenditures;
4. provide the information system (IS) with a blueprint for development.

By 1980, IBM's Business Systems Planning (BSP) was promoted as a method for analyzing and designing an organization's information architecture, with the following goals:

1. understand the issues and opportunities with the current applications and technical architecture;
2. develop a future state and migration path for the technology that supports the enterprise;
3. provide business executives with a direction and decision making framework for IT capital expenditures;
4. provide the information system (IS) with a blueprint for development.

到1980年，IBM 的业务系统规划(Business Systems Planning，BSP)被推广为一种分析和设计组织信息架构的方法，其目标如下: # 了解当前应用程序和技术架构的问题和机会; # 为支持企业的技术开发未来状态和迁移路径; # 为企业高管提供 IT 资本支出的方向和决策框架; # 为信息系统(IS)提供发展蓝图。

In 1982, when working for IBM and with BSP, John Zachman outlined his framework for enterprise-level "Information Systems Architecture". Then and in later papers, Zachman used the word enterprise as a synonym for business. "Although many popular information systems planning methodologies, design approaches, and various tools and techniques do not preclude or are not inconsistent with enterprise-level analysis, few of them explicitly address or attempt to define enterprise architectures." However, in this article the term "Enterprise Architecture" was mentioned only once without any specific definition and all subsequent works of Zachman used the term "Information Systems Architecture".

In 1982, when working for IBM and with BSP, John Zachman outlined his framework for enterprise-level "Information Systems Architecture". Then and in later papers, Zachman used the word enterprise as a synonym for business. "Although many popular information systems planning methodologies, design approaches, and various tools and techniques do not preclude or are not inconsistent with enterprise-level analysis, few of them explicitly address or attempt to define enterprise architectures."John Zachman (1982) Business Systems Planning and Business Information Control Study: A comparison in IBM Systems Journal 21(1). p32. However, in this article the term "Enterprise Architecture" was mentioned only once without any specific definition and all subsequent works of Zachman used the term "Information Systems Architecture".

1982年，在为 IBM 和 BSP 工作时，John Zachman 概述了他的企业级“信息系统架构”框架。然后，在后来的论文中，扎克曼使用企业这个词作为商业的同义词。“尽管许多流行的信息系统规划方法、设计方法以及各种工具和技术并不排除或不与企业级分析不一致，但它们中很少有明确提出或试图定义企业架构。“ John Zachman (1982)业务系统规划和业务信息控制研究: IBM 系统杂志21(1)中的比较。P32.然而，在本文中，“企业架构”这个术语只被提到了一次，没有任何具体的定义，而且 Zachman 后来的所有作品都使用了“信息系统架构”这个术语。

In 1986, the PRISM architecture framework was developed as a result of the research project sponsored by a group of companies, including IBM, which was seemingly the first published EA framework.

In 1986, the PRISM architecture framework was developed as a result of the research project sponsored by a group of companies, including IBM, which was seemingly the first published EA framework.Svyatoslav Kotusev (2016). The History of Enterprise Architecture: An Evidence-Based Review. In: Journal of Enterprise Architecture, vol. 12, no. 1, pp. 29-37.

在1986年，PRISM 体系结构框架是由包括 IBM 在内的一组公司发起的研究项目的结果，这似乎是第一个发布的 EA 框架。斯维亚托斯拉夫 · 科图塞夫(2016)。企业架构的历史: 一个基于证据的回顾。企业架构杂志。12号，不。1页。29-37.

In 1987, John Zachman, who was a marketing specialist at IBM, published the paper, A Framework for Information Systems Architecture. The paper provided a classification scheme for artifacts that describe (at several levels of abstraction) the what, how, where, who, when and why of information systems. Given IBM already employed BSP, Zachman had no need to provide planning process. The paper did not mention enterprise architecture.

In 1987, John Zachman, who was a marketing specialist at IBM, published the paper, A Framework for Information Systems Architecture.John A. Zachman (1987). A Framework for Information Systems Architecture. In: IBM Systems Journal, vol 26, no 3. IBM Publication G321-5298. The paper provided a classification scheme for artifacts that describe (at several levels of abstraction) the what, how, where, who, when and why of information systems. Given IBM already employed BSP, Zachman had no need to provide planning process. The paper did not mention enterprise architecture.

1987年，IBM 市场营销专家 John Zachman 发表了一篇名为《信息系统架构框架》的论文。约翰 · A · 扎克曼(1987)。信息系统体系结构框架。在: IBM 系统杂志，第26卷，第3期。IBM 出版物 G321-5298。这篇论文提供了一个工件的分类方案，这些工件描述了(在几个抽象层次上)信息系统的“什么”、“如何”、“在哪里”、“谁”、“何时”以及“为什么”。鉴于 IBM 已经采用了 BSP，Zachman 不需要提供计划流程。这篇文章没有提到企业架构。

In 1989, the National Institute of Standards and Technology (NIST) published the NIST Enterprise Architecture Model. This was a five-layer reference model that illustrates the interrelationship of business, information system, and technology domains. It was promoted within the U.S. federal government. It was not an EA framework as we see it now, but it helped to establish the notion of dividing EA into architecture domains or layers. The NIST Enterprise Architecture Model seemingly was the first publication that consistently used the term "Enterprise Architecture".

In 1989, the National Institute of Standards and Technology (NIST) published the NIST Enterprise Architecture Model.W.B. Rigdon (1989). Architectures and Standards. In Information Management Directions: The Integration Challenge (NIST Special Publication 500-167), E.N. Fong, A.H. Goldfine (Eds.), Gaithersburg, MD: National Institute of Standards and Technology (NIST), pp.135-150. This was a five-layer reference model that illustrates the interrelationship of business, information system, and technology domains. It was promoted within the U.S. federal government. It was not an EA framework as we see it now, but it helped to establish the notion of dividing EA into architecture domains or layers. The NIST Enterprise Architecture Model seemingly was the first publication that consistently used the term "Enterprise Architecture".

1989年，美国国家标准与技术研究所(NIST)发布了 NIST 企业架构模型 W.B。里格登(1989)。架构及标准。信息管理方向: 集成挑战(NIST 特别出版物500-167) ，E.N。方，A.H. 戈德费恩(编辑部)。) ，盖瑟斯堡，MD: 国家标准与技术研究所(nIST) ，第135-150页。这是一个五层参考模型，说明了业务、信息系统和技术领域之间的相互关系。它是在美国联邦政府内部推广的。它不是我们现在看到的 EA 框架，但它帮助建立了将 EA 划分为架构域或层的概念。NIST 企业架构模型似乎是第一个始终使用术语“企业架构”的出版物。

In 1990, the term "Enterprise Architecture" was formally defined for the first time as an architecture that "defines and interrelates data, hardware, software, and communications resources, as well as the supporting organization required to maintain the overall physical structure required by the architecture".

In 1990, the term "Enterprise Architecture" was formally defined for the first time as an architecture that "defines and interrelates data, hardware, software, and communications resources, as well as the supporting organization required to maintain the overall physical structure required by the architecture".

1990年，术语“企业架构”第一次被正式定义为“定义和相互关联的数据、硬件、软件和通信资源，以及维护架构所需的整体物理结构所需的支持组织”的架构。

In 1992, a paper by Zachman and Sowa started thus "John Zachman introduced a framework for information systems architecture (ISA) that has been widely adopted by systems analysts and database designers." The term enterprise architecture did not appear. The paper was about using the ISA framework to describe, “...the overall information system and how it relates to the enterprise and its surrounding environment.” The word enterprise was used as a synonym for business.

In 1992, a paper by Zachman and SowaZachman and Sowa (1992) Extending and formalising the framework of information systems architecture IBM Systems Journal, Vol 31, No 3 started thus "John Zachman introduced a framework for information systems architecture (ISA) that has been widely adopted by systems analysts and database designers." The term enterprise architecture did not appear. The paper was about using the ISA framework to describe, “...the overall information system and how it relates to the enterprise and its surrounding environment.” The word enterprise was used as a synonym for business.

1992年，Zachman 和 SowaZachman 以及 Sowa (1992)发表了一篇论文，对信息系统架构的框架进行了扩展和正式化，IBM Systems Journal，Vol 31，No 3开始这样写道: “ John Zachman 介绍了一个信息系统架构(ISA)的框架，这个框架已经被系统分析师和数据库设计师广泛采用。”没有出现“企业架构”这个术语。本文是关于使用 ISA 框架来描述“ ... 整个信息系统以及它如何与企业及其周围环境相关联。”企业这个词曾被用作商业的同义词。

In 1993, Stephen Spewak's book Enterprise Architecture Planning (EAP) defined a process for defining architectures for the use of information in support of the business and the plan for implementing those architectures. The business mission is the primary driver. Then the data required to satisfy the mission. Then the applications built to store and provide that data. Finally the technology to implement the applications. Enterprise Architecture Planning is a data-centric approach to architecture planning. An aim is to improve data quality, access to data, adaptability to changing requirements, data interoperability and sharing, and cost containment. EAP has its roots in IBM's Business Systems Planning (BSP).

In 1993, Stephen Spewak's book Enterprise Architecture Planning (EAP) defined a process for defining architectures for the use of information in support of the business and the plan for implementing those architectures. The business mission is the primary driver. Then the data required to satisfy the mission. Then the applications built to store and provide that data. Finally the technology to implement the applications. Enterprise Architecture Planning is a data-centric approach to architecture planning. An aim is to improve data quality, access to data, adaptability to changing requirements, data interoperability and sharing, and cost containment. EAP has its roots in IBM's Business Systems Planning (BSP).

在1993年，Stephen Spewak 的著作《企业架构规划》(Enterprise Architecture Planning，EAP)定义了一个定义架构的过程，用于使用支持业务的信息和实现这些架构的计划。业务使命是主要驱动力。然后是满足任务所需的数据。然后构建用于存储和提供该数据的应用程序。最后介绍了实现应用的技术。企业架构规划是以数据为中心的架构规划方法。其目的是提高数据质量、访问数据、适应不断变化的需求、数据互操作性和共享以及成本控制。EAP 起源于 IBM 的业务系统规划(BSP)。

In 1994, the Open Group selected TAFIM from the US DoD as a basis for development of TOGAF, where architecture meant IT architecture. TOGAF started out taking a strategic and enterprise-wide, but technology-oriented, view. It emerged from the desire to rationalize a messy IT estate. Right up to version 7, TOGAF was still focused on defining and using a Technical Reference Model (or foundation architecture) to define the platform services required from the technologies that an entire enterprise uses to support business applications.

In 1994, the Open Group selected TAFIM from the US DoD as a basis for development of TOGAF, where architecture meant IT architecture. TOGAF started out taking a strategic and enterprise-wide, but technology-oriented, view. It emerged from the desire to rationalize a messy IT estate. Right up to version 7, TOGAF was still focused on defining and using a Technical Reference Model (or foundation architecture) to define the platform services required from the technologies that an entire enterprise uses to support business applications.

1994年，Open Group 从美国国防部选择了 TAFIM 作为开发 TOGAF 的基础，其中架构意味着 IT 架构。TOGAF 最初采取的是一种战略性的、企业范围的、但以技术为导向的观点。它来自于合理化一个混乱的 IT 产业的愿望。直到版本7，TOGAF 仍然专注于定义和使用技术参考模型(或基础架构)来定义整个企业用于支持业务应用程序的技术所需的平台服务。

In 1996, the US IT Management Reform Act, more commonly known as the Clinger-Cohen Act, repeatedly directed that a US federal government agency's investment in IT must be mapped to identifiable business benefits. In addition, it made the agency CIO responsible for, “...developing, maintaining and facilitating the implementation of a sound and integrated IT architecture for the executive agency.”

In 1996, the US IT Management Reform Act, more commonly known as the Clinger-Cohen Act, repeatedly directed that a US federal government agency's investment in IT must be mapped to identifiable business benefits. In addition, it made the agency CIO responsible for, “...developing, maintaining and facilitating the implementation of a sound and integrated IT architecture for the executive agency.”

1996年，美国《 IT 管理改革法案》(更常见的名称是《克林格-科恩法案》(Clinger-Cohen Act))多次指示，美国联邦政府机构在 IT 领域的投资必须与可识别的商业利益挂钩。此外，它还使该机构的 CIO 负责“ ... ... 为执行机构开发、维护和促进一个健全和集成的 IT 架构的实施。”

By 1997, Zachman had renamed and refocused his ISA framework as an EA framework; it remained a classification scheme for descriptive artifacts, not a process for planning systems or changes to systems.

By 1997, Zachman had renamed and refocused his ISA framework as an EA framework; it remained a classification scheme for descriptive artifacts, not a process for planning systems or changes to systems.

到1997年，扎克曼已经重新命名了 ISA 框架，并将其重新定位为 EA 框架，它仍然是描述性工件的分类方案，而不是规划系统或更改系统的过程。

In 1998, The Federal CIO Council began developing the Federal Enterprise Architecture Framework (FEAF) in accordance with the priorities enunciated in Clinger-Cohen and issued it in 1999. FEAF was a process much like TOGAF's ADM, in which “The architecture team generates a sequencing plan for the transition of systems, applications, and associated business practices predicated upon a detailed gap analysis [between baseline and target architectures].”

In 1998, The Federal CIO Council began developing the Federal Enterprise Architecture Framework (FEAF) in accordance with the priorities enunciated in Clinger-Cohen and issued it in 1999. FEAF was a process much like TOGAF's ADM, in which “The architecture team generates a sequencing plan for the transition of systems, applications, and associated business practices predicated upon a detailed gap analysis [between baseline and target architectures].”

1998年，联邦首席信息官委员会根据 Clinger-Cohen 阐述的优先事项，开始制定联邦企业架构框架(feAF) ，并于1999年发布。FEAF 是一个非常类似于 TOGAF 的 ADM 的过程，在这个过程中，“体系结构团队根据基线和目标体系结构之间的详细差距分析，为系统、应用程序和相关业务实践的转换生成一个排序计划。”

In 2001, the US Chief CIO council published A practical guide to Federal Enterprise Architecture, which starts, “An enterprise architecture (EA) establishes the Agency-wide roadmap to achieve an Agency’s mission through optimal performance of its core business processes within an efficient information technology (IT) environment." At that point, the processes in TOGAF, FEAF, EAP and BSP were clearly related.

In 2001, the US Chief CIO council published A practical guide to Federal Enterprise Architecture, which starts, “An enterprise architecture (EA) establishes the Agency-wide roadmap to achieve an Agency’s mission through optimal performance of its core business processes within an efficient information technology (IT) environment." At that point, the processes in TOGAF, FEAF, EAP and BSP were clearly related.

2001年，美国首席信息官理事会出版了《联邦企业架构实用指南》 ，其中开头写道: “企业架构(EA)建立了机构范围的路线图，通过在有效的信息技术(IT)环境中优化其核心业务流程来实现机构的使命。”当时，TOGAF、东亚经济合作联盟、东亚经济合作联盟和巴黎协定的程序显然是相互关联的。

In 2002/3, in its Enterprise Edition, TOGAF 8 shifted focus from the technology architecture layer to the higher business, data and application layers. It introduced structured analysis, after information technology engineering, which features, for example, mappings of organization units to business functions and data entities to business functions. Today, business functions are often called business capabilities. And many enterprise architects regard their business function/capability hierarchy/map as the fundamental Enterprise Architecture artifact. They relate data entities, use cases, applications and technologies to the functions/capabilities.

In 2002/3, in its Enterprise Edition, TOGAF 8 shifted focus from the technology architecture layer to the higher business, data and application layers. It introduced structured analysis, after information technology engineering, which features, for example, mappings of organization units to business functions and data entities to business functions. Today, business functions are often called business capabilities. And many enterprise architects regard their business function/capability hierarchy/map as the fundamental Enterprise Architecture artifact. They relate data entities, use cases, applications and technologies to the functions/capabilities.

在2002/3年度的企业版中，TOGAF 8将重点从技术架构层转移到了更高的业务、数据和应用程序层。它在信息技术工程之后引入了结构化分析，例如，组织单元到业务功能的映射，以及数据实体到业务功能的映射。今天，业务功能通常被称为业务功能。许多企业架构师将其业务功能/能力层次结构/映射视为基本的企业架构构件。它们将数据实体、用例、应用程序和技术与功能/能力联系起来。

In 2006, the popular book Enterprise Architecture As Strategy reported the results of work by MIT's Center for Information System Research. This book emphasises the need for enterprise architects to focus on core business processes ("Companies excel because they've [decided] which processes they must execute well, and have implemented the IT systems to digitise those processes.") and to engage business managers with the benefits that strategic cross-organisational process integration and/or standardisation could provide.

In 2006, the popular book Enterprise Architecture As StrategyJeanne W. Ross, Peter Weill, and David C. Robertson ( (2006) Enterprise Architecture As Strategy: Creating a Foundation for Business Execution. Harvard Business Review Press reported the results of work by MIT's Center for Information System Research. This book emphasises the need for enterprise architects to focus on core business processes ("Companies excel because they've [decided] which processes they must execute well, and have implemented the IT systems to digitise those processes.") and to engage business managers with the benefits that strategic cross-organisational process integration and/or standardisation could provide.

2006年，流行书籍《企业架构作为战略》(Enterprise Architecture As Strategies) ，珍妮 · W · 罗斯(Jeanne W. Ross)、彼得 · 威尔(Peter Weill)和大卫 · C · 罗伯逊(David C. Robertson)(2006)《企业架构作为战略: 为企业执行创造基础》(Enterprise Architecture As Strategy: Create a Foundation for Business Execution)。哈佛商业评论出版社报道了麻省理工学院信息系统研究中心的工作成果。这本书强调了企业架构师关注核心业务流程的必要性(“公司之所以优秀，是因为他们已经[决定]了必须很好地执行哪些流程，并且已经实现了将这些流程数字化的 IT 系统。”)并让业务经理参与战略性跨组织流程整合和/或标准化可能带来的好处。

A 2008 research project for the development of professional certificates in enterprise and solution architecture by the British Computer Society (BCS) showed that enterprise architecture has always been inseparable from information system architecture, which is natural, since business people need information to make decisions and carry out business processes.

A 2008 research project for the development of professional certificates in enterprise and solution architecture by the British Computer Society (BCS) showed that enterprise architecture has always been inseparable from information system architecture, which is natural, since business people need information to make decisions and carry out business processes.

2008年，英国计算机协会(BCS)的一个企业和解决方案体系结构专业证书开发研究项目表明，企业体系结构一直与信息系统体系结构密不可分，这是很自然的，因为企业人员需要信息来做出决策和执行业务流程。

In 2011, the TOGAF 9.1. specification says: "Business planning at the strategy level provides the initial direction to enterprise architecture." Normally, the business principles, business goals, and strategic drivers of the organization are defined elsewhere. In other words, Enterprise Architecture is not a business strategy, planning or management methodology. Enterprise Architecture strives to align business information systems technology with given business strategy, goals and drivers. The TOGAF 9.1 specification clarified, that, "A complete enterprise architecture description should contain all four architecture domains (business, data, application, technology), but the realities of resource and time constraints often mean there is not enough time, funding, or resources to build a top-down, all-inclusive architecture description encompassing all four architecture domains, even if the enterprise scope is [...] less than the full extent of the overall enterprise."

In 2011, the TOGAF 9.1. specification says: "Business planning at the strategy level provides the initial direction to enterprise architecture."The Open Group (2011) TOGAF® 9.1 > Part II: Architecture Development Method (ADM) > Preliminary Phase. Accessed July 16, 2013 Normally, the business principles, business goals, and strategic drivers of the organization are defined elsewhere. In other words, Enterprise Architecture is not a business strategy, planning or management methodology. Enterprise Architecture strives to align business information systems technology with given business strategy, goals and drivers. The TOGAF 9.1 specification clarified, that, "A complete enterprise architecture description should contain all four architecture domains (business, data, application, technology), but the realities of resource and time constraints often mean there is not enough time, funding, or resources to build a top-down, all-inclusive architecture description encompassing all four architecture domains, even if the enterprise scope is [...] less than the full extent of the overall enterprise."The Open Group (2011) TOGAF® 9.1 > Part II: Architecture Development Method (ADM) > Introduction to the ADM. Accessed July 16, 2013

在2011年，TOGAF 9.1. 规范说: “战略级别的业务规划为企业架构提供了初始方向。开放小组(2011) TOGAF 9.1 > 第二部分: 架构开发方法(ADM) > 初步阶段。2013年7月16日访问通常，组织的业务原则、业务目标和战略驱动因素在其他地方定义。换句话说，企业架构不是一种业务战略、计划或管理方法。企业架构力求使业务信息系统技术与给定的业务战略、目标和驱动因素保持一致。TOGAF 9.1规范阐明，“一个完整的企业架构描述应该包含所有四个架构域(业务、数据、应用程序、技术) ，但是资源和时间限制的现实往往意味着没有足够的时间、资金或资源来构建一个自顶向下的、包含所有四个架构域的全面架构描述，即使企业范围[ ... ]小于整个企业的全部范围。开放小组(2011) TOGAF 9.1 > 第二部分: 架构开发方法(ADM) > ADM 介绍2013年7月16日访问

In 2013, TOGAF is the most popular Architecture framework (judged by published certification numbers) that some assume it defines EA. However, some still use the term Enterprise Architecture as a synonym for Business Architecture, rather than covering all four architecture domains - business, data, applications and technology.

In 2013, TOGAFTOGAF 9.1 White Paper An Introduction to TOGAF Version 9.1 http://www.opengroup.org/togaf/ is the most popular Architecture framework (judged by published certification numbers) that some assume it defines EA. However, some still use the term Enterprise Architecture as a synonym for Business Architecture, rather than covering all four architecture domains - business, data, applications and technology.

2013年，TOGAFTOGAF 9.1白皮书 TOGAF 9.1版本 http://www.opengroup.org/TOGAF/是最流行的架构框架(根据已发布的认证号判断) ，有些人认为它定义了 EA。然而，有些人仍然使用术语企业架构作为业务架构的同义词，而不是涵盖所有四个架构领域-业务、数据、应用程序和技术。

= EA 框架主题 =

Architecture domain

文件:Layers of the Enterprise Architecture.jpg

Layers of the enterprise architecture.

Since Stephen Spewak's Enterprise Architecture Planning (EAP) in 1993 – and perhaps before then – it has been normal to divide enterprises architecture into four architecture domains.

thumb|320px|Layers of the enterprise architecture.Niles E Hewlett (2006), The USDA Enterprise Architecture Program . PMP CEA, Enterprise Architecture Team, USDA-OCIO. January 25, 2006. Since Stephen Spewak's Enterprise Architecture Planning (EAP) in 1993 – and perhaps before then – it has been normal to divide enterprises architecture into four architecture domains.

= = = 体系结构域 = = = 拇指 | 320px | 企业体系结构的层次 | 奈尔斯 · E · 休利特(2006) ，[美国农业部企业体系结构计划 http://www.ocio.USDA.gov/p_mgnt/doc/pm_class_ea_neh_012506_final.ppt ]。企业架构团队。2006年01月25日。自从1993年 Stephen Spewak 的企业架构规划(Enterprise Architecture Planning，EAP)以来——或许在那之前——将企业架构划分为四个架构领域已经很正常了。

• Business architecture,
• Data architecture,
• Applications architecture,
• Technology architecture.

• Business architecture,
• Data architecture,
• Applications architecture,
• Technology architecture.

• 业务架构
• 数据架构
• 应用架构
• 技术架构。

Note that the applications architecture is about the choice of and relationships between applications in the enterprise's application portfolio, not about the internal architecture of a single application (which is often called application architecture).

Note that the applications architecture is about the choice of and relationships between applications in the enterprise's application portfolio, not about the internal architecture of a single application (which is often called application architecture).

请注意，应用程序体系结构是关于企业应用程序组合中应用程序的选择和应用程序之间的关系，而不是关于单个应用程序的内部体系结构(通常称为应用程序体系结构)。

Many EA frameworks combine data and application domains into a single (digitized) information system layer, sitting below the business (usually a human activity system) and above the technology (the platform IT infrastructure).

Many EA frameworks combine data and application domains into a single (digitized) information system layer, sitting below the business (usually a human activity system) and above the technology (the platform IT infrastructure).

许多 EA 框架将数据和应用程序域组合成一个单一的(数字化的)信息系统层，位于业务(通常是人工活动系统)和技术(平台 IT 基础设施)之上。

Layers of the enterprise architecture

文件:FEA Reference Models.jpg

Example of the federal enterprise architecture, which has defined five architectural layers.

For many years, it has been common to regard the architecture domains as layers, with the idea that each layer contains components that execute processes and offer services to the layer above. This way of looking at the architecture domains was evident in TOGAF v1 (1996), which encapsulated the technology component layer behind the platform services defined in the "Technical Reference Model" - very much according to the philosophy of TAFIM and POSIX.

For many years, it has been common to regard the architecture domains as layers, with the idea that each layer contains components that execute processes and offer services to the layer above. This way of looking at the architecture domains was evident in TOGAF v1 (1996), which encapsulated the technology component layer behind the platform services defined in the "Technical Reference Model" - very much according to the philosophy of TAFIM and POSIX.

多年来，人们普遍将体系结构域视为层，认为每一层都包含执行流程并向上一层提供服务的组件。这种看待架构领域的方式在 TOGAF v1(1996)中很明显，它封装了“技术参考模型”中定义的平台服务背后的技术组件层——非常符合 TAFIM 和 POSIX 的哲学。

The view of architecture domains as layers can be presented thus:

The view of architecture domains as layers can be presented thus:

体系结构领域作为层次的观点可以这样表示:

• Environment (the external entities and activities monitored, supported or directed by the business).
• Business Layer (business functions offering services to each other and to external entities).
• Data Layer (Business information and other valuable stored data)
• Information System Layer (business applications offering information services to each other and to business functions)
• Technology Layer (generic hardware, network and platform applications offering platform services to each other and to business applications).

• Environment (the external entities and activities monitored, supported or directed by the business).
• Business Layer (business functions offering services to each other and to external entities).
• Data Layer (Business information and other valuable stored data)
• Information System Layer (business applications offering information services to each other and to business functions)
• Technology Layer (generic hardware, network and platform applications offering platform services to each other and to business applications).

• 环境(由业务监察、支援或指示的外部实体及活动)。
• 业务层(为彼此和外部实体提供服务的业务功能)。
• 数据层(业务信息和其他有价值的存储数据)
• 信息系统层(业务应用程序相互提供信息服务和业务功能)
• 技术层(通用硬件、网络和平台应用程序相互提供平台服务和业务应用程序)。

Each layer delegates work to the layer below. In each layer, the components, the processes and the services can be defined at a coarse-grained level and decomposed into finer-grained components, processes and services. The graphic shows a variation on this theme.

Each layer delegates work to the layer below. In each layer, the components, the processes and the services can be defined at a coarse-grained level and decomposed into finer-grained components, processes and services. The graphic shows a variation on this theme.

每一层都将工作委托给下一层。在每一层中，组件、流程和服务都可以在粗粒度级别上定义，并分解为更细粒度的组件、流程和服务。图表显示了这个主题的一个变体。

Components of enterprise architecture framework

In addition to three major framework components discussed above.

1. Description advice: some kind of Architecture Artifacts Map or Viewpoint Library
2. Process advice: some kind of Architecture Development Method, with supporting guidance.
3. Organization advice: including an EA Governance Model

In addition to three major framework components discussed above.

1. Description advice: some kind of Architecture Artifacts Map or Viewpoint Library
2. Process advice: some kind of Architecture Development Method, with supporting guidance.
3. Organization advice: including an EA Governance Model

= = 企业架构框架的组件 = = 除了上面讨论的三个主要框架组件之外。描述建议: 某种类型的架构工件地图或视点库过程建议: 某种类型的架构开发方法，以及支持指导。# 组织建议: 包括 EA 治理模型

An ideal EA framework should feature:

1. Business value measurement metrics
2. EA initiative model
3. EA maturity model
4. Enterprise communication model

An ideal EA framework should feature:

1. Business value measurement metrics
2. EA initiative model
3. EA maturity model
4. Enterprise communication model

一个理想的 EA 框架应该具有以下特征: # 业务价值度量指标 # EA 计划模型 # EA 成熟度模型 # 企业沟通模型

Most modern EA frameworks (e.g. TOGAF, ASSIMPLER, EAF) include most of the above. Zachman has always focused on architecture description advice.

Most modern EA frameworks (e.g. TOGAF, ASSIMPLER, EAF) include most of the above. Zachman has always focused on architecture description advice.

大多数现代 EA 框架(例如。TOGAF，ASSIMPLER，EAF)包括上述大部分。Zachman 一直专注于体系结构描述建议。

Enterprise architecture domains and subdomains

文件:Enterprise Architecture Domain Reference Architecture.JPG

Enterprise architecture reference architecture with sub domains

The application and technology domains (not to be confused with business domains) are characterized by domain capabilities and domain services. The capabilities are supported by the services. The application services are also referred to in service-oriented architecture (SOA). The technical services are typically supported by software products.

thumb|320px|Enterprise architecture reference architecture with sub domains The application and technology domains (not to be confused with business domains) are characterized by domain capabilities and domain services. The capabilities are supported by the services. The application services are also referred to in service-oriented architecture (SOA). The technical services are typically supported by software products.

= = = 企业架构域和子域 = = = 拇指 | 320px | 企业架构参考架构与子域应用程序和技术域(不要与业务域混淆)是拥有属性域功能和域服务。服务支持这些功能。应用程序服务也在面向服务的体系结构(SOA)中提及。技术服务通常由软件产品支持。

The data view starts with the data classes which can be decomposed into data subjects which can be further decomposed into data entities. The basic data model type which is most commonly used is called merda (master entity relationship diagrams assessment, see entity-relationship model). The Class, subject and entity forms a hierarchical view of data. Enterprises may have millions of instances of data entities.

The data view starts with the data classes which can be decomposed into data subjects which can be further decomposed into data entities. The basic data model type which is most commonly used is called merda (master entity relationship diagrams assessment, see entity-relationship model). The Class, subject and entity forms a hierarchical view of data. Enterprises may have millions of instances of data entities.

数据视图从可以分解为数据主体的数据类开始，数据主体可以进一步分解为数据实体。最常用的基本数据模型类型称为 merda (主实体关系图评估，见 ER模型)。类、主题和实体形成了数据的分层视图。企业可能有数百万个数据实体实例。

The Enterprise Architecture Reference Traditional Model offers a clear distinction between the architecture domains (business, information/data, application/integration and technical/infrastructure). These domains can be further divided into Sub domain disciplines. An example of the EA domain and subdomains is in the image on the right.

The Enterprise Architecture Reference Traditional Model offers a clear distinction between the architecture domains (business, information/data, application/integration and technical/infrastructure). These domains can be further divided into Sub domain disciplines. An example of the EA domain and subdomains is in the image on the right.

企业架构参考传统模型提供了架构域(业务、信息/数据、应用程序/集成和技术/基础设施)之间的明确区别。这些领域可以进一步划分为子领域学科。EA 域和子域的一个例子在右边的图像中。

Many enterprise architecture teams consist of Individuals with Skills aligned with the Enterprise Architecture Domains and sub-domain disciplines. Here are some examples: enterprise business architect, enterprise documentational architect, enterprise application architect, enterprise infrastructure architect, enterprise information architect, etc.

Many enterprise architecture teams consist of Individuals with Skills aligned with the Enterprise Architecture Domains and sub-domain disciplines. Here are some examples: enterprise business architect, enterprise documentational architect, enterprise application architect, enterprise infrastructure architect, enterprise information architect, etc.

许多企业架构团队由具有与企业架构领域和子领域规程相一致的技能的个人组成。下面是一些示例: 企业业务架构师、企业文档架构师、企业应用程序架构师、企业基础设施架构师、企业信息架构师等。

An example of the list of reference architecture patterns in the application and information architecture domains are available at Architectural pattern (computer science).

An example of the list of reference architecture patterns in the application and information architecture domains are available at Architectural pattern (computer science).

应用程序和信息体系结构域中的参考体系结构模式列表的一个示例可以在体系结构模式(计算机科学)中找到。

View model

文件:4+1 Architectural View Model.svg

Illustration of the 4+1 view model of architecture.

A view model is a framework that defines the set of views or approaches used in systems analysis, systems design, or the construction of an enterprise architecture.

A view model is a framework that defines the set of views or approaches used in systems analysis, systems design, or the construction of an enterprise architecture.

视图模型是一个框架，它定义了一组用于系统分析、系统设计或构建企业架构的视图或方法。

Since the early 1990s, there have been a number of efforts to define standard approaches for describing and analyzing system architectures. Many of the recent Enterprise Architecture frameworks have some kind of set of views defined, but these sets are not always called view models.

Since the early 1990s, there have been a number of efforts to define standard approaches for describing and analyzing system architectures. Many of the recent Enterprise Architecture frameworks have some kind of set of views defined, but these sets are not always called view models.

自20世纪90年代初以来，人们一直在努力定义描述和分析系统架构的标准方法。最近的许多企业架构框架都定义了某种类型的视图集，但是这些视图集并不总是被称为视图模型。

Standardization

Perhaps the best-known standard in the field of software architecture and system architecture started life as IEEE 1471, an IEEE Standard for describing the architecture of a software-intensive system approved in 2000.

Perhaps the best-known standard in the field of software architecture and system architecture started life as IEEE 1471, an IEEE Standard for describing the architecture of a software-intensive system approved in 2000.

或许软件架构和系统架构领域最著名的标准是 IEEE 1471，这是一个 IEEE 标准，用于描述2000年批准的软件密集型系统的架构。

In its latest version, the standard is published as ISO/IEC/IEEE 42010:2011. The standard defines an architecture framework as conventions, principles and practices for the description of architectures established within a specific domain of application and/or community of stakeholders, and proposes an architecture framework is specified by:

In its latest version, the standard is published as ISO/IEC/IEEE 42010:2011. The standard defines an architecture framework as conventions, principles and practices for the description of architectures established within a specific domain of application and/or community of stakeholders, and proposes an architecture framework is specified by:

该标准的最新版本以 ISO/IEC/IEEE 42010:2011发表。该标准将体系结构框架定义为用于描述在特定应用领域和/或利益攸关方群体内建立的体系结构的约定、原则和做法，并提议体系结构框架由以下方面具体规定:

1. the relevant stakeholders in the domain,
2. the types of concerns arising in that domain,
3. architecture viewpoints framing those concerns and
4. correspondence rules integrating those viewpoints cited before.

1. the relevant stakeholders in the domain,
2. the types of concerns arising in that domain,
3. architecture viewpoints framing those concerns and
4. correspondence rules integrating those viewpoints cited before.

1. 领域中的相关利益相关者 # 该领域中产生的关注点的类型 # 构建这些关注点的体系结构观点 # 将之前引用的观点整合在一起的通信规则。

Architecture frameworks conforming to the standard can include additional methods, tools, definitions, and practices beyond those specified.

Architecture frameworks conforming to the standard can include additional methods, tools, definitions, and practices beyond those specified.

符合标准的体系结构框架可以包括超出指定范围的其他方法、工具、定义和实践。

Types of enterprise architecture framework

文件:Enterprise Architecture frameworks utilized 2011.jpg

Just a few of the Enterprise Architecture frameworks utilized today, 2011

Nowadays there are now countless EA frameworks, many more than in the following listing.

Nowadays there are now countless EA frameworks, many more than in the following listing.

企业架构框架的类型现在有无数的 EA 框架，比下面列出的要多得多。

Consortia-developed frameworks

• ARCON – A Reference Architecture for Collaborative Networks – not focused on a single enterprise but rather on networks of enterprises
• The Cloud Security Alliance (Trusted Cloud Initiative) TCI reference architectue.
• Generalised Enterprise Reference Architecture and Methodology (GERAM)
• RM-ODP – the Reference Model of Open Distributed Processing (ITU-T Rec. X.901-X.904 | ISO/IEC 10746) defines an enterprise architecture framework for structuring the specifications of open distributed systems.
• IDEAS Group – a four-nation effort to develop a common ontology for architecture interoperability
• ISO 19439 Framework for enterprise modelling
• TOGAF – The Open Group Architecture Framework – a widely used framework including an architectural Development Method and standards for describing various types of architecture.

• ARCON – A Reference Architecture for Collaborative Networks – not focused on a single enterprise but rather on networks of enterprisesL.M. Camarinha-Matos, H. Afsarmanesh, Collaborative Networks: Reference Modeling, Springer, 2008.
• The Cloud Security Alliance (Trusted Cloud Initiative) TCI reference architectue.
• Generalised Enterprise Reference Architecture and Methodology (GERAM)
• RM-ODP – the Reference Model of Open Distributed Processing (ITU-T Rec. X.901-X.904 | ISO/IEC 10746) defines an enterprise architecture framework for structuring the specifications of open distributed systems.
• IDEAS Group – a four-nation effort to develop a common ontology for architecture interoperability
• ISO 19439 Framework for enterprise modelling
• TOGAF – The Open Group Architecture Framework – a widely used framework including an architectural Development Method and standards for describing various types of architecture.

联盟开发的框架 = = =

• ARCON-协作网络的参考体系结构-不是针对单个企业，而是针对企业的网络。《协作网络: 参考建模》 ，施普林格出版社，2008年。
• 云端保安联盟(可信云端倡议)的 TCI 参考架构。
• 通用企业参考架构和方法(GERAM)
• RM-ODP-开放分布式处理的参考模型(ITU-T Rec。X. 901-X. 904 | ISO/IEC 10746)定义了一个用于构建开放分布式系统规范的企业架构框架。
• IDEAS Group-四个国家共同努力开发建筑互操作性的通用本体论
• ISO 19439企业模型框架
• TOGAF-开放组织架构框架-一个广泛使用的框架，包括架构开发方法和描述各种类型架构的标准。

Defense industry frameworks

• AGATE – the France DGA Architecture Framework
• DNDAF – the DND/CF Architecture Framework (CAN)
• DoDAF – the US Department of Defense Architecture Framework
• MODAF – the UK Ministry of Defence Architecture Framework
• NAF – the NATO Architecture Framework

• AGATE – the France DGA Architecture Framework
• DNDAFDNDAF – the DND/CF Architecture Framework (CAN)
• DoDAF – the US Department of Defense Architecture Framework
• MODAF – the UK Ministry of Defence Architecture Framework
• NAF – the NATO Architecture Framework

= = 国防工业框架 =

• AGATE-法国 DGA 架构框架
• DNDAFDNDAF-DND/CF 架构框架(CAN)
• DoDAF-美国国防部架构框架
• MODAF-英国国防部架构框架
• NAF-北约架构框架

Government frameworks

• European Space Agency Architectural Framework (ESAAF) - a framework for European space-based Systems of Systems
• FDIC Enterprise Architecture Framework
• Federal Enterprise Architecture Framework (FEAF) – a framework produced in 1999 by the US Federal CIO Council for use within the US Government (not to be confused with the 2002 Federal Enterprise Architecture (FEA) guidance on categorizing and grouping IT investments, issued by the US Federal Office of Management and Budget)
• Government Enterprise Architecture (GEA) – a common framework legislated for use by departments of the Queensland Government
• Nederlandse Overheid Referentie Architectuur (NORA) – a reference framework from the Dutch Government E-overheid NORA
• NIST Enterprise Architecture Model
• Treasury Enterprise Architecture Framework (TEAF) – a framework for treasury, published by the US Department of the Treasury in July 2000.
• Colombian Enterprise Architecture Framework - MRAE - Marco de Referencia de Arquitectura Empresarial a framework for all the Colombian Public Agencies
• India Enterprise Architecture (IndEA) framework - IndEA is a reference framework from Government of India.

• European Space Agency Architectural Framework (ESAAF) - a framework for European space-based Systems of Systems
• FDIC Enterprise Architecture Framework
• Federal Enterprise Architecture Framework (FEAF) – a framework produced in 1999 by the US Federal CIO Council for use within the US Government (not to be confused with the 2002 Federal Enterprise Architecture (FEA) guidance on categorizing and grouping IT investments, issued by the US Federal Office of Management and Budget)
• Government Enterprise Architecture (GEA) – a common framework legislated for use by departments of the Queensland Government
• Nederlandse Overheid Referentie Architectuur (NORA) – a reference framework from the Dutch Government E-overheid NORA
• NIST Enterprise Architecture Model
• Treasury Enterprise Architecture Framework (TEAF) – a framework for treasury, published by the US Department of the Treasury in July 2000.US Department of the Treasury Chief Information Officer Council (2000). Treasury Enterprise Architecture Framework . Version 1, July 2000.
• Colombian Enterprise Architecture Framework - MRAE - Marco de Referencia de Arquitectura Empresarial a framework for all the Colombian Public Agencies
• India Enterprise Architecture (IndEA) framework - IndEA is a reference framework from Government of India.

• 联邦企业架构框架(feAF)——1999年由美国联邦首席信息官理事会制定的框架，供美国政府内部使用(不要与2002年联邦企业架构(FEA)关于 IT 投资分类和分组的指南混淆，该指南由美国联邦管理和预算办公室发布)
• 政府企业架构(GEA)——为昆士兰州政府部门立法使用的通用框架
• 荷兰 Overheid 参考架构(诺拉)A
• NIST 企业架构模型
• 财政部企业架构框架(TEAF)-财政部的一个框架，由美国财政部于2000年7月公布。美国财政部首席信息官理事会(2000年)。库务署企业架构框架。二零零零年七月第一版。
• 哥伦比亚企业架构框架-MRAE-Marco de Referencia de Arquitectura Empresaria 所有哥伦比亚公共机构的框架
• 印度企业架构(IndEA)框架-IndEA 是来自印度政府的参考框架。

Open-source frameworks

Enterprise architecture frameworks that are released as open source:

• Lean Architecture Framework (LAF) is a collection of good practices thanks to which the IT environment will respond consistently and quickly to a changing business situation while maintaining its consistent form.
• MEGAF is an infrastructure for realizing architecture frameworks that conform to the definition of architecture framework provided in ISO/IEC/IEEE 42010.
• Praxeme, an open enterprise methodology, contains an enterprise architecture framework called the Enterprise System Topology (EST)
• TRAK – a general systems-oriented framework based on MODAF 1.2 and released under GPL/GFDL.
• Sherwood Applied Business Security Architecture (SABSA) is an open framework and methodology for Enterprise Security Architecture and Service Management, that is risk based and focuses on integrating security into business and IT management.

Enterprise architecture frameworks that are released as open source:

• Lean Architecture Framework (LAF)https://lafinstitute.org/ is a collection of good practices thanks to which the IT environment will respond consistently and quickly to a changing business situation while maintaining its consistent form.
• MEGAFMEGAF is an infrastructure for realizing architecture frameworks that conform to the definition of architecture framework provided in ISO/IEC/IEEE 42010.
• Praxeme, an open enterprise methodology, contains an enterprise architecture framework called the Enterprise System Topology (EST)
• TRAK – a general systems-oriented framework based on MODAF 1.2 and released under GPL/GFDL.
• Sherwood Applied Business Security Architecture (SABSA)SABSA is an open framework and methodology for Enterprise Security Architecture and Service Management, that is risk based and focuses on integrating security into business and IT management.

• 精益架构框架(Lean Architecture Framework，LAF) https://lafinstitute.org/是一系列良好实践的集合，由于这些良好实践，IT 环境能够在保持其一致性的同时，对不断变化的业务环境作出一致和快速的响应。
• MEGAFMEGAF 是实现符合 ISO/IEC/IEEE 42010架构框架定义的架构框架的基础设施。Praxeme 是一个开放的企业方法论，包含一个名为企业系统拓扑(Enterprise System Topology，EST)的企业架构框架。 TRAK 是一个基于 MODAF 1.2的通用系统导向框架，以 GPL/GFDL 发布。
• Sherwood Applied Business Security Architecture (SABSA) SABSA 是用于企业安全体系结构和服务管理的开放框架和方法，它是基于风险的，侧重于将安全性集成到业务和 IT 管理中。

Proprietary frameworks

• ASSIMPLER Framework – an architecture framework, based on the work of Mandar Vanarse at Wipro in 2002
• Avancier Methods (AM) Processes and documentation advice for enterprise and solution architects, supported by training and certification.
• BRM (Build-Run-Manage) Framework - an architecture framework created by Sanjeev "Sunny" Mishra during his early days at IBM in 2000.
• Capgemini Integrated Architecture Framework (IAF) – from Capgemini company in 1993
• Dragon1 - An open Visual Enterprise Architecture Method recently recognized by The Open Group as Architecture Framework
• DYA framework developed by Sogeti since 2004.
• Dynamic Enterprise Enterprise architecture concept based on Web 2.0 technology
• Extended Enterprise Architecture Framework - from Institute For Enterprise Architecture Developments in 2003
• EACOE Framework [3] – an Enterprise Architecture framework, as an elaboration of the work of John Zachman
• IBM Information FrameWork (IFW) – conceived by Roger Evernden in 1996
• Infomet - conceived by Pieter Viljoen in 1990
• Labnaf - Unified Framework for Driving Enterprise Transformations
• Pragmatic Enterprise Architecture Framework (PEAF) - part of Pragmatic Family of Frameworks developed by Kevin Lee Smith, Pragmatic EA, from 2008
• Purdue Enterprise Reference Architecture developed by Theodore J. Williams at the Purdue University early 1990s.
• SAP Enterprise Architecture Framework
• Service-oriented modeling framework (SOMF), based on the work of Michael Bell
• Solution Architecting Mechanism (SAM) – A coherent architecture framework consisting of a set of integral modules.
• Zachman Framework – an architecture framework, based on the work of John Zachman at IBM in the 1980s

• ASSIMPLER Framework – an architecture framework, based on the work of Mandar Vanarse at Wipro in 2002
• Avancier Methods (AM)Avancier Methods (AM) Processes and documentation advice for enterprise and solution architects, supported by training and certification.
• BRM (Build-Run-Manage) Framework - an architecture framework created by Sanjeev "Sunny" Mishra during his early days at IBM in 2000.
• Capgemini Integrated Architecture Framework (IAF) – from Capgemini company in 1993
• Dragon1 - An open Visual Enterprise Architecture Method recently recognized by The Open Group as Architecture Framework
• DYA framework developed by Sogeti since 2004.
• Dynamic Enterprise Enterprise architecture concept based on Web 2.0 technology
• Extended Enterprise Architecture Framework - from Institute For Enterprise Architecture Developments in 2003
• EACOE Framework – an Enterprise Architecture framework, as an elaboration of the work of John Zachman
• IBM Information FrameWork (IFW) – conceived by Roger Evernden in 1996
• Infomet - conceived by Pieter Viljoen in 1990
• Labnaf Labnaf - Unified Framework for Driving Enterprise Transformations
• Pragmatic Enterprise Architecture Framework (PEAF)Pragmatic EA - part of Pragmatic Family of Frameworks developed by Kevin Lee Smith, Pragmatic EA, from 2008
• Purdue Enterprise Reference Architecture developed by Theodore J. Williams at the Purdue University early 1990s.
• SAP Enterprise Architecture Framework
• Service-oriented modeling framework (SOMF), based on the work of Michael Bell
• Solution Architecting Mechanism (SAM)Solution Architecting Mechanism (SAM) – A coherent architecture framework consisting of a set of integral modules.Tony Shan and Winnie Hua (2006). Solution Architecting Mechanism. Proceedings of the 10th IEEE International EDOC Enterprise Computing Conference (EDOC 2006), October 2006, p23-32.
• Zachman Framework – an architecture framework, based on the work of John Zachman at IBM in the 1980s

ASSIMPLER 框架——一个基于2002年 Wipro 公司 Mandar Vanarse 工作的架构框架

• Avancier Method (AM) Avancier Method (AM)流程和文档建议，为企业和解决方案架构师提供培训和认证支持。
• BRM (Build-Run-Management) Framework ——一个由 Sanjeev“ Sunny”Mishra 在2000年在 IBM 的早期创建的架构框架。
• Capgemini 集成架构框架(IAF)——来自 Capgemini 公司，于1993年
• Dragon 1——最近被 Open Group 认可为架构框架的开放视觉企业架构方法
• 自2004年以来 Sogeti 开发的 DYA 框架。
• 基于 Web 2.0技术的动态企业架构概念
• 扩展的企业架构框架——来自2003年的企业架构开发研究所
• EACOE 框架——一个企业架构框架，作为对约翰 · 扎克曼工作的阐述
• IBM 信息框架(IFW)——由罗杰 · 埃文登在1996年构思
• 信息网络——由彼得 · 维尔约恩在1990年构思
• Labnaf Labnaf ——驱动企业变革的统一框架
• 实用企业架构框架(peAF)实用电子学——由凯文 · 李 · 史密斯开发的实用框架家族的一部分，实用电子学，从2008年开始
• 普渡大学企业参考架构，由西奥多 · J · 威廉姆斯在20世纪90年代初开发。
• SAP 企业架构框架
• 面向服务的建模框架(SOMF) ，基于 Michael Bell 的工作
• 解决方案架构机制(SAM)解决方案架构机制(SAM)-由一组完整的模块组成的一致的架构框架。单仲偕及华(2006)。解决方案架构机制。第十届 IEEE 国际 EDOC 企业计算会议论文集(EDOC 2006) ，2006年10月，第23-32页。
• Zachman Framework ——一个架构框架，基于 IBM 的 John Zachman 在20世纪80年代的工作

= 另见 =

• Architecture patterns (EA reference architecture)
• EABOK (The Guide to the Enterprise Architecture Body of Knowledge)
• Enterprise architecture
• Enterprise architecture artifacts
• Enterprise architecture planning
• Enterprise engineering
• ISO/IEC/IEEE 42010
• Reference architecture

• Architecture patterns (EA reference architecture)
• EABOK (The Guide to the Enterprise Architecture Body of Knowledge)
• Enterprise architecture
• Enterprise architecture artifacts
• Enterprise architecture planning
• Enterprise engineering
• ISO/IEC/IEEE 42010
• Reference architecture

• 企业架构
• 企业架构工件
• 企业架构规划
• 企业工程
• ISO/IEC/IEEE 42010
• 参考架构

External links

• Enterprise Architecture Frameworks: The Fad of the Century (July 2016)
• A Comparison of the Top Four Enterprise Architecture Frameworks (July 2021)

• Enterprise Architecture Frameworks: The Fad of the Century (July 2016)
• A Comparison of the Top Four Enterprise Architecture Frameworks (July 2021)

= 外部链接 =

• 企业架构框架: 世纪风尚(2016年7月)
• 四大企业架构框架的比较(2021年7月)

Category:Enterprise architecture

类别: 企业架构

ja:エンタープライズアーキテクチャフレームワーク

ja:エンタープライズアーキテクチャフレームワーク

This page was moved from wikipedia:en:Enterprise architecture framework. Its edit history can be viewed at 企业架构框架/edithistory