體系架構(gòu)（Enterprise Architecture, EA）的開山之作，之前一直引用，從來沒有系統(tǒng)的學(xué)習(xí)，通過翻譯加深理解，與感興趣的朋友一起學(xué)習(xí)探討。在提出基本框架后，作者從數(shù)據(jù)描述列（第一列）開始詳細(xì)介紹框架中的內(nèi)容，首先圍繞范圍呈現(xiàn)（第一行）做了分析和解讀。

翻譯中自己理解的東西加的比較多，不對的地方大家多多指正。

數(shù)據(jù)描述的架構(gòu)呈現(xiàn)

Architectural representations for?describing data

對應(yīng)圖2，可以了解到數(shù)據(jù)描述列每個(gè)單元格的內(nèi)容以及他們之間的區(qū)別。盡管列中的每個(gè)單元格的架構(gòu)呈現(xiàn)都是與數(shù)據(jù)描述相關(guān)（對應(yīng)描述類型I），并且呈現(xiàn)模式都是“實(shí)體-關(guān)系-實(shí)體”，但“實(shí)體”和“關(guān)系”的含義會隨著架構(gòu)參與方的視角不同而相應(yīng)變化。例外的是范圍呈現(xiàn)（ballpark）中的實(shí)體與業(yè)務(wù)呈現(xiàn)單元格中的實(shí)體是相同的。范圍呈現(xiàn)（ballpark）的視角只是一個(gè)宏觀的描述，就像建筑架構(gòu)師的“氣泡圖”一樣被用來建立數(shù)據(jù)策略的總體規(guī)模和范圍，進(jìn)而決定如何投入資源來處理和管理數(shù)據(jù)。

To illustrate how each cell differs fromall of the others, examine the data description column of Figure 2. Even thoughevery cell in the column is descriptive type I relating to data, and thedescriptive model is “entity-relationship-entity,’’ the meanings of “entity”and “relationship” change with the different perspectives of the participantsin the architecture process. The only exception is the scope description(ballpark) cell, in which entity is defined the same as entity in the model ofthe business cell. This ballpark perspective is merely a very high level ofaggregation which is being used like the architect’s “bubble charts” toestablish the gross size and scope of the data strategy, leading to thedecision regarding investment of data processing resources in managing data.

范圍呈現(xiàn)（ballpark視角）-數(shù)據(jù)列。圖2的數(shù)據(jù)描述列中的范圍呈現(xiàn)單元格是一個(gè)對業(yè)務(wù)相關(guān)的重要事物的列表。

Scope/description (ballpark perspective)-data?column.The scope description cell in the datadescription column of Figure 2 could be expected to be a list of all the thingsthat are important to the business, and therefore, that the business manages.

表5是從范圍的角度看數(shù)據(jù)描述列中的架構(gòu)呈現(xiàn)的示例。

Table 5 is an example of an architecturalrepresentation in the data description column from the scope descriptionperspective.

數(shù)據(jù)描述對應(yīng)的是事物列表（實(shí)物、名詞），而不是動作的列表（過程、動詞）。而在下一列流程描述中則包含操作列表（動詞）。數(shù)據(jù)描述列中的事物（材料）列表在數(shù)據(jù)術(shù)語中被稱為“實(shí)體”。

This representation would be a list ofthings (i.e., material-grammatically, nouns) as opposed to a list of actions(i.e., processes-grammatically, verbs). A list of actions (verbs) could beexpected in the next column, process description. The list of things (material)in the data description column would be called “entities” in data vernacular.

目前主要在范圍一行討論架構(gòu)呈現(xiàn)，實(shí)體（事物）也可以是一類實(shí)體，即在更高層次聚合。利用這些架構(gòu)呈現(xiàn)（實(shí)體）來作范圍的決策，而不是設(shè)計(jì)的決策。選擇什么實(shí)體或?qū)嶓w類，需要考慮利用信息系統(tǒng)的建設(shè)能否實(shí)現(xiàn)數(shù)據(jù)“倉庫”的管理目標(biāo)。

Since this architectural representation isat the scope description row, one could also expect that the entities (things)would likely be entity “classes,” that is, higher levels of aggregation,because the decision being made as a result of this representation would be oneof scope, not one of design. A selection would be being made of the entityclass or classes in which to invest actual information system (I/s) resourcesfor data “inventory” management purposes.

此外，在范圍的單元格中，難以明確確定實(shí)體之間的關(guān)系。范圍的決策，是在所有涉及業(yè)務(wù)價(jià)值的實(shí)體或?qū)嶓w類中，根據(jù)實(shí)際信息系統(tǒng)建設(shè)可以投入的資源，選擇可實(shí)施和管理的實(shí)體類的子集。不過，先形成一個(gè)完整的實(shí)體總列表通常也很有用，有時(shí)，未被選中的實(shí)體與被選中的實(shí)體一樣重要。

Further, in this cell, one might not expect to be definitive about the relationship between entities. The scope decision would constitute overlaying the business values on the total range of possibilities to identify a subset of entity classes for implementation which is consistent with the resources available for investing in information systems-specifically, in this case, the management of the selected class (or classes) of data，F(xiàn)urthermore, it is useful to startwith the total list of entities because, at times, the entities that are notselected are as significant as those that are selected.

戰(zhàn)略/資源投資決策是基于對理解業(yè)務(wù)價(jià)值和發(fā)展戰(zhàn)略做出的，通過信息收集/分析技術(shù)來完成業(yè)務(wù)分析，將分析結(jié)論對照業(yè)務(wù)實(shí)體的總表，選擇實(shí)體的子集來進(jìn)行實(shí)際投資和建設(shè)。由于本文的目的是定義架構(gòu)，而不是描述決策的過程方法，因此后續(xù)除了一些環(huán)節(jié)具有特殊的決策方法外，將不會進(jìn)一步說明決策如何制定。圖2第一一行的范圍描述單元格都具有這種策略/資源投資決策的特點(diǎn)。例如，在總體的業(yè)務(wù)流程列表中，業(yè)務(wù)可能沒有足夠的數(shù)據(jù)處理資源來自動化所有流程，需要選擇一個(gè)子集，在其中投資數(shù)據(jù)處理資源以進(jìn)行實(shí)際自動化。同樣的情況，在業(yè)務(wù)運(yùn)營地點(diǎn)的總列表中，可能沒有足夠的數(shù)據(jù)處理資源來將硬件和軟件放在每個(gè)位置，因此也必須在實(shí)際安裝軟硬件位置做取舍。此外，盡管它們具有一定的聯(lián)系，但是每個(gè)決策的制定都應(yīng)該獨(dú)立于其他決策。

The strategy/resource investment decisionis made by understanding the values/strategies of the business, which can bedone by using various datagathering/analytical techniques. The decision is madeby overlaying the analytical conclusions on the total list of business entitiesin the scope description cell and thereby selecting the subset of businessentities in which to actually invest data processing resources. Since thispaper is intended to define architecture, not to describe strategymethodologies, nothing further will be said about strategic planning except topoint out that similar kinds of decisions have to be made relative to everyother scope description cell. That is, out of the total list of business processes,the business likely does not have enough data processing resources to automateall the processes. Therefore, a decision will have to be made to select asubset in which to invest data processing resources for actual automation. Bythe same token, out of the total list of locations in which the businessoperates, it probably does not have enough data processing resources to puthardware and software in every location. Again, decisions will have to be madein selecting a subset of locations in which to actually install hardware andsoftware. These are the strategy/resource investment decisions that aresupported by the scope description cells in the top row of Figure 2. Althoughthey are inextricably related, the probability is that each decision will haveto be addressed independently of the others. Discussion now continues on theframework, particularly the data description column of Figure 2.

<<未完待更>>