Summary of Reference
Summary of Reference
Summary of Reference
企业架构
企业架构在工作:
第1章
Chapter 1: Introduction to Enterprise Architecture
Architecture: Essential for managing the complexity of large organizations. It involves creating a
master plan and detailed specifications, much like designing a house.
Enterprise Architecture (EA): A holistic approach to designing an organization's business
processes, IT systems, and infrastructure. It ensures alignment with business objectives and
facilitates flexibility and adaptability.
Definition: According to ISO/IEC/IEEE FDIS 42010:2011, architecture encompasses the
fundamental concepts or properties of a system in its environment, its elements, relationships,
and design principles.
Stakeholders: Individuals or groups with interests in the system. Effective communication
between architects and stakeholders is crucial.
EA Characteristics: Provides a holistic view, balancing local optimization with overall business
needs. It must adapt to changes and align with business objectives.
Architecture Process: Involves steps from initial idea to implementation and maintenance. Clear
communication with stakeholders throughout is vital.
第 1 章:企业架构简介
架构:对于管理大型组织的复杂性至关重要。它涉及创建总体规划和详细规范,就像设计
房屋一样。
企业架构 (EA):一种整体方法,用于设计组织的业务流程、IT 系统和基础设施。它确保与
业务目标的一致性,并促进灵活性和适应性。
定义:根据 ISO/IEC/IEEE FDIS 42010:2011,架构包括系统在其环境中的基本概念或属性、其
元素、关系和设计原则。
利益相关者:对系统感兴趣的个人或群体。架构师与利益相关者之间的有效沟通至关重要。
EA 特征:提供整体视图,平衡局部优化与整体业务需求。必须适应变化并与业务目标保持
一致。
架构过程:包括从初始想法到实施和维护的步骤。与利益相关者的清晰沟通贯穿始终是至
关重要的。
第 2.2.2 章
Chapter 2.2.2: The Zachman Framework
Introduction: Introduced by John Zachman in 1987 as the "Framework for Information Systems
Architecture," it is the first and best-known enterprise architecture framework.
Purpose: Provides a logical structure for classifying and organizing descriptive representations of
an enterprise, significant for both management and system development.
Framework Structure:
Roles: Planner, Owner, Designer, Builder, Subcontractor.
Product Abstractions: What (material), How (process), Where (geometry).
Additional Interrogatives: Who (people), When (time), Why (motivation).
Advantages:
Easy to understand.
Addresses the enterprise as a whole.
Defined independently of tools and methodologies.
Issues can be mapped against it to understand their fit.
Drawbacks:
Large number of cells, making practical applicability challenging.
Relations between different cells are not well specified.
Legacy: Despite drawbacks, it remains a widely used and comprehensive framework for
enterprise architecture.
第 2.2.2 章: 扎克曼框架
简介:由约翰·扎克曼于 1987 年提出,最初称为“信息系统架构框架”,这是第一个也是
最著名的企业架构框架。
目的:提供一个逻辑结构,用于分类和组织企业的描述性表示,这对于企业管理和系统开
发都很重要。
框架结构:
角色:规划者、所有者、设计者、建造者、分包商。
产品抽象:是什么(材料)、如何(过程)、在哪里(几何)。
附加质问:谁(人员)、何时(时间)、为什么(动机)。
优点:
容易理解。
涵盖整个企业。
独立于工具和方法定义。
可以将问题映射到框架中以理解其适应性。
缺点:
单元格数量多,实际应用具有挑战性。
不同单元格之间的关系没有很好地指定。
遗产:尽管有缺点,该框架仍然是广泛使用的全面企业架构框架。
更多
The Zachman Framework
Introduction:
Creator: John Zachman introduced the framework in 1987.
Original Name: Initially called the "Framework for Information Systems Architecture".
Significance: Recognized as the first comprehensive enterprise architecture framework.
Purpose:
Classification and Organization: The framework provides a logical structure to classify and
organize the descriptive representations of an enterprise.
Management and Development: These representations are crucial for both managing the
enterprise and developing its systems.
Framework Structure:
Design Process Roles:
Planner: Responsible for scoping and setting the context.
Owner: Focuses on the enterprise model from a conceptual viewpoint.
Designer: Develops system models at a logical level.
Builder: Constructs technology models at a physical level.
Subcontractor: Deals with detailed representations out of context.
Product Abstractions:
What: The material or data elements of the enterprise.
How: The functions or processes within the enterprise.
Where: The network or geographical distribution of components.
Additional Interrogatives:
Who: The people involved in various roles and activities.
When: The timing and sequencing of events and processes.
Why: The motivations and reasons behind actions and decisions.
Advantages:
Comprehensibility: The framework is straightforward and easy to understand.
Holistic Approach: It addresses the enterprise in its entirety, offering a broad perspective.
Tool and Methodology Independence: Defined independently, it can be applied universally
without being tied to specific tools or methods.
Mapping Issues: Any issues or components can be mapped to the framework to understand their
place and relevance.
Drawbacks:
Complexity: The large number of cells (intersections of roles and abstractions) can make the
framework cumbersome and challenging to apply in practice.
Undefined Relationships: The connections and interactions between different cells are not well-
defined, which can limit its practical utility.
Legacy:
Pioneering Work: Despite its limitations, the Zachman Framework is credited with laying the
foundational groundwork for enterprise architecture.
Continued Use: It remains a widely respected and utilized framework in the field of enterprise
architecture, influencing many subsequent frameworks and methodologies.
扎克曼框架
简介:
创建者:约翰·扎克曼于 1987 年引入该框架。
最初名称:最初称为“信息系统架构框架”。
重要性:被公认为第一个全面的企业架构框架。
目的:
分类和组织:该框架提供了一个逻辑结构,用于分类和组织企业的描述性表示。
管理和开发:这些表示对于企业管理和系统开发都至关重要。
框架结构:
设计过程角色:
规划者:负责范围界定和设定背景。
所有者:从概念角度关注企业模型。
设计者:在逻辑层面开发系统模型。
建造者:在物理层面构建技术模型。
分包商:处理上下文之外的详细表示。
产品抽象:
是什么:企业的材料或数据元素。
如何:企业内的功能或流程。
在哪里:组件的网络或地理分布。
附加质问:
谁:参与各种角色和活动的人员。
何时:事件和流程的时间和顺序。
为什么:行动和决策背后的动机和原因。
优点:
易于理解:该框架简单明了,容易理解。
整体方法:它涵盖整个企业,提供了广泛的视角。
工具和方法独立性:独立定义,可以普遍应用,不依赖于特定的工具或方法。
问题映射:任何问题或组件都可以映射到框架中,以理解它们的位置和相关性。
缺点:
复杂性: 大量的单元格(角色和抽象概念的交叉点)会使框架变得繁琐,在实际应用中具
有挑战性。
未定义的关系: 不同单元之间的联系和互动没有明确定义,这可能会限制其实际效用。
遗产:
开创性工作: 尽管有其局限性,Zachman 框架还是为企业架构奠定了基础。
继续使用:它仍然是企业架构领域广受推崇和使用的框架,影响了许多后续框架和方法。