Table 1: Zachman Framework classification matrix.
表1：Zachaman框架分级矩阵。
Application 5: Zachman as an aid during RUP tailoring.
应用5：在rup裁剪过程中，Zachman作为辅助。
Figure 7: Distribution of artifacts according to the Zachman layout.
图7：根据Zachman设计的工件分布。
Application 7: When planning a RUP project, look at the Zachman structure.
应用7：在计划RUP项目时，考虑Zachman结构。
Application 4: Learning RUP alongside Zachman (and vice versa) may be easier.
应用4：和Zachman一起学习RUP(或者相反)可能更加容易。
Simpler realizations can replicate Zachman structure using file system folders.
更简单的实现可以使用文件系统文件夹复制Zachman结构。
Applying RUP to Zachman or vice versa makes for a better overall learning experience.
将RUP应用于Zachman或者相反，有助于更全面的学习经验。
Organizations that favor this approach usually choose Zachman or an equivalent framework.
喜欢此方法的组织通常选择Zachman或等价的框架。
Despite the fact that both RUP and Zachman rely on models, they have virtually no functional overlap.
虽然RUP和Zachman都依赖模型，但实际上它们没有功能交迭。
Application 8: Use RUP with Zachman to help bridge the gap between enterprise and project architecture.
应用8：结合使用Zachman与RUP，来帮助架起企业和项目构架之间的桥梁。
I still believe that most practitioners will find Zachman to be a handy analysis reference during their work.
我仍相信大多数实践人员将会发现Zachman在他们的工作中是便利的分析参考资源。
With its rigid structure, Zachman may be just the right source of information to answer questions like these. 10.
Zachman具有固定的结构，可能恰恰是回答像这样问题的合适的信息来源。
The standard existing enterprise architecture frameworks (including TOGAF, Zachman, and FEAF) share a similar history.
标准的现有企业架构框架(包括TOGAF、Zachman和FEAF)分享着相似的历史。
For example, it would be questionable to use Zachman in a development environment by virtue of its inherent unsuitability.
例如，由于其固有的不适应性，在开发环境中使用Zachman是值得置疑的。
When it comes to supporting a customized enterprise architecture (ea) function in the organization, the Zachman Framework is a great aid.
当涉及支持企业里的定制企业构架(ea)功能时，Zachman框架可以提供很多帮助。
Applying joint use cases across RUP and Zachman may help narrow the gap between the enterprise and its projects, thus making the organization more efficient.
在RUP和Zachman中结合应用用例可以帮助缩小企业与其项目之间的差距，从而使得组织更加有效。
This is actually good news for both enterprise and project architects, as it implies that UML, Zachman, and RUP can be used jointly to deliver better overall enterprise value.
对企业和项目构架师来说这都是好消息，因为那意味着UML、Zachman和RUP可以共同使用以产生更全面的企业价值。
The Zachman Framework for Enterprise Architectures—Although self-described as a framework, is actually more accurately defined as a taxonomy for for organizing architectural artifacts.
企业架构Zachman框架——尽管它自称是一个框架，实际上将其定义为一个组织架构的分类更贴切。
Some aspects of the Zachman structure are formulated as questions like what, where, and how, which are generic to all project types and may be translated into more project-specific questions.
Zachman结构的一些方面通过一些公式化的问题，例如，什么、哪里、如何，来表述，这些问题对所有的项目类型来说是通用的，而且如果有必要，也可以转化成为针对特定项目的问题。
However, the path toward learning Zachman may strongly benefit from the application of some core RUP principles, such as "requirements-driven," "architecture-centric," "model-driven," and "iterative."
尽管如此，学习Zachman的方法可能主要受益于一些RUP主要原则——例如，“需求驱动”、“以构架为中心”、“模型驱动”和“迭代”——的应用。
However, the path toward learning Zachman may strongly benefit from the application of some core RUP principles, such as "requirements-driven," "architecture-centric," "model-driven," and "iterative."
尽管如此，学习Zachman的方法可能主要受益于一些RUP主要原则——例如，“需求驱动”、“以构架为中心”、“模型驱动”和“迭代”——的应用。
应用推荐