體系架構(gòu)（Enterprise Architecture, EA）的開(kāi)山之作，之前一直引用，從來(lái)沒(méi)有系統(tǒng)的學(xué)習(xí)，通過(guò)翻譯加深理解，與感興趣的朋友一起學(xué)習(xí)探討。講完了三列內(nèi)容，文章來(lái)到了尾聲，在文章的結(jié)論了，又再一次強(qiáng)調(diào)了架構(gòu)是多維的集合，視角不同架構(gòu)呈現(xiàn)也不同。

翻譯中有一些是自己的理解，不對(duì)的地方大家多多指正。

結(jié)論

Conclusions

當(dāng)被問(wèn)及“什么是信息系統(tǒng)架構(gòu)？”答案是，“沒(méi)有一個(gè)信息系統(tǒng)架構(gòu)，而是一組架構(gòu)！”架構(gòu)是相對(duì)的概念，架構(gòu)是什么，取決于你在做什么。例如，請(qǐng)參見(jiàn)表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.

不同的角色相互之間溝通信息系統(tǒng)體系架構(gòu)往往很困難，因?yàn)榇嬖谝唤M架構(gòu)，而不是一個(gè)。沒(méi)有說(shuō)那一個(gè)架構(gòu)一定是正確的或是錯(cuò)誤的，不同視角架構(gòu)是不同的，但又相互關(guān)聯(lián)和互補(bǔ)。實(shí)際應(yīng)用中，可以根據(jù)資源的情況，選擇性選取特定架構(gòu)去設(shè)計(jì)和開(kāi)發(fā)。但是同時(shí)，任何一種架構(gòu)的缺失都會(huì)存在一些風(fēng)險(xiǎn)。

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.

對(duì)框架中每個(gè)架構(gòu)的明確定義的正在進(jìn)一步研究中，通過(guò)明確定義，可以更好的理解設(shè)計(jì)的目標(biāo)，明確每個(gè)架構(gòu)的設(shè)計(jì)初衷，厘清每個(gè)架構(gòu)缺失會(huì)帶來(lái)的風(fēng)險(xiǎn)，同時(shí)明確每個(gè)單元格的“產(chǎn)出”模板和用法。

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.

<<未完待更>>