UML基本架构建模－－图的术语和概念(二)



Structural Diagrams

The UML’s structural diagrams exist to visualize, specify, construct, and document the static aspects of a system. You can think of the static aspects of a system as representing its relatively stable skeleton and scaffolding. Just as the static aspects of a house encompass the existence and placement of such things as walls, doors, windows, pipes, wires, and vents, so too do the static aspects of a software system encompass the existence and placement of such things as classes, interfaces, collaborations, components, and nodes.

UML的结构图实际是可视化、具体化，结构化和文档化系统的静态方面。你可以将系统的静态方面想象成表现它相对稳定的骨架和脚手架。就像一个房子的静态方面包括实体和如墙、门、窗、管道、线路及通风设施这类事物的安放，一个软件系统的静态方面同样也包括实体和如类、接口、交互、组件及节点的放置。

 

The UML’s structural diagrams are roughly organized around the major groups of things you’ll find when modeling a system.

1.Class diagram

Classes, interfaces, and collaborations

2.Component diagram

components

3.Composite structure diagram

Internal structure

4.Object diagram

Objects

5.Artifact diagram

Artifacts

6.Deployment diagram

Nodes

UML的结构图大致围绕着你构建系统模型时所发现的事物的主要群体。

1.类图

类群，接口群和交互群

2.组件图

组件群

3.复合结构图

内部结构

4.对象图

对象群

5.产品图

产品群

6.部署图

节点群

 

Class Diagram      Aclass diagram shows a set of classes, interfaces, and collaborations and their relationships. Class diagrams are the most common diagram found in modeling object-oriented systems. You use class diagrams to illustrate the static design view of a system. Class diagrams that include active classes are used to address the static process view of a system.

类图      

类图显示一组类，接口和交互以及它们的关系。类图是在构建面向对象系统时最常见的图。使用类图来说明系统的静态设计视图。类图包括被用于解决系统的静态过程的活动类。

 

Component Diagram      Ancomponent diagram shows the internal parts, connectors, and ports that implement a component. When the component is instantiated, copies of its internal parts are also instantiated.

组件图      

组件图显示内部配件、连接器和实现组件的端口。当组件实例化时，它的内部配件的副本也会实例化。

 

Composite Structure Diagram      Ancomposite structure diagramshows the internal structure of a class or a collaboration. The difference between components and composite structure is small and this book treats them both as component diagrams.

复合结构图      

复合结构图显示一个类或一个交互的内部结构。它与组件图的差异很小，在本书中将两者都作为组件图看待。

 

Object Diagram       Anobject diagram shows a set of objects and their relationships. You use object diagrams to illustrate data structures, the static snapshots of instances of the things found in class diagrams. Object diagrams address the static design view or static process view of a system just as class diagrams do, but from the perspective of real or prototypical cases.

对象图      

对象图显示一组对象以及它们的关系。使用对象图来说明数据结构、在类图中发现的事物的实例的静态快照。对象图与类图所做的一样，用来解决系统的静态设计视图和静态过程视图，但其视角来自实际的或典型的案例。

 

Artifact Diagram      Anartifact diagram shows a set of artifacts and their relationships to other artifacts and to the classes that they implement. You use artifact diagrams to show the physical implementation units of the system. (UML considers artifacts to be part of deployment diagrams, but we separate them for convenience of discussion.)

产品图      

产品图显示一组产品，也显示这些产品与其它产品的关系，还显示它们与所实现的类的关系。使用产品图显示系统的物理实现单元。（UML认为产品是部署图的一部分，但是为求方便，我们将它们分开讨论）。

 

Deployment Diagram      Adeployment diagramshows a set of nodes and their relationships. You use deployment diagrams to illustrate the static deployment view of an architecture. Deployment diagrams are related to component diagrams in that a node typically encloses one or more components.

部署图      

部署图显示一组节点和它们的关系。使用部署图来说明一个架构的静态部署视图。部署图是与节点通常包含的一个或多个组件相关的组件图。

 

Note:There are some common variants of these four diagrams, named after their primary purpose. For example, you might create a subsystem diagram to illustrate the structural decomposition of a system into subsystems. A subsystem diagram is just a class diagram that contains, primarily, subsystems.

备注：为它们指定了首要目的后，这四类图有一些常见的变体。例如，你可以创建一个子系统图来说明一个系统分解成子系统后的结构。子系统图仅仅是一个包含主要子系统的类图。