UML2.51邊譯邊學(xué)-部署圖
本文是UML規(guī)范2.5.1中部署圖相關(guān)部分中文翻譯。原文可從https://www.omg.org/spec/UML/2.5.1下載。
19.1 Summary（總結(jié)）
The Deployments package specifies constructs that can be used to define the execution architecture of systems and the assignment of software artifacts to system elements. A streamlined model of deployment, sufficient for the majority of modern applications, is provided. Where more elaborate deployment models are required, the package can be extended through profiles or metamodels to represent specific hardware and/or software environments.?
部署包指定了可用于定義系統(tǒng)執(zhí)行架構(gòu)和軟件模塊如何分配到系統(tǒng)要素。它提供了一個(gè)足以滿足大多數(shù)現(xiàn)代應(yīng)用需要的精簡的部署模型。在需要更復(fù)雜的部署模型的地方，可以通過配置文件或元模型擴(kuò)展部署包以表示特定的硬件和/或軟件環(huán)境。
19.2 Deployments（部署關(guān)系）
19.2.1 Summary（總結(jié)）
Deployments capture relationships between logical and/or physical elements of systems and information technology assets assigned to them.
部署關(guān)系用于表現(xiàn)系統(tǒng)的邏輯和/或物理元素與分配給它們的信息技術(shù)制品之間的關(guān)系。
19.2.3 Semantics（語義）
A Deployment captures the relationship between a particular conceptual or physical element of a modeled system and the information assets assigned to it. System elements are represented as DeployedTargets, and information assets, as DeployedArtifacts. DeploymentTargets and DeploymentArtifacts are abstract classes that cannot be directly instantiated. They are, however, elaborated as concrete classes as described in the Artifacts and Nodes sub clauses that follow.
部署關(guān)系表現(xiàn)建模對(duì)象系統(tǒng)的特定概念或物理元素與分配給它的信息資產(chǎn)之間的關(guān)系。系統(tǒng)元素表示為部署對(duì)象，信息資產(chǎn)表示為被部署制品。部署對(duì)象和被部署制品是不能直接實(shí)例化的抽象類。然而，它們被詳細(xì)闡述為具體類，如隨后的工件和節(jié)點(diǎn)子條款中所述。
Individual Deployment relationships can be tailored for specific uses by adding DeploymentSpecifications containing configurational and/or parametric information and may be extended in specific component profiles. For example, standard, non-normative stereotypes that a profile might add to DeploymentSpecification include ?concurrencyMode?, with tagged values {thread, process, none}, and ?transactionMode?, with tagged values {transaction,
nestedTransaction, none}.
可以通過添加包含配置和/或參數(shù)信息的部署定義來針對(duì)特定用途定制各個(gè)部署關(guān)系，并且可以在特定組件配置文件中進(jìn)行擴(kuò)展。例如，配置文件可能添加到?部署定義的標(biāo)準(zhǔn)、非規(guī)范構(gòu)造型包括 ?并發(fā)模式?，帶有標(biāo)記值 {線程,進(jìn)程,無} 和 ?事務(wù)模式?，帶有標(biāo)記值 {事務(wù), 嵌套事務(wù)，無}。
The Deployment relationship between a DeployedArtifact and a DeploymentTarget can be defined at the “type” level and at the “instance” level. At the “type” level, the Deployment connects kinds of DeploymentTargets to kinds of DeployedArtifacts. Whereas, at the “instance” level, the Deployment connects particular DeploymentTargets instances to particular DeployedArtifacts instances. For example, a ”type” level Deployment might connect an “applicationserver” with an “order entry request handler.” In contrast, at the ”instance” level, three specific application services (say, “app-server1”, “app-server-2” and “app-server3”) may be the DeploymentTargets for six different “request handler” instances.
被部署制品和部署對(duì)象之間的部署關(guān)系可以按照“類型”或“實(shí)例”觀點(diǎn)進(jìn)行定義。?按照“類型”觀點(diǎn)，部署關(guān)系將各種部署對(duì)象連接到各種被部署制品。而按照“實(shí)例”觀點(diǎn)，部署將特定的部署對(duì)象實(shí)例連接到特定的被部署制品實(shí)例。例如，“類型”觀點(diǎn)的部署可能會(huì)將“應(yīng)用程序服務(wù)器”與“訂單輸入請(qǐng)求處理程序”連接起來。相比之下，按照“實(shí)例”觀點(diǎn)，三個(gè)特定的應(yīng)用程序服務(wù)（例如，“app-server1”、“app-server-2”和“app-server3”）可能是六個(gè)不同“請(qǐng)求處理程序”實(shí)例的部署對(duì)象。
For modeling complex models consisting of composite structures, a Property, functioning as a part (i.e., owned by a?composition), may be the target of a Deployment. Likewise, InstanceSpecifications can be DeploymentTargets in a Deployment relationship, if they represent a Node that functions as a part within an encompassing Node composition hierarchy, or if they represent an Artifact.
對(duì)于由復(fù)合結(jié)構(gòu)組成的復(fù)雜模型的建模，屬性作為一個(gè)部分（即由組合擁有）可能成為部署的目標(biāo)。同樣，實(shí)例定義可以是部署關(guān)系中的部署對(duì)象，如果它們代表一個(gè)節(jié)點(diǎn)作為包含節(jié)點(diǎn)的組合層次結(jié)構(gòu)中的一部分，或者如果它們代表一個(gè)制品。
譯者注：下面的例子可以看作是通過配置文件控制制品行為的畫法實(shí)例。
19.3 Artifacts（制品）
19.3.1 Summary（總結(jié)）
An Artifact represents some (usually reifiable) item of information that is used or produced by a software development?process or by operation of a system. Examples of Artifacts include model files, source files, scripts, executable files, database tables, development deliverables, word-processing documents, and mail messages.
制品表示由軟件開發(fā)過程或系統(tǒng)操作使用或產(chǎn)生的一些（通常是可具體化的）信息項(xiàng)。?制品的示例包括模型文件、源文件、腳本、可執(zhí)行文件、數(shù)據(jù)庫表、開發(fā)可交付成果、文字處理文檔和郵件消息。
19.3.3 Semantics（語義）
Artifacts elaborate and reify the abstract notion of DeployedArtifact. They represent concrete elements in the physical?world, may have Properties representing their features and Operations that can be performed their instances, and may be multiply-instantiated so that different instances may be deployed to various DeploymentTargets, each with separate property values.
制品詳細(xì)闡述并具體化了被部署制品的抽象概念。它們代表物理世界中的具體元素，可以具有代表它們的特性和可以在它們的實(shí)例中執(zhí)行的操作，并且可以被多重實(shí)例化，以便不同的實(shí)例可以部署到不同的部署目標(biāo)，每個(gè)具有單獨(dú)的屬性值。
More complex Artifacts can be created by organizing them into composition hierarchies. In this way, a DeploymentSpecification for a component may be contained within an Artifact, allowing a component and its parameters to be deployed as a single Artifact instance.
可以通過將制品組織成組合層次結(jié)構(gòu)來創(chuàng)建更復(fù)雜的制品。通過這種方式，組件的部署定義可以包含在工件中，從而允許將組件及其參數(shù)部署為單個(gè)組件實(shí)例。
Artifacts may be extended to better represent the needs of specific information items. For example, profiles may extend Artifact to model sets of files. UML defines several standard stereotypes for Artifacts, including ?source? and ?executable?, that may be further specialized as needed. For example, an EJB profile might define ?jar? as a subclass of ?executable? for executable Java archives.
可以擴(kuò)展制品以更好地表示特定信息項(xiàng)的需求。例如，配置文件可以將制品擴(kuò)展到模型文件集。UML 為制品定義了幾個(gè)標(biāo)準(zhǔn)構(gòu)造型，包括 ?source? 和 ?executable?，可以根據(jù)需要進(jìn)一步專門化。例如，EJB 配置文件可能將 ?jar? 定義為可執(zhí)行 Java 存檔的 ?executable? 的子類。
An Artifact may embody, or manifest, a number of model elements. The Artifact owns the Manifestations, each representing the utilization of some PackageableElement. Profiles may extend the Manifestation relationship to indicate particular forms of embodiment. For example, ?tool generated? and ?custom code? might be two Manifestations for
different Classes embodied in an Artifact.
制品可能包含或體現(xiàn)多個(gè)模型元素。?制品擁有若干表現(xiàn)定義，每個(gè)表現(xiàn)定義代表某些包元素的利用率。配置文件可以擴(kuò)展表現(xiàn)關(guān)系以指示特定形式的實(shí)施例。例如，?工具生成? 和 ?自定義代碼? 可能是兩個(gè)不同的類體現(xiàn)在一個(gè)制品中時(shí)的表現(xiàn)定義。
19.4 Nodes（節(jié)點(diǎn)）
19.4.1 Summary（總結(jié)）
Nodes elaborate and reify the abstract notion of DeploymentTargets. They can be nested and can be connected into?systems of arbitrary complexity using communication paths. Typically, Nodes represent either hardware devices or software execution environments.
節(jié)點(diǎn)詳細(xì)闡述并具體化了部署對(duì)象的抽象概念。它們可以嵌套并且可以使用通信路徑連接到任意復(fù)雜的系統(tǒng)中。通常，節(jié)點(diǎn)代表硬件設(shè)備或軟件執(zhí)行環(huán)境。
19.4.3 Semantics（語義）
A Node is computational resource upon which Artifacts may be deployed, via Deployment relationships, for execution. For advanced modeling applications, Nodes may have complex internal structure defined by nesting and may be interconnected to represent specific situations. The internal structure of Nodes can only consist of other Nodes. Besides?participating in Deployments, Nodes acquire a set of associated elements derived from the Manifestation relationships of the Artifacts deployed on them.
節(jié)點(diǎn)是計(jì)算資源，可以通過部署關(guān)系在其上部署制品以供執(zhí)行。對(duì)于高級(jí)建模應(yīng)用程序，節(jié)點(diǎn)可能具有由嵌套定義的復(fù)雜內(nèi)部結(jié)構(gòu)，并且可以互連以表示特定情況。?節(jié)點(diǎn)的內(nèi)部結(jié)構(gòu)只能由其他節(jié)點(diǎn)組成。除了參與部署之外，節(jié)點(diǎn)還需要一組關(guān)聯(lián)元素，這些元素源自部署在其上的制品的表現(xiàn)關(guān)系。
Nodes may be further sub-typed as Devices and ExecutionEnvironments. Devices represent physical machine components. ExecutionEnvironments represent standard software systems that application components may require at execution time. Specific profiles might, for example, define stereotypes for ExecutionEnvironments such as ?OS?, ?workflow engine?, ?database system?, and ?J2EE container?.
節(jié)點(diǎn)可以進(jìn)一步細(xì)分為設(shè)備和執(zhí)行環(huán)境。設(shè)備代表物理機(jī)器組件。?執(zhí)行表示應(yīng)用程序組件在執(zhí)行時(shí)可能需要的標(biāo)準(zhǔn)軟件系統(tǒng)。例如，特定的配置文件可能會(huì)定義執(zhí)行環(huán)境的構(gòu)造型，例如《OS》、《工作流引擎》、《數(shù)據(jù)庫系統(tǒng)》和《J2EE 容器》。
A Device is a physical computational resource with processing capability upon which Artifacts may be deployed for?execution. Devices may be complex (i.e., they may consist of other devices) either through namespace ownership or through attributes that are themselves typed by Devices. Entire physical computing systems may be decomposed into?their constituents in this way. Examples of Devices might include ?application server?, ?client workstation?, ?mobile?device?, and ?embedded device?.
設(shè)備是具有處理能力的物理計(jì)算資源，可以在其上部署制品以執(zhí)行。設(shè)備可能很復(fù)雜（即，它們可能由其他設(shè)備組成），或者通過名稱空間所有權(quán)或通過設(shè)備本身定義的屬性。整個(gè)物理計(jì)算系統(tǒng)可以通過這種方式分解成它們的組成部分。設(shè)備的示例可能包括《應(yīng)用服務(wù)器》、《客戶端工作站》、《移動(dòng)設(shè)備》和《嵌入式設(shè)備》。
Typically, ExecutionEnvironments are assigned to some, often higher level, Device or general system Node via the composition relationship defined on Node. ExecutionEnvironments can be nested (for example, a database ExecutionEnvironment might be nested in an operating system ExecutionEnvironment). ExecutionEnvironment may have explicit interfaces for system level services that can be called by the deployed elements. In such cases, software ExecutionEnvironment services should be explicitly modeled. Application Components of the appropriate type are then deployed, with a Deployment relationship, to specific ExecutionEnvironment nodes or the Manifestations relationships?of DeployedArtifacts. For each component Deployment, aspects of these services may be determined by properties in a
DeploymentSpecification for a particular kind of ExecutionEnvironment.
通常，執(zhí)行環(huán)境通過 Node.js 上定義的組合關(guān)系分配給一些通常更高級(jí)別的設(shè)備或通用系統(tǒng)節(jié)點(diǎn)。?執(zhí)行環(huán)境可以嵌套（例如，數(shù)據(jù)庫執(zhí)行環(huán)境可能嵌套在操作系統(tǒng)執(zhí)行環(huán)境中）。執(zhí)行環(huán)境可能具有系統(tǒng)級(jí)服務(wù)的顯式接口，可以由部署的元素調(diào)用。在這種情況下，應(yīng)該對(duì)軟件執(zhí)行環(huán)境服務(wù)進(jìn)行顯式建模。然后將具有部署關(guān)系的適當(dāng)類型的應(yīng)用程序組件部署到特定的節(jié)執(zhí)行環(huán)境節(jié)點(diǎn)或?被部署制品的表現(xiàn)關(guān)系。對(duì)于每個(gè)組件部署，這些服務(wù)的方面可能由
特定類型的執(zhí)行環(huán)境的部署定義。
Nodes can be connected to represent specific network topologies using CommunicationPaths defining specific connections between Node instances. A CommunicationPath is an Association between two DeploymentTargets,?through which they may exchange Signals and Messages.
可以使用定義節(jié)點(diǎn)實(shí)例之間的特定連接的通信路徑來連接節(jié)點(diǎn)以表示特定的網(wǎng)絡(luò)拓?fù)洹?通信路徑是兩個(gè)部署對(duì)象之間的關(guān)聯(lián)，通過它它們可以交換信號(hào)和消息。
作者著作介紹
《實(shí)戰(zhàn)Python設(shè)計(jì)模式》是作者去年3月份出版的技術(shù)書籍，該書利用Python 的標(biāo)準(zhǔn)GUI 工具包tkinter，通過可執(zhí)行的示例對(duì)23 個(gè)設(shè)計(jì)模式逐個(gè)進(jìn)行說明。這樣一方面可以使讀者了解真實(shí)的軟件開發(fā)工作中每個(gè)設(shè)計(jì)模式的運(yùn)用場(chǎng)景和想要解決的問題；另一方面通過對(duì)這些問題的解決過程進(jìn)行說明，讓讀者明白在編寫代碼時(shí)如何判斷使用設(shè)計(jì)模式的利弊，并合理運(yùn)用設(shè)計(jì)模式。
對(duì)設(shè)計(jì)模式感興趣而且希望隨學(xué)隨用的讀者通過本書可以快速跨越從理解到運(yùn)用的門檻；希望學(xué)習(xí)Python GUI 編程的讀者可以將本書中的示例作為設(shè)計(jì)和開發(fā)的參考；使用Python 語言進(jìn)行圖像分析、數(shù)據(jù)處理工作的讀者可以直接以本書中的示例為基礎(chǔ)，迅速構(gòu)建自己的系統(tǒng)架構(gòu)。
覺得本文有幫助？請(qǐng)分享給更多人。
關(guān)注微信公眾號(hào)【面向?qū)ο笏伎肌枯p松學(xué)習(xí)每一天！
面向?qū)ο箝_發(fā)，面向?qū)ο笏伎迹?/span>