企业架构

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

25px  此article介紹的是the technique/methodology。For Sparx Systems Enterprise Architect, see Enterprise Architect (software).

Enterprise architecture (EA) is an analytical discipline that provides methods to comprehensively define, organize, standardize, and document an organization’s structure and interrelationships in terms of certain critical business domains (physical, organizational, technical, etc.) characterizing the entity under analysis. The goal of EA is to create an effective representation of the business enterprise that may be used at all levels of stewardship to guide, optimize, and transform the business as it responds to real-world conditions. EA serves to capture the relationships and interactions between domain elements as described by their processes, functions, applications, events, data, and employed technologies.

Enterprise architecture (EA) is an analytical discipline that provides methods to comprehensively define, organize, standardize, and document an organization’s structure and interrelationships in terms of certain critical business domains (physical, organizational, technical, etc.) characterizing the entity under analysis. The goal of EA is to create an effective representation of the business enterprise that may be used at all levels of stewardship to guide, optimize, and transform the business as it responds to real-world conditions. EA serves to capture the relationships and interactions between domain elements as described by their processes, functions, applications, events, data, and employed technologies.

企业架构(Enterprise Architecture，EA)是一门分析学科，它提供方法来全面定义、组织、标准化和记录一个组织的结构以及某些关键业务领域(物理、组织、技术等)的相互关系描述被分析的实体。EA 的目标是创建一个业务企业的有效表示，可以在各级管理中使用它来指导、优化和转换业务，因为它对现实世界的条件作出了响应。EA 用于捕获域元素之间的关系和交互，这些关系和交互由它们的过程、功能、应用程序、事件、数据和所使用的技术来描述。

Overview

As practitioners of enterprise architecture, enterprise architects support an organization’s strategic vision by acting to align people, process and technology decisions with actionable goals and objectives that result in quantifiable improvements toward achieving that vision. The practice of enterprise architecture:

As practitioners of enterprise architecture, enterprise architects support an organization’s strategic vision by acting to align people, process and technology decisions with actionable goals and objectives that result in quantifiable improvements toward achieving that vision. The practice of enterprise architecture:

作为企业架构的实践者，企业架构师通过将人员、流程和技术决策与可操作的目标和目标相结合，从而为实现组织的战略愿景提供可量化的改进支持。企业架构的实践:

/* Styling for Template:Quote */ .templatequote { overflow: hidden; margin: 1em 0; padding: 0 40px; } .templatequote .templatequotecite {

   line-height: 1.5em;
   /* @noflip */
   text-align: left;
   /* @noflip */
   padding-left: 1.6em;
   margin-top: 0;

}

/* Styling for Template:Quote */ .templatequote { overflow: hidden; margin: 1em 0; padding: 0 40px; } .templatequote .templatequotecite {

   line-height: 1.5em;
   /* @noflip */
   text-align: left;
   /* @noflip */
   padding-left: 1.6em;
   margin-top: 0;

}

It helps business and IT managers to figure out the best strategies to support and enable business development and business change – in relation to the business information systems that the business depends on.

It helps business and IT managers to figure out the best strategies to support and enable business development and business change – in relation to the business information systems that the business depends on.

它帮助业务和 IT 经理找到支持和启用业务开发和业务变更的最佳策略——与业务所依赖的业务信息系统相关。

= 主题 =

The terms enterprise and architecture

The term enterprise can be defined as describing an organizational unit, organization, or collection of organizations that share a set of common goals and collaborate to provide specific products or services to customers.

The term enterprise can be defined as describing an organizational unit, organization, or collection of organizations that share a set of common goals and collaborate to provide specific products or services to customers.Business Analysis Body of Knowledge, from the International Institute of Business Analysis

术语企业和体系结构可以定义为描述组织单元、组织或组织的集合，这些组织共享一组共同的目标并协作向客户提供特定的产品或服务。商业分析机构的知识，来自国际商业分析研究所

In that sense, the term enterprise covers various types of organizations, regardless of their size, ownership model, operational model, or geographical distribution. It includes those organizations' complete socio-technical systems, including people, information, processes, and technologies.

In that sense, the term enterprise covers various types of organizations, regardless of their size, ownership model, operational model, or geographical distribution. It includes those organizations' complete socio-technical systems,Giachetti, R.E., Design of Enterprise Systems, Theory, Architecture, and Methods, CRC Press, Boca Raton, FL, 2010. including people, information, processes, and technologies.

从这个意义上说，企业这个术语涵盖了各种类型的组织，不管它们的规模、所有权模式、运营模式或地理分布如何。它包括这些组织的完整的社会技术系统，Giachetti，R.E. ，企业系统设计，理论，体系结构和方法，CRC 出版社，Boca Raton，佛罗里达州，2010。包括人、信息、流程和技术。

The term architecture refers to fundamental concepts or properties of a system in its environment, embodied in its elements, relationships, and in the principles of its design and evolution.

The term architecture refers to fundamental concepts or properties of a system in its environment, embodied in its elements, relationships, and in the principles of its design and evolution.

体系结构这个术语是指一个系统在其环境中的基本概念或属性，体现在其元素、关系以及设计和演化的原则中。

Understood as a socio-technical system, the term enterprise defines the scope of the enterprise architecture.

Understood as a socio-technical system, the term enterprise defines the scope of the enterprise architecture.

作为一个社会技术系统，术语企业定义了企业架构的范围。

Scopes

Perspectives, or beliefs, held by enterprise architecture practitioners and scholars, with regards to the meaning of the enterprise architecture, typically gravitate towards one or a hybrid of three schools of thought:

1. Enterprise IT design – the purpose of EA is the greater alignment between IT and business concerns. The main purpose of enterprise architecture is to guide the process of planning and designing the IT/IS capabilities of an enterprise in order to meet desired organizational objectives. Typically, architecture proposals and decisions are limited to the IT/IS aspects of the enterprise; other aspects only serve as inputs.
2. Enterprise integrating – According to this school of thought, the purpose of EA is to achieve greater coherency between the various concerns of an enterprise (HR, IT, Operations, etc.) including the linking between strategy formulation and execution. Typically, architecture proposals and decisions encompass all the aspects of the enterprise.
3. Enterprise ecosystem adaptation – the purpose of EA is to foster and maintain the learning capabilities of enterprises so that they may be sustainable. Consequently, a great deal of emphasis is put on improving the capabilities of the enterprise to improve itself, to innovate and to coevolve with its environment. Typically, proposals and decisions encompass both the enterprise and its environment.

Perspectives, or beliefs, held by enterprise architecture practitioners and scholars, with regards to the meaning of the enterprise architecture, typically gravitate towards one or a hybrid of three schools of thought:Lapalme, J., Three Schools of Thought on Enterprise Architecture, IT Professional, vol. 14, no. 6, pp. 37–43, Nov.–Dec. 2012, doi:10.1109/MITP.2011.109

1. Enterprise IT design – the purpose of EA is the greater alignment between IT and business concerns. The main purpose of enterprise architecture is to guide the process of planning and designing the IT/IS capabilities of an enterprise in order to meet desired organizational objectives. Typically, architecture proposals and decisions are limited to the IT/IS aspects of the enterprise; other aspects only serve as inputs.
2. Enterprise integrating – According to this school of thought, the purpose of EA is to achieve greater coherency between the various concerns of an enterprise (HR, IT, Operations, etc.) including the linking between strategy formulation and execution. Typically, architecture proposals and decisions encompass all the aspects of the enterprise.
3. Enterprise ecosystem adaptation – the purpose of EA is to foster and maintain the learning capabilities of enterprises so that they may be sustainable. Consequently, a great deal of emphasis is put on improving the capabilities of the enterprise to improve itself, to innovate and to coevolve with its environment. Typically, proposals and decisions encompass both the enterprise and its environment.

关于企业架构的意义，企业架构从业者和学者所持有的观点或信念，通常倾向于一种或三种思想流派的混合体: Lapalme，J. ，企业架构的三种思想流派，IT 专业人士，vol。14岁，不。6页。11月37日至12月43日。2012，doi: 10.1109/MITP. 2011.109 # 企业 IT 设计—— EA 的目的是在 IT 和业务关注点之间实现更大的一致性。企业架构的主要目的是指导规划和设计企业 IT/IS 能力的过程，以满足期望的组织目标。通常，架构建议和决策仅限于企业的 IT/IS 方面; 其他方面仅作为输入。# 企业集成——根据这个学派的思想，EA 的目的是在企业的各种关注点(人力资源、 IT、运营等)之间实现更大的一致性包括战略制定和执行之间的联系。通常，体系结构建议和决策包含企业的所有方面。# 企业生态系统适应-企业环境评估的目的是培养和维持企业的学习能力，使其可持续发展。因此，大量的重点是提高企业的能力，以改善自己，创新和共同发展的环境。通常，建议和决策包含企业及其环境。

One’s belief with regards to the meaning of enterprise architecture will impact how one sees its purpose, its scope, the means of achieving it, the skills needed to conduct it, and the locus of responsibility for conducting it

One’s belief with regards to the meaning of enterprise architecture will impact how one sees its purpose, its scope, the means of achieving it, the skills needed to conduct it, and the locus of responsibility for conducting it

一个人对于企业架构意义的信念将影响他如何看待企业架构的目的、范围、实现它的方法、进行企业架构所需的技能以及进行企业架构的责任所在地

Architectural description of an enterprise

See also: Architecture domain

According to the standard ISO/IEC/IEEE 42010, the product used to describe the architecture of a system is called an architectural description. In practice, an architectural description contains a variety of lists, tables, and diagrams. These are models known as views. In the case of enterprise architecture, these models describe the logical business functions or capabilities, business processes, human roles and actors, the physical organization structure, data flows and data stores, business applications and platform applications, hardware, and communications infrastructure.

According to the standard ISO/IEC/IEEE 42010, the product used to describe the architecture of a system is called an architectural description. In practice, an architectural description contains a variety of lists, tables, and diagrams. These are models known as views. In the case of enterprise architecture, these models describe the logical business functions or capabilities, business processes, human roles and actors, the physical organization structure, data flows and data stores, business applications and platform applications, hardware, and communications infrastructure.

根据 ISO/IEC/IEEE 42010标准，用于描述系统架构的产品称为架构描述。在实践中，体系结构描述包含各种列表、表和图表。这些模型被称为视图。在企业架构的情况下，这些模型描述逻辑业务功能或能力、业务流程、人员角色和参与者、物理组织结构、数据流和数据存储、业务应用程序和平台应用程序、硬件和通信基础设施。

The UK National Computing Centre EA best practice guidance states:

The UK National Computing Centre EA best practice guidanceJarvis, Bob (2003) Enterprise Architecture: Understanding the Bigger Picture – A Best Practice Guide for Decision Makers in IT, The UK National Computing Centre, Manchester, UK. p. 9 states:

英国国家计算中心 EA 最佳实践指南(2003)企业架构: 理解更大的图景—— IT 决策者的最佳实践指南，英国曼彻斯特国家计算中心。P. 9国家:

Normally an EA takes the form of a comprehensive set of cohesive models that describe the structure and functions of an enterprise. The individual models in an EA are arranged in a logical manner that provides an ever-increasing level of detail about the enterprise.

Normally an EA takes the form of a comprehensive set of cohesive models that describe the structure and functions of an enterprise. The individual models in an EA are arranged in a logical manner that provides an ever-increasing level of detail about the enterprise.

EA 通常采用一组全面的内聚模型的形式，这些内聚模型描述企业的结构和功能。EA 中的各个模型以一种逻辑方式进行排列，这种方式提供了关于企业的越来越多的详细信息。

The architecture of an enterprise is described with a view to improving the manageability, effectiveness, efficiency, or agility of the business, and ensuring that money spent on information technology (IT) is justified.

The architecture of an enterprise is described with a view to improving the manageability, effectiveness, efficiency, or agility of the business, and ensuring that money spent on information technology (IT) is justified.

描述企业的体系结构是为了提高业务的可管理性、有效性、效率或敏捷性，并确保花在信息技术(IT)上的资金是合理的。

Paramount to changing the enterprise architecture is the identification of a sponsor. His/her mission, vision, and strategy, and the governance framework define all roles, responsibilities, and relationships involved in the anticipated transformation. Changes considered by enterprise architects typically include:

• innovations in the structure or processes of an organization
• innovations in the use of information systems or technologies
• the integration and/or standardization of business processes, and
• improving the quality and timeliness of business information.

Paramount to changing the enterprise architecture is the identification of a sponsor. His/her mission, vision, and strategy, and the governance framework define all roles, responsibilities, and relationships involved in the anticipated transformation. Changes considered by enterprise architects typically include:

• innovations in the structure or processes of an organization
• innovations in the use of information systems or technologies
• the integration and/or standardization of business processes, and
• improving the quality and timeliness of business information.

更改企业架构的首要任务是确定发起人。他/她的任务、愿景和战略以及治理框架定义了预期转换中涉及的所有角色、职责和关系。企业架构师考虑的变化通常包括:

• 组织结构或流程的创新
• 信息系统或技术使用的创新
• 业务流程的集成和/或标准化，以及
• 提高业务信息的质量和及时性。

A methodology for developing and using architecture to guide the transformation of a business from a baseline state to a target state, sometimes through several transition states, is usually known as an enterprise architecture framework. A framework provides a structured collection of processes, techniques, artifact descriptions, reference models, and guidance for the production and use of an enterprise-specific architecture description.

A methodology for developing and using architecture to guide the transformation of a business from a baseline state to a target state, sometimes through several transition states, is usually known as an enterprise architecture framework. A framework provides a structured collection of processes, techniques, artifact descriptions, reference models, and guidance for the production and use of an enterprise-specific architecture description.

开发和使用体系结构来指导业务从基线状态到目标状态(有时经过几个转换状态)的转换的方法通常称为企业体系结构框架。框架为特定于企业的体系结构描述的生产和使用提供了过程、技术、工件描述、参考模型和指南的结构化集合。

Benefits

The benefits of enterprise architecture are achieved through its direct and indirect contributions to organizational goals. It has been found that the most notable benefits of enterprise architecture can be observed in the following areas:

• Organizational design – Enterprise architecture provides support in the areas related to design and re-design of the organizational structures during mergers, acquisitions or during general organizational change.
• Organizational processes and process standards – Enterprise architecture helps enforce discipline and standardization of business processes, and enable process consolidation, reuse, and integration.
• Project portfolio management – Enterprise architecture supports investment decision-making and work prioritization.
• Project management – Enterprise architecture enhances the collaboration and communication between project stakeholders. Enterprise architecture contributes to efficient project scoping and to defining more complete and consistent project deliverables.
• Requirements engineering – Enterprise architecture increases the speed of requirement elicitation and the accuracy of requirement definitions, through publishing of the enterprise architecture documentation.
• System development - Enterprise architecture contributes to optimal system designs and efficient resource allocation during system development and testing.
• IT management and decision making – Enterprise architecture is found to help enforce discipline and standardization of IT planning activities and to contribute to a reduction in time for technology-related decision making.
• IT value – Enterprise architecture helps reduce the system's implementation and operational costs, and minimize replication of IT infrastructure services across business units.
• IT complexity – Enterprise architecture contributes to a reduction in IT complexity, consolidation of data and applications, and to better interoperability of the systems.
• IT openness – Enterprise architecture contributes to more open and responsive IT as reflected through increased accessibility of data for regulatory compliance, and increased transparency of infrastructure changes.
• IT risk management – Enterprise architecture contributes to the reduction of business risks from system failures and security breaches. Enterprise architecture helps reduce risks of project delivery.

The benefits of enterprise architecture are achieved through its direct and indirect contributions to organizational goals. It has been found that the most notable benefits of enterprise architecture can be observed in the following areas:The Contribution of Enterprise Architecture to the Achievement of Organizational Goals: Establishing the Enterprise Architecture Benefits Framework, Technical Report, Department of Information and Computing Sciences Utrecht University, Utrecht, The Netherlands, (2010 online)

• Organizational design – Enterprise architecture provides support in the areas related to design and re-design of the organizational structures during mergers, acquisitions or during general organizational change.Bert Arnold, Martin Op 't Land and Jan Dietz. "Effects of an architectural approach to the implementation of shared service centers," in Second International Workshop on Enterprise, Applications and Services in the Finance Industry (FinanceCom05), Regensburg, Germany, 2005.Jaap Schekkerman. Trends in enterprise architecture 2005: How are organizations progressing? [Online]. 2009(10/20), pp. 33. Available: (online)T. Bucher, R. Fischer, S. Kurpjuweit and R. Winter, "Enterprise architecture analysis and application: An exploratory study," in EDOC Workshop TEAR, Hong Kong, 2006.Nilsson, "Management of technochange in an interorganizational E-government project," in Proceedings of the 41st Annual Hawaii International Conference on System Sciences, 2008, pp. 209.
• Organizational processes and process standards – Enterprise architecture helps enforce discipline and standardization of business processes, and enable process consolidation, reuse, and integration.J. Varnus and N. Panaich. TOGAF 9 enterprise architecture survey results. Presented at 23rd Enterprise Architecture Practitioners Conference. [Online]. Available: www.opengroup.org/public/member/proceedings/q309/q309a/Presentations/pl-varnus-panaich.pdf.Jeanne W. Ross and Peter Weill, "Understanding the Benefits of Enterprise Architecture," CISR Research Briefings, 2005.
• Project portfolio management – Enterprise architecture supports investment decision-making and work prioritization.
• Project management – Enterprise architecture enhances the collaboration and communication between project stakeholders. Enterprise architecture contributes to efficient project scoping and to defining more complete and consistent project deliverables.
• Requirements engineering – Enterprise architecture increases the speed of requirement elicitation and the accuracy of requirement definitions, through publishing of the enterprise architecture documentation.W. Engelsman, M. E. Iacob and H. M. Franken, "Architecture-driven requirements engineering," in Proceedings of the 2009 ACM Symposium on Applied Computing(SAC '09), Honolulu, Hawaii, 2009, pp. 285-286.
• System development - Enterprise architecture contributes to optimal system designs and efficient resource allocation during system development and testing.
• IT management and decision making – Enterprise architecture is found to help enforce discipline and standardization of IT planning activities and to contribute to a reduction in time for technology-related decision making.
• IT value – Enterprise architecture helps reduce the system's implementation and operational costs, and minimize replication of IT infrastructure services across business units.L. Kappelman, T. McGinnis, A. Pettite and A. Sidorova, "Enterprise architecture: Charting the territory for academic research," in AMCIS 2008, 2008.
• IT complexity – Enterprise architecture contributes to a reduction in IT complexity, consolidation of data and applications, and to better interoperability of the systems.
• IT openness – Enterprise architecture contributes to more open and responsive IT as reflected through increased accessibility of data for regulatory compliance, and increased transparency of infrastructure changes.M. Pulkkinen, A. Naumenko and K. Luostarinen, "Managing information security in a business network of machinery maintenance services business - Enterprise architecture as a coordination tool," J. Syst. Softw., vol. 80, pp. 1607-1620, 2007.
• IT risk management – Enterprise architecture contributes to the reduction of business risks from system failures and security breaches. Enterprise architecture helps reduce risks of project delivery.T. Obitz and M. K. Babu. (2009). Enterprise architecture expands its role in strategic business transformation: Infosys enterprise architecture survey 2008/2009. (online).

企业架构的好处是通过其对组织目标的直接和间接贡献来实现的。企业架构最显著的好处可以在以下领域观察到: 企业架构对实现组织目标的贡献: 建立企业架构效益框架，技术报告，信息和计算科学部乌特勒支大学，荷兰乌得勒支，(2010年在线)

• 组织设计-企业架构在合并、收购或一般组织变革期间提供与组织结构的设计和重新设计有关的领域的支持。Bert Arnold Martin Opt Land 和 Jan Dietz。“架构方法对实现共享服务中心的影响”，第二届金融业企业、应用和服务国际研讨会(FinanceCom05) ，雷根斯堡，2005。Jaap Schekkerman.2005年企业架构趋势: 组织进展如何？[在线]。2009(10/20) ，pp.33.可获得: (在线) T. Bucher，R. Fischer，S. Kurpjuweit 和 R. Winter，“企业架构分析和应用: 探索性研究”，EDOC 讲习班 TEAR，香港，2006。Nilsson，“跨组织电子政务项目中的技术变革管理”，发表于第41届夏威夷系统科学国际会议论文集，2008年，pp。209.组织流程和流程标准——企业架构有助于加强业务流程的纪律性和标准化，并支持流程整合、重用和集成。Varnus 和 N. Panaich。TOGAF 9企业架构调查结果。在第23届企业架构从业者会议上发表。[在线]。可供 www.opengroup.org/public/member/proceedings/q309/q309a/presentations/pl-varnus-panaich.pdf : jeannew.Ross 和 peterWeill，“理解企业架构的好处”，CISR 研究简报，2005年。
• 项目组合管理——企业架构支持投资决策和工作优先排序。
• 项目管理——企业架构加强了项目利益攸关方之间的协作和沟通。企业架构有助于有效的项目范围界定和定义更完整和一致的项目可交付成果。
• 需求工程——企业架构通过发布企业架构文档，提高了需求获取的速度和需求定义的准确性。Engelsman，M.E. Iacob and H. M. Franken，“架构驱动的需求工程”，2009年 ACM 应用计算研讨会(SAC’09) ，夏威夷檀香山，2009，pp。285-286.
• 系统开发——在系统开发和测试期间，企业架构有助于优化系统设计和有效的资源分配。
• 信息技术管理和决策——企业架构有助于加强信息技术规划活动的纪律性和标准化，并有助于缩短与技术有关的决策时间。
• IT 价值-企业架构有助于减少系统的实施和运营成本，并最大限度地减少跨业务单位的 IT 基础设施服务的复制。卡佩尔曼，T。麦金尼斯，A。佩蒂特和 A。西多洛娃，“企业架构: 为学术研究绘制领域”，AMCIS 2008,2008。
• IT 复杂性——企业架构有助于降低 IT 复杂性、整合数据和应用程序，并提高系统的互操作性。
• 资讯科技的开放性-企业架构有助提高资讯科技的开放性和应变能力，这反映在守规更容易取得资料，以及基础设施更改的透明度有所提高。机械维修服务业务网络中的信息安全管理——作为协调工具的企业架构。柔软，沃尔。80页。1607-1620, 2007.
• 资讯科技风险管理-企业架构有助减低因系统故障和数字证书认证机构引致的业务风险。企业架构有助于降低项目交付的风险。Obitz 和 M.K. Babu。(2009).企业架构扩大其在战略业务转型中的作用: Infosys 企业架构调查2008/2009。(网上)。

Examples

Documenting the architecture of enterprises is done within the U.S. Federal Government in the context of the Capital Planning and Investment Control (CPIC) process.

Documenting the architecture of enterprises is done within the U.S. Federal GovernmentFederal Government agency success stories, (2010), whitehouse.gov in the context of the Capital Planning and Investment Control (CPIC) process.

企业架构的文档化是在美国联邦政府联邦政府机构的成功故事中完成的，(2010) ，白宫网站，在资本规划和投资控制(CPIC)过程的背景下。

The Federal Enterprise Architecture (FEA) reference model guides federal agencies in the development of their architectures.

The Federal Enterprise Architecture (FEA) reference model guides federal agencies in the development of their architectures.FEA Practice Guidance Federal Enterprise Architecture Program Management Office OMB, (2007), whitehouse.gov

联邦企业架构(FEA)参考模型指导联邦机构开发其架构。 FEA 实践指南联邦企业架构计划管理办公室 OMB，(2007) ，白宫

Companies such as Independence Blue Cross, Intel, Volkswagen AG and InterContinental Hotels Group use enterprise architecture to improve their business architectures as well as to improve business performance and productivity.

Companies such as Independence Blue Cross, Intel, Volkswagen AG"Volkswagen of America: Managing IT Priorities," Harvard Business Review, October 5, 2005, Robert D. Austin, Warren Ritchie, Greggory Garrett and InterContinental Hotels Group use enterprise architecture to improve their business architectures as well as to improve business performance and productivity.

独立蓝十字，英特尔，大众汽车公司“美国大众汽车: 管理 IT 优先事项”，《哈佛商业评论》 ，2005年10月5日，罗伯特 D 奥斯汀，沃伦里奇，格雷戈里加勒特和洲际酒店集团使用企业架构来改善他们的业务架构，以及提高业务绩效和生产力。

For various understandable reasons, commercial organizations rarely publish substantial enterprise architecture descriptions. However, government agencies have begun to publish architectural descriptions they have developed. Examples include:

• US Department of the Interior
• US Department of Defense Business Enterprise Architecture, or the 2008 BEAv5.0 version
• Treasury Enterprise Architecture Framework

For various understandable reasons, commercial organizations rarely publish substantial enterprise architecture descriptions. However, government agencies have begun to publish architectural descriptions they have developed. Examples include:

• US Department of the Interior
• US Department of Defense Business Enterprise Architecture,DoD BEA or the 2008 BEAv5.0 version
• Treasury Enterprise Architecture Framework

出于各种可以理解的原因，商业组织很少发布实质性的企业架构描述。然而，政府机构已经开始公布他们开发的建筑描述。例子包括:

• 美国内政部
• 美国国防部企业架构，国防部 BEA 或2008年 BEAV5.0版本
• 财政部企业架构框架

Relationship to other disciplines

According to the Federation of Enterprise Architecture Professional Organizations (FEAPO), enterprise architecture interacts with a wide array of other disciplines commonly found in business settings. According to FEAPO: /* Styling for Template:Quote */ .templatequote { overflow: hidden; margin: 1em 0; padding: 0 40px; } .templatequote .templatequotecite {

   line-height: 1.5em;
   /* @noflip */
   text-align: left;
   /* @noflip */
   padding-left: 1.6em;
   margin-top: 0;

}

According to the Federation of Enterprise Architecture Professional Organizations (FEAPO), enterprise architecture interacts with a wide array of other disciplines commonly found in business settings. According to FEAPO:

= = 与其他学科的关系 = = 根据企业架构专业组织联合会(Federation of Enterprise Architecture Professional Organization，FEAPO) ，企业架构与业务设置中常见的大量其他学科进行交互。据 FEAPO 报道:

As enterprise architecture has emerged in various organizations, the broad reach has resulted in this business role being included in the information technology governance processes of many organizations. While this may imply that enterprise architecture is closely tied to IT, it should be viewed in the broader context of business optimization in that it addresses business architecture, performance management, and process architecture, as well as more technical subjects.

As enterprise architecture has emerged in various organizations, the broad reach has resulted in this business role being included in the information technology governance processes of many organizations. While this may imply that enterprise architecture is closely tied to IT, it should be viewed in the broader context of business optimization in that it addresses business architecture, performance management, and process architecture, as well as more technical subjects.

随着企业架构在各个组织中出现，其广泛的影响力已导致这一业务角色被纳入许多组织的信息技术治理过程。虽然这可能意味着企业架构与 IT 紧密相连，但是应该在更广泛的业务优化上下文中看待它，因为它涉及业务架构、性能管理和流程架构，以及更多的技术主题。

Discussions of the intersection of enterprise architecture and various IT practices have been published by various IT analysis firms. Gartner and Forrester have stressed the important relationship of enterprise architecture with emerging holistic design practices such as Design Thinking and User Experience Design. Analyst firm Real Story Group suggested that enterprise architecture and the emerging concept of the digital workplace were "two sides to the same coin." The Cutter Consortium describes enterprise architecture as an information and knowledge-based discipline.

Discussions of the intersection of enterprise architecture and various IT practices have been published by various IT analysis firms. Gartner and Forrester have stressed the important relationship of enterprise architecture with emerging holistic design practices such as Design Thinking and User Experience Design.Clay Richardson, Forrester Blogs – Design Thinking Reshapes EA For Dynamic Business, (2013) Joe McKendrick, ZDNet – Gartner urges more 'design thinking' to break enterprise architecture out of its silo, (2010) Leslie Owens, Forrester Blogs – Who Owns Information Architecture? All Of Us., (2010), blogs.forrester.com Analyst firm Real Story Group suggested that enterprise architecture and the emerging concept of the digital workplace were "two sides to the same coin."Tony Byrne, Real Story Group Blog – Digital workplace and enterprise architecture: two sides to same coin, (2012), The Cutter Consortium describes enterprise architecture as an information and knowledge-based discipline.Evernden, Roger. "Dealing with Too Much Data from an Architectural Perspective", November 13, 2012 (online)

关于企业架构和各种 IT 实践的交集的讨论已经由各种 IT 分析公司发布。Gartner 和 Forrester 强调了企业架构与新兴的整体设计实践(如设计思维和用户体验设计)之间的重要关系。Clay Richardson，Forrester Blog-Design Thinking Reshapes EA For Dynamic Business，(2013) Joe McKendrick，ZDNet-Gartner 敦促更多的“设计思维”来打破企业架构的藩篱，(2010) Leslie Owens，Forrester Blog-谁拥有信息架构？Blogs.forrester.com 分析公司 Real Story Group 认为，企业架构和数字化工作场所的新兴概念是“同一枚硬币的两面”。Tony Byrne，Real Story Group Blog-数字化工作场所和企业架构: 同一枚硬币的两面，(2012) ，Cutter Consortium 将企业架构描述为一个信息和知识为基础的学科。埃文登，罗杰。“从架构的角度处理太多的数据”，2012年11月13日(在线)

The enterprise architecture of an organization is too complex and extensive to document in its entirety, so knowledge management techniques provide a way to explore and analyze these hidden, tacit, or implicit areas. In return, enterprise architecture provides a way of documenting the components of an organization and their interaction, in a systemic and holistic way that complements knowledge management.

The enterprise architecture of an organization is too complex and extensive to document in its entirety, so knowledge management techniques provide a way to explore and analyze these hidden, tacit, or implicit areas. In return, enterprise architecture provides a way of documenting the components of an organization and their interaction, in a systemic and holistic way that complements knowledge management.Evernden, Elaine, Evernden, Roger. Information First - Integrating Knowledge and Information Architecture for Business Advantage, Butterworth-Heinemann, Oxford, 2003 (online)

组织的企业架构过于复杂和广泛，无法将其完整地记录下来，因此知识管理技术提供了一种方法来探索和分析这些隐藏的、隐性的或隐性的领域。作为回报，企业架构提供了一种记录组织组件及其相互作用的方法，以一种补充知识管理的系统性和整体性的方式。Evernden.信息第一-集成知识和信息架构的商业优势，Butterworth-Heinemann，牛津，2003(在线)

In various venues, enterprise architecture has been discussed as having a relationship with Service Oriented Architecture, a particular style of application integration. Research points to enterprise architecture promoting the use of SOA as an enterprise-wide integration pattern.

In various venues, enterprise architecture has been discussed as having a relationship with Service Oriented Architecture, a particular style of application integration. Research points to enterprise architecture promoting the use of SOA as an enterprise-wide integration pattern.Christopher Kistasamy, Alta van der Merwe, Andre de la Harpe, (2012), The role of service-oriented architecture as an enabler for Enterprise Architecture, AMCIS 2012, Seattle Washington

在各种场合，企业架构被讨论为与面向服务的体系结构的关系，一种特殊的应用集成风格。研究重点是企业架构如何促进 SOA 作为企业范围的集成模式的使用。Christopher Kistasamy，Alta van der Merwe，Andre de la Harpe，(2012) ，《面向服务的体系结构作为企业架构推动者的角色》 ，AMCIS 2012，西雅图华盛顿

Challenges

Establishing enterprise architecture, as accepted, recognized, functionally integrated and fully involved concept at operational and tactical levels is identified as one of the biggest challenges facing Enterprise Architects today and one of the main reasons why many EA-Initiatives fail.

Challenges

Establishing enterprise architecture, as accepted, recognized, functionally integrated and fully involved concept at operational and tactical levels is identified as one of the biggest challenges facing Enterprise Architects today and one of the main reasons why many EA-Initiatives fail.Dedic, N. (2020). "FEAMI: A Methodology to include and to integrate Enterprise Architecture Processes into Existing Organizational Processes" in IEEE Engineering Management Review. Volume 48, Issue 4. DOI: https://doi.org/10.1109/EMR.2020.3031968

挑战 = = 挑战 = = 建立企业架构，作为被接受的，被认可的，功能集成的和充分参与的概念在操作和战术层面被认为是企业架构师今天面临的最大挑战之一，也是许多 EA-Initiative 失败的主要原因之一。德迪克，N。(2020)。在 IEEE 工程管理评论中的“ FEAMI: 一种将企业架构过程包括并整合到现有组织过程中的方法”。第48卷，第4期。Https://DOI.org/10.1109/emr.2020.3031968

Criticism

Despite the benefits that enterprise architecture claims to provide, for more than a decade, writers and organizations raised concerns about enterprise architecture as an effective practice. Here is a partial list of those objections:

Despite the benefits that enterprise architecture claims to provide, for more than a decade, writers and organizations raised concerns about enterprise architecture as an effective practice. Here is a partial list of those objections:

尽管企业架构声称可以提供好处，但是十多年来，作者和组织都对企业架构作为一种有效的实践表示关注。下面是这些反对意见的部分清单:

• In 2007, computer scientist Ivar Jacobson (a major contributor to UML and pioneer in OO software development) gave his assessment of enterprise architecture: "Around the world introducing an Enterprise Architecture EA has been an initiative for most financial institutions (banks, insurance companies, government, etc.) for the last five years or so, and it is not over. I have been working with such companies and helped some of them to avoid making the worst mistakes. Most EA initiatives failed. My guess is that more than 90% never really resulted in anything useful."
• In a 2007 report, on enterprise architecture, Gartner predicted that "... by 2012 40% of [2007’s] enterprise architecture programs will be stopped."
• A 2008 study performed by Erasmus University Rotterdam and software company IDS Scheer concluded that two-thirds of enterprise architecture projects failed to improve business and IT alignment.

• In 2007, computer scientist Ivar Jacobson (a major contributor to UML and pioneer in OO software development) gave his assessment of enterprise architecture: "Around the world introducing an Enterprise Architecture EA has been an initiative for most financial institutions (banks, insurance companies, government, etc.) for the last five years or so, and it is not over. I have been working with such companies and helped some of them to avoid making the worst mistakes. Most EA initiatives failed. My guess is that more than 90% never really resulted in anything useful."EA Failed Big Way! by Ivar Jacobson. on http://blog.ivarjacobson.com/ October 18, 2007.
• In a 2007 report, on enterprise architecture, Gartner predicted that "... by 2012 40% of [2007’s] enterprise architecture programs will be stopped."Gartner (2007) Gartner Enterprise Architecture Summit: Architecting the Agile Organization, 26 – 27 September 2007. Overview on www.gartner.com. Accessed November 18, 2013.
• A 2008 study performed by Erasmus University Rotterdam and software company IDS Scheer concluded that two-thirds of enterprise architecture projects failed to improve business and IT alignment.S. Roeleven, Sven and J. Broer (2010). "Why Two Thirds of Enterprise Architecture Projects Fail,"

ARIS Expert Paper (online)

在2007年，计算机科学家 Ivar Jacobson (UML 的主要贡献者和面向对象软件开发的先驱)给出了他对企业架构的评估: “在世界各地引入企业架构 EA 已经成为大多数金融机构(银行、保险公司、政府等)的一个倡议在过去的五年左右，这还没有结束。我一直与这样的公司合作，帮助他们中的一些避免犯下最严重的错误。大多数 EA 计划都失败了。我的猜测是，超过90% 的人从来没有真正产生过任何有用的东西。“ EA 失败了！作者: Ivar Jacobson。Http://blog.ivarjacobson.com/于2007年10月18日。在2007年关于企业架构的报告中，Gartner 预测到2012年40% 的企业架构程序将被停止。Gartner (2007) Gartner 企业架构峰会: 构建敏捷组织，2007年9月26-27日。概述 www.gartner. com。2013年11月18日访问。

• 鹿特丹大学和软件公司 IDS Scheer 在2008年进行的一项研究得出结论认为，三分之二的企业架构项目未能改善业务和 IT 的一致性。罗11，斯文和 J。布罗尔(2010)。“为什么三分之二的企业架构项目失败,”ARIS 专家论文(在线)

• In a 2009 article, industry commentator Dion Hinchcliffe wrote that traditional enterprise architecture might be "broken": "At its very best, enterprise architecture provides the bright lines that articulate the full range of possibilities for a business, even describing how to go about getting there. ... Recently there’s a growing realization that traditional enterprise architecture as it’s often practiced today might be broken in some important way. What might be wrong and how to fix it are the questions du jour."
• In 2011, federal enterprise architecture consultant Stanley Gaver released a report that examined problems within the United States federal government’s enterprise architecture program. Mr. Gaver concluded that the federal enterprise architecture program had mostly failed; this conclusion was corroborated by a similar one made by the federal government at an October 2010 meeting that was held to determine why the federal enterprise architecture program was not "as influential and successful as in the past."

• In a 2009 article, industry commentator Dion Hinchcliffe wrote that traditional enterprise architecture might be "broken": "At its very best, enterprise architecture provides the bright lines that articulate the full range of possibilities for a business, even describing how to go about getting there. ... Recently there’s a growing realization that traditional enterprise architecture as it’s often practiced today might be broken in some important way. What might be wrong and how to fix it are the questions du jour."Fixing Enterprise Architecture: Balancing the Forces of Change in the Modern Organization Dion Hinchcliffe, September 3, 2009
• In 2011, federal enterprise architecture consultant Stanley Gaver released a report that examined problems within the United States federal government’s enterprise architecture program. Mr. Gaver concluded that the federal enterprise architecture program had mostly failed; this conclusion was corroborated by a similar one made by the federal government at an October 2010 meeting that was held to determine why the federal enterprise architecture program was not "as influential and successful as in the past.""Why Doesn't the FEA Work"

在2009年的一篇文章中，行业评论员 Dion Hinchcliffe 写道，传统的企业架构可能会被“打破”: “在最好的情况下，企业架构提供了清晰的线条，表达了企业的各种可能性，甚至描述了如何实现这一目标。...最近越来越多的人认识到，传统的企业架构，因为它经常实践今天可能会打破一些重要的方式。什么可能是错误的，以及如何解决它是当今的问题。2009年9月3日，Dion Hinchcliffe

• 2011年，联邦企业架构顾问 Stanley Gaver 发布了一份报告，研究了美国联邦政府企业架构计划中的问题。加弗先生得出的结论是，联邦企业架构计划基本上已经失败; 这一结论得到了联邦政府在2010年10月举行的一次会议上做出的类似结论的证实，该会议旨在确定为什么联邦企业架构计划“不像过去那样有影响力和成功”。“为什么 FEA 不工作”

A key concern about EA has been the difficulty in arriving at metrics of success, because of the broad-brush and often opaque nature of EA projects.

A key concern about EA has been the difficulty in arriving at metrics of success, because of the broad-brush and often opaque nature of EA projects.Measuring Enterprise Architecture Effectiveness: A Focus on Key Performance Indicators, Gunther, W 2014

关于 EA 的一个关键问题是难以达到成功的度量标准，因为 EA 项目的性质是粗略的，而且通常是不透明的。衡量企业架构有效性: 关注关键绩效指标，Gunther，W 2014

See also

• Origins of enterprise architecture
• Enterprise architecture artifacts
• Enterprise architecture framework
• Architectural pattern (computer science)
• Architecture of Integrated Information Systems
• Architecture of Interoperable Information Systems
• John Zachman, promoter of enterprise architecture
• Enterprise Architecture Service Life Cycle - SOMF

• Origins of enterprise architecture
• Enterprise architecture artifacts
• Enterprise architecture framework
• Architectural pattern (computer science)
• Architecture of Integrated Information Systems
• Architecture of Interoperable Information Systems
• John Zachman, promoter of enterprise architecture
• Enterprise Architecture Service Life Cycle - SOMF

企业架构的起源

• 企业架构工件
• 企业架构框架
• 集成信息系统架构
• 可互操作信息系统架构
• John Zachman，企业架构的倡导者
• 企业架构服务生命周期 -SOMF

External links

• 模板:Commons category-inline
• 模板:Wikiquote-inline
• 模板:Wiktionary-inline

= 外部链接 =

Category:Information science Category:Systems engineering

类别: 信息科学类别: 系统工程

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