體系架構(gòu)（Enterprise Architecture, EA）的開山之作，之前一直引用，從來沒有系統(tǒng)的學(xué)習(xí)，通過翻譯加深理解，與感興趣的朋友一起學(xué)習(xí)探討。

前言

隨著信息系統(tǒng)實(shí)施規(guī)模和難度的不斷增長，如何用邏輯結(jié)構(gòu)（或架構(gòu)）模型定義和管理系統(tǒng)內(nèi)各組件間的接口和集成關(guān)系，已變的越來越重要。本文在信息系統(tǒng)之外的學(xué)科領(lǐng)域抽象出一種中立、客觀的描述性框架，反向類比出信息系統(tǒng)架構(gòu)的定義，同時(shí)，框架推導(dǎo)過程中形成的一些初步結(jié)論也在本文中予以呈現(xiàn)。相關(guān)的探討，僅限于架構(gòu)層面，不包括戰(zhàn)略規(guī)劃層面的方法。

With increasing size and complexity of the implementationsof information systems, it is necessary to use some logical construct (orarchitecture) for defining and controlling the interfaces and the integrationof all of the components of the system.?This paper defines information systems architecture by creating adescriptive framework from disciplines quite independent of informationsystems, then by analogy specifies information systems architecture based uponthe neutral, objective framework. Also, some preliminary conclusions about theimplications of the resultant descriptive framework are drawn. The discussionis limited to architecture and does not include a strategic planningmethodology.

信息系統(tǒng)架構(gòu)正開始受到越來越多的關(guān)注。信息系統(tǒng)實(shí)現(xiàn)范圍和復(fù)雜性的不斷增加，迫切需要通過邏輯結(jié)構(gòu)(或架構(gòu))模型來定義和管理系統(tǒng)內(nèi)各組件接口以集成關(guān)系。三十年前（本文發(fā)表于1987年），在當(dāng)時(shí)的信息技術(shù)條件下，信息系統(tǒng)規(guī)模和復(fù)雜性較低，討論信息系統(tǒng)架構(gòu)是沒有意義的。例如，在4K的計(jì)算機(jī)技術(shù)條件下，一些設(shè)計(jì)和優(yōu)化工作根本無從談起。

The subject of information systems architecture isbeginning to receive considerable attention. The increased scope of design andlevels of complexity of information systems implementations are forcing the useof some logical construct (or architecture) for defining and controlling theinterfaces and the integration of all of the components of the system. Thirtyyears ago this issue was not at all significant because the technology itselfdid not provide for either breadth in scope or depth in complexity ininformation systems. The inherent limitations of the then available 4Kmachines, for example, constrained design and necessitated suboptimalapproaches for automating a business.

技術(shù)的發(fā)展正在迅速消除觀念和成本的限制。在可預(yù)期的未來，將有規(guī)模龐大、復(fù)雜度高的信息系統(tǒng)進(jìn)行實(shí)施，其實(shí)施范圍也將擴(kuò)展至整個(gè)組織層面。我們可以清晰的看到這種大型、復(fù)雜、面向組織級實(shí)施方法的優(yōu)勢——這種系統(tǒng)可以靈活地適應(yīng)業(yè)務(wù)的調(diào)整，并與組織對業(yè)務(wù)資源管理策略保持一致性。當(dāng)然，傳統(tǒng)的、小規(guī)模、次優(yōu)系統(tǒng)方法也有其優(yōu)點(diǎn)。比如，成本低、實(shí)施速度快、易于設(shè)計(jì)和管理等。

Current technology is rapidly removing both conceptual andfinancial constraints. It is not hard to speculate about, if not realize, verylarge, very complex systems implementations, extending in scope and complexityto encompass an entire enterprise. One can readily delineate the merits of thelarge, complex enterprise-oriented approaches. Such systems allow flexibilityin managing business changes and coherency in the management of businessresources. However, there also is merit in the more traditional, smaller,suboptimal systems design approach. Such systems are relatively economical,quickly implemented, and easier to design and manage.

不論以上哪種實(shí)施模式，由于“分布式”概念和技術(shù)的出現(xiàn)，大量的信息系統(tǒng)組件（或應(yīng)用）“分發(fā)”到不同的計(jì)算單元，組件間的結(jié)構(gòu)(或架構(gòu))成為需要明確管理的內(nèi)容，沒有結(jié)構(gòu)將導(dǎo)致混亂。因此，為了防止業(yè)務(wù)碎片化、信息孤島等問題，通過信息系統(tǒng)架構(gòu)來規(guī)范和管理各系統(tǒng)，已成為信息系統(tǒng)投資建設(shè)過程中的必然選擇。業(yè)務(wù)的發(fā)展越來越離不開信息系統(tǒng)的支撐，而信息系統(tǒng)在成本控制還是在實(shí)現(xiàn)效果上的成功，都需要在信息系統(tǒng)管理中引入更加規(guī)范化的方法。

In either case, since the technology permits “distributing”large amounts of computing facilities in small packages to remote locations,some kind of structure (or architecture) is imperative because decentralizationwithout structure is chaos. Therefore, to keep the business fromdisintegrating, the concept of information systems architecture is becomingless an option and more a necessity for establishing some order and control inthe investment of information systems resources. The cost involved and thesuccess of the business depending increasingly on its information systemsrequire a disciplined approach to the management of those systems.

既然我們認(rèn)為對信息系統(tǒng)架構(gòu)的清晰理解對形成一種規(guī)范化的實(shí)施方法非常重要，隨之而來的問題就是“到底什么是信息系統(tǒng)架構(gòu)？”不幸的是，在信息化行業(yè)內(nèi)對“架構(gòu)”的概念和內(nèi)涵還沒有形成一致性的認(rèn)識。而在沒有達(dá)成一致的情況下來談“信息系統(tǒng)架構(gòu)”，純扯！換句話說，從專業(yè)信息化領(lǐng)域抽象出具有通用性、中立性的架構(gòu)概念幾乎是不可能的。要開展對架構(gòu)的定義工作，要換個(gè)視角，找到更為中立、公正、獨(dú)立的開端。

On the assumption that an understanding of informationsystems architecture is important to the development of a disciplined approach,the question that naturally arises is “What, in fact, is information systemsarchitecture?” Unfortunately, among the proponents of information systemsarchitecture, there seems to be little consistency in concepts or inspecifications of “architecture,” to the extent that the words “informationsystems architecture” are already losing their meaning! Furthermore, itprobably is not reasonable to expect reconciliation or commonality ofdefinition to emerge from the professional data processing community itself.The emotional commitment associated with vested interests almost demands aneutral, unbiased, independent source as a prerequisite for any acceptable workin this area.

無論如何，制定某種框架，使各種架構(gòu)概念和方法合理化、規(guī)范化是十分必要的。一方面促進(jìn)專業(yè)、明確的溝通，另一方面，有效的改進(jìn)和集成各種開發(fā)方法和工具，此外，有助于建立對信息系統(tǒng)投資的信任和信心。

In any event, it likely will be necessary to develop somekind of framework for rationalizing the various architectural concepts andspecifications in order to provide for clarity of professional communication,to allow for improving and integrating development methodologies and tools, andto establish credibility and confidence in the investment of systems resources.

雖然信息系統(tǒng)架構(gòu)與組織的戰(zhàn)略、信息化戰(zhàn)略和業(yè)務(wù)戰(zhàn)略息息相關(guān)，但本文的討論范圍聚焦在架構(gòu)，而不涉及如何提出組織戰(zhàn)略規(guī)劃的方法。組織戰(zhàn)略的規(guī)劃以及與信息化戰(zhàn)略的聯(lián)系，最終如何以架構(gòu)的方式體現(xiàn)，是需要研究的重要課題；但它與本文的研究主題不同，本文旨在為信息系統(tǒng)架構(gòu)定義一個(gè)框架。

Although information systems architecture is related tostrategy, both information strategy and business strategy, this paperdeliberately limits itself to architecture and should not be construed aspresenting a strategic planning methodology. The development of a businessstrategy and its linkage to information systems strategies, which ultimatelymanifest them- selves in architectural expression, is an important subject topursue; but it is quite independent of the subject of this work, which isdefining a framework for information systems architecture.

<<未完待更>>?