TOGAF 9：企业连续体和架构存储库之间的区别
我试图理解 TOGAF 9 的核心概念。
无论我多久阅读 TOGAF 手册中的解释，我都不明白 Enterprise Continuum 和 Architecture Repository 之间的差异和关系。
文档中的一些引用：
Enterprise Continuum
“企业连续体最简单的思考方式是作为所有架构资产的存储库的视图。它可以包含架构描述、模型、构建块、模式、观点和其他工件”
“企业连续体为理解架构模型提供了有价值的背景：它显示了构建块和 它们之间的关系，以及架构开发周期的约束和要求。” （第 565 页和第 48 页）
架构存储库
“TOGAF 的这一部分为架构存储库提供了一个结构框架，允许企业区分组织中不同抽象级别上存在的不同类型的架构资产。” （第 593 页）
假设
TOGAF 的示例/模板包包含一个文字文档“TOGAF 9 Template - Architecture Repository.doc”，因此
1)
2) 企业连续体是另一个文档，它将架构存储库的内容从基础架构分类到组织架构，并提供有关这些对象之间关系的信息。
企业连续体和架构存储库之间有什么区别/关系？
I am trying to understand the core concepts of TOGAF 9.
No matter how often I read the explanation in the TOGAF manual, I don't understand the differences and the relationship between the Enterprise Continuum and the Architecture Repository.
Some quotes from the documentation:
Enterprise Continuum
"The simplest way of thinking of the Enterprise Continuum is as a view of the repository of all the architecture assets. It can contain architecture descriptions, models, building blocks, patterns, viewpoints, and other artifacts"
"The Enterprise Continuum provides a valuable context for understanding architectural models: it shows building blocks and
their relationships to each other, and the constraints and requirements on a cycle of architecture development."
(pages 565 and 48)
Architecture Repository
"This section of TOGAF provides a structural framework for an Architecture Repository that allows an enterprise to distinguish between different types of architectural assets that exist at different levels of abstraction in the organization."
(page 593)
Assumptions
The samples/template-package of TOGAF contains a word document "TOGAF 9 Template - Architecture Repository.doc", so
1) I think of the architecture repository as a large document, containing all outputs of all projects related to the architecture.
2) The enterprise continuum is another document classifying the contents of the architecture repository from foundation architecture to organization architecture and providing information about the relationship between these objects.
What is the difference/relationship between the enterprise continuum and the architecture repository?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（10）
架构存储库是内容 - 您的所有设计、策略、框架等。
连续体是您对它们进行分类的方法。这不仅仅是基础->组织方面的问题。它涵盖了所有内容，因此根据上面的内容，您将获得第三方框架、业务原则、技术标准以及您企业中存在的所有这些内容的分类。
EC 内存在架构连续体和解决方案连续体。您可以在此处根据基金会、CSA、行业和组织级别对 ABB 和 SBB 进行分类。
The architecture repository is the content - all your designs, policies, frameworks etc.
The continuum is the means by which you classify them. It's not just where something is in terms of foundation->organisation. It covers everything, so as per above you will have classifications of 3rd party frameworks, business principles, Technical Standards, all those things too that are present in your enterprise.
Within the EC exists the Architecture Continuum and the Solutions Continuum. THis is where you classify your ABB's and SBB's according to the Foundation, CSA, Industry, and Organisation tiers.
企业连续体 = 架构连续体 + 解决方案连续体
什么是连续体
连续体模型将变化解释为涉及逐渐的定量过渡，而不会突然变化或不连续。
企业连续体提供了一种一致的语言来传达 用于对架构和解决方案工件进行分类的
1。架构连续体
架构连续体=基础架构+通用系统架构+行业架构+组织架构，
其中
基础架构为产品和服务提供方向和策略，非常高水平、通用、
通用系统架构创建了一个可用于构建通用和通用系统架构的架构。跨广泛相关领域的可重用解决方案，其中一些示例包括安全架构、电子邮件架构和网络架构
行业架构更具行业特定性，例如，无论哪个运营商在哪个国家/地区运营，电信行业都可能遵循一些标准，Active Store Arch对于零售行业来说，电信行业的eTOM
组织架构更多地与特定的企业或组织相关，针对特定的组织需求量身定制，每个业务部门可能有不同的需求，每个部门可能有不同的组织特定架构。它们的要求更加具体，
2。解决方案连续体
解决方案连续体 = 产品和服务 + 系统解决方案 + 行业解决方案 + 组织解决方案
示例
产品：需要根据审批链进行采购
服务：需要是顶级的，包括使用课程材料进行面对面培训
系统解决方案：仅需要实施经过认证和品牌的系统
行业解决方案：如果比开发自己的选择更好，则从行业领导者那里采购可重复使用的组件
组织解决方案：实施提供所需业务功能的企业架构
所有内容都在企业连续体中协同工作
Enterprise Continuum = Architecture Continuum + Solution Continuum
What is Continuum
Continuum models explain variation as involving a gradual quantitative transition without abrupt changes or discontinuities
The Enterprise Continuum provides a consistent language to communicate the differences between architectures so that Architectures and Solutions can be re-used, Also EC is
1. Architecture Continuum
Architectural Continuum = Foundation Architecture + Common System Architecture + Industry Architecture + Organization Architecture
where
Foundation Architecture provides direction and strategies for products and services, Very High level, Generic,
Common System Architecture create an architecture useful for building common and reusable solutions across a wide number of relevant domains, Some of the examples are Security Architecture, Email Architecture and Network Architecture
Industry Architecture is more Industry Specific , for example telecom industry might follow some standards no matter which operator operates in which country, Active Store Arch for Retail Industry, eTOM for Telecom Industry
Organization Architecture is more related to Specific Enterprise or Organization, Tailored for Specific Org Needs, Each Business Divisions might have different needs , and each Divisions might have different Org Specific Architecture. They are more requirement specific,
2. Solutions Continuum
Solution Continuum = Products and Services + System Solutions + Industry Solution + Organization Solution
example
Products : Need to be procured based on Approval chain
Services : Need to be top class including In Person Training with Course Material
System Solutions : Only Certified and Branded Systems need to be implemented
Industry Solutions : Procure Re-usable components from Industry leaders if it is better choice than to develop your own
Organization Solutions : Implementation of the EnterpriseArchitecture that provides therequired business functions
All working together in Enterprise Continuum
架构存储库是架构工件的列表。
Enterprise Continuum 向您展示如何参与企业生活 - 例如如何以及何时更新架构存储库。
Architecture Repository is the list of Architecture Artifacts.
Enterprise Continuum shows your way how to participate in the Enterprise life - how and when to update Architecture Repository for example.
企业连续体是您对架构文档进行排序的方式。下图说明了企业连续体概念：
企业连续体如何工作？
架构存储库是企业架构文档的实际集合。它按照企业连续体建议的结构进行组织。
其他 TOGAF 概念解释如下： https://www.digitalroadmap .management/blog/2019/1/13/what-is-togaf
The Enterprise Continuum is the way HOW you sort your architecture documents. The following pictures illustrates the Enterprise Continuum concept:
How does the Enterprise Continuum work?
The Architecture repository is the actual collection of architecture documents of an enterprise. It is organized with the structure that the Enterprise Continuum suggests.
Other TOGAF concepts are explained here: https://www.digitalroadmap.management/blog/2019/1/13/what-is-togaf
用外行人的话来回答你的问题
架构存储库是一个很大的文档，包含与架构相关的所有项目的所有输出。
企业连续体是另一个文档，对架构存储库的内容进行分类，从最基本的基础架构发展到组织架构（从基础到特定于应用程序），并提供有关这些对象之间关系的信息。
注意：架构连续体相互关联的解决方案连续体以及
To Answer your question in layman terms
Architecture repository is a large document, containing all outputs of all projects related to the architecture.
Enterprise continuum is another document classifying the contents of the architecture repository evolving from the most basic foundation architecture to organization architecture (from basic to application specific) and providing information about the relationship between these objects.
Note That: Architecture Continuum inter-relating solutions continuum as well
以下描述有助于区分框架和存储库。
从 TOGAF 8 定义来看，我发现它比下面所述的 TOGAF 9 定义更清晰。
The following description was helpful in differentiating the framework from the repository.
From TOGAF 8 definition which I find clearer than TOGAF 9 definition stated below.
架构连续体提供了一个框架或方法，用于对架构资产进行分类，使得访问架构资产并将其传达给各个利益相关者变得容易且易于理解。这里的问题是，建筑工件是由各种模型构建的，这必然会产生具有不同符号的资产描述，这必然会导致沟通和理解变得困难。所以对我来说，更多的是建筑文物如何存储在建筑景观中。
另一方面，架构存储库关注架构工件/资产的物理存储位置，以及在某种程度上存储它的哪些方面。
Architecture Continuum provides a framework or methods for classifying Architectural assets in a manner that makes accessing and communicating them to various stakeholders easy and understandable. The issue here is that Architectural Artifacts are build from various models, and this is bound to come up with assets descriptions with different notations, which is bound to make communication and understanding difficult. So to me its more of HOW Architectural Artifacts are stored in the Architecture Landscape.
On the other hand Architecture Repository focuses at WHERE physically the Architectural artifacts/Assets are stored and to some extend WHAT aspects of it are stored.
来自开放组/核心概念 (http://pubs.opengroup。 org/architecture/togaf9-doc/arch/chap02.html#tag_02_06)：企业连续体是架构的视图存储库（强调已添加）。
而存储库是以特定方式组织的工件的存储。
From Open Group / Core concepts (http://pubs.opengroup.org/architecture/togaf9-doc/arch/chap02.html#tag_02_06): The Enterprise Continuum is a view of the Architecture Repository (emphasis added).
Whereas the repository is the store of artifacts, organised in a specific manner.
这是我的 2 美分价值。
Enterprise Continuum 不仅是架构框架内的文档集合，而且可用于架构以提高效率、速度和准确性。内容存储在企业存储库中，该存储库还存储架构存储库。
架构存储库特定于手头的项目，该项目处于 EA 的完全控制之下。这包括 ADM 周期的工件和可交付成果。
Here is my 2 cents worth.
Enterprise Continuum is the collection of documents not just within architecture framework but can be used for the architecture to improve efficiency, speed and accuracy. The contents are stored in Enterprise Repository which will also store Architecture Repository
Architecture repository is specific to the project at hand which is under the complete control of EAs. This includes artificats and deliverables from the ADM cycle.
首先，Enterprise Continuum 不是像 Architecture Repository 那样的物理存储库。这是一种关于基础物理建筑资产的报告，根据您的方便进行分类。一种方法是将它们分类为基础、通用系统、行业和组织特定。例如，EC 就像查询 Oracle 数据库中的底层架构存储库。
First of all, Enterprise Continuum is not a physical repository like Architecture Repository. It's a kind of a report on the underlying physical architectural assets classified according to your convenience. One way to do is to classify them as Foundation, Common System, Industry and Org Specific. EC is like querying the underling architecture repository in an Oracle database for example.