体系架构（Enterprise Architecture, EA）的开山之作，之前一直引用，从来没有系统的学习，通过翻译加深理解，与感兴趣的朋友一起学习探讨。作者继续对框架中数据描述列（第一列）的详细（分解视角）架构（第五行）做分析和解读。到这里，数据描述的架构设计阶段就告一段落了。
翻译中自己理解的东西加的比较多，不对的地方大家多多指正。
详细架构（分解视角）-数据描述列。详细架构中也是采用“实体-关系-实体”的描述模型。详细架构是用于指导工程分解实施的架构呈现，例如，数据定义文件（DDL）。比如，一个DBDGEN（IMS层次数据库数据库创建语句），其中实体是“字段”的规范，关系是“地址”的规范。图6显示了一个详细架构的示例。
Detailed description (out-of-context perspective)- data description column. Thedescriptive model is “entity-relationship-entity” in the detailed descriptioncell. This cell is analogous to the subcontractors’ out-of-contextdescriptions. What could be expected is Data Definition Language. An examplemight be a DBDGEN in which the entities are specifications of the “fields,” andrelationships are specifications of the “addresses.” An example is shown inFigure 6.
这种详细的描述将被“编译”以生成机器执行语言，并进一步“链接-处理”以生成保存在机器中的实际物理数据。
This description is “compiled” to producethe machine language representation (relative addressing not shown in the figure), which is further “link-edited” to produce the actual physical data(absolute addressing) residing in the machine.
很明显，现实生活中有很多例子来可以用来说明信息系统的数据（或原料）描述中的各种视角呈现（架构呈现）。
It is clear that real-life examples can befound to illustrate all of the architectural representations for the variousviewpoints or perspectives that are created for the data (or material)description of the information system.
利用已经列举出的例子（图）可以继续推导剩余的架构模型，本文就不再具体展开了。后续，我们将重点分析架构中的术语含义是如何根据视角转移发生变化的。
Although actual samples (figures) for each of the remaining cells are available, no attempt will be made to include them in this paper. Let it be sufficient merely to describe how the meanings of the descriptive model terms change in the remaining two columns as the representations shift from perspective to perspective.
很明显，现实生活中有很多例子来可以用来说明信息系统的数据（或原料）描述中的各种视角呈现（架构呈现）。
It is clear that real-life examples can befound to illustrate all of the architectural representations for the variousviewpoints or perspectives that are created for the data (or material)description of the information system.
<<未完待更>>
