体系架构（Enterprise Architecture, EA）的开山之作，之前一直引用，从来没有系统的学习，通过翻译加深理解，与感兴趣的朋友一起学习探讨。结束了数据描述列，作者继续对框架中流程描述列（第二列）进行解读，分解方法和数据描述列类似。
翻译中自己理解的东西加的比较多，不对的地方大家多多指正。
流程描述的架构呈现
Architectural representations fordescribing the process
流程描述的架构呈现模型是“输入-过程-输出”，与数据描述列的情况一样，对于流程描述列里不同单元格来说，对应架构模型中的“输入”、“过程”和“输出”都代表着不同的含义。
Thedescriptive model for describing the process is input-process-output,” and, asin the case of the data description column, each of the representations in thedifferent cells in the process description column of Figure 2 have differentmeanings associated with “input,” “process,” and “output.”
在范围呈现（ballpark）单元格中，“过程”意味着业务流程，或是一些流程组成的流程集合。从范围呈现单元中，将会选择适当的业务流程，利用信息系统将这些有限的处理实现自动化。判断业务流程有没有价值作为后续信息化实现，不需要确定相关输入、输出。因此，在流程描述的范围呈现单元格中，只需要一个业务流程列表即可。
Atthe scope description (ballpark perspective) cell, “process” would meanbusiness process. It would likely be some process “class,” a relatively highlevel of aggregation, as the decision being made from the scope descriptioncell is the selection of some subset of the appropriate business processes inwhich to invest some finite amount of information systems resources for actualautomation purposes. Further, in making the scope decision, it is unnecessary tobe definitive about the input and output linkages between the functions byoverlaying the business values against the total range of automationpossibilities. Therefore, just a list of business processes would appropriatelybe expected in this cell representation.
<<未完待更>>
