体系架构（Enterprise Architecture, EA）的开山之作，之前一直引用，从来没有系统的学习，通过翻译加深理解，与感兴趣的朋友一起学习探讨。讲完了三列内容，文章来到了尾声，在文章的结论了，又再一次强调了架构是多维的集合，视角不同架构呈现也不同。
翻译中有一些是自己的理解，不对的地方大家多多指正。
结论
Conclusions
当被问及“什么是信息系统架构？”答案是，“没有一个信息系统架构，而是一组架构！”架构是相对的概念，架构是什么，取决于你在做什么。例如，请参见表6。
When the question is asked, “What isinformation systems architecture?” the answer is, “There is not an informationsystems architecture, but a set of them!” Architecture is relative. What youthink architecture is depends on what you are doing. For an example, see Table6.
不同的角色相互之间沟通信息系统体系架构往往很困难，因为存在一组架构，而不是一个。没有说那一个架构一定是正确的或是错误的，不同视角架构是不同的，但又相互关联和互补。实际应用中，可以根据资源的情况，选择性选取特定架构去设计和开发。但是同时，任何一种架构的缺失都会存在一些风险。
We are having difficulties communicatingwith one another about information systems architecture, because a set ofarchitectural representations exists, instead of a single architecture. One isnot right and another wrong. The architectures are different. They are additiveand complementary. There are reasons for electing to expend the resources fordeveloping each architectural representation. And there are risks associatedwith not developing any one of the architectural representations.
对框架中每个架构的明确定义的正在进一步研究中，通过明确定义，可以更好的理解设计的目标，明确每个架构的设计初衷，厘清每个架构缺失会带来的风险，同时明确每个单元格的“产出”模板和用法。
Research is being done to create moreexplicit definitions for each of the architectural representations in thisframework, to understand the design issues, the reasons for developing eachrepresentation, the risks associated with not developing any one, and the“tool” implications of each cell.
<<未完待更>>
