随着UML2的轨迹，本文介绍组件图。
Continuing down the track of UML 2 structure diagrams, this article introduces the component diagram.
组件图的主要目的是显示系统组件间的结构关系。
The component diagram's main purpose is to show the structural relationships between the components of a system.
组件图：组件图展示了系统组件之间的结构关系。
Component diagram: a component diagram shows the structural relationships between the components of a system.
图1：UML组件图显示了架构设计中的重要元素
Figure 1: UML component diagram showing architecturally significant elements
除此之外，组件图对于不同的小组是有用的交流工具。
In addition, component diagrams are useful communication tools for various groups.
因此，组件图能够让架构师来验证，组件在实现系统的所需功能。
Therefore, a component diagram allows an architect to verify that components are implementing a system's required functionality.
组件图是比较容易理解的图之一，因此没有很多超越基础的内容。
The component diagram is one of the easier-to-understand diagrams, so there is not much to cover beyond the basics.
然而，所有类之间的关系已经被适当的生成了，产生设计和组件图是相对容易的。
However, with all the relationships between classes already in place, generating design and component diagrams was relatively easy.
组件图允许一个架构师验证系统的必需功能是由组件实现的，这样确保了最终系统将会被接受。
Component diagrams allow an architect to verify that a system's required functionality is being implemented by components, thus ensuring that the eventual system will be acceptable.
为了解释清楚这个难题的各个方面，图1显示了高抽象级别的插件、项目和工件的概念化的组件图。
To help clarify the disparate pieces of this puzzle, Figure 1 shows a conceptual component diagram of the plugins, projects, and artifacts that are involved at a high level.
系统管理员发现组件图是有用的，因为他们可以获得将运行于他们系统上的逻辑软件组件的早期视图。
System administrators find component diagrams useful because they get an early view of the logical software components that will be running on their systems.
关于这一点的理由是，如同我们在这篇文章的其余部分将会见到一样，UML2显著地增强了组件图的符号集。
For that reason, UML 2 dramatically enhances the notation set of the component diagram, as we will see throughout the rest of this article.
利用UML的用例图、类图、时序图、合作图、组件图和部署图等，定义系统需求，描述系统设计。
The system requirements and design models are defined by UML diagrams such as Use Case diagram, Class diagram, Sequence diagram, Collaboration diagram, Component diagram, and Deployment diagram.
定义体系结构：可以通过绘制UM l组件图、类图和序列图，对大型系统结构和设计模式进行建模。
Define the architecture: Model the large-scale structure of the system and the design patterns by drawing UML component, class, and sequence diagrams.
许多系统是在三个主要层次上设计的：系统、子系统和组件，如图1 所示。
Many systems are designed at three primary levels: system, subsystem, and component, as shown in Figure 1.
它们包括类，组件和（或）对象图。
图1演示了这些组件之间的关系。
Figure 1 illustrates the relationship between these components.
要在配置模式组件页面(图3)上创建一个新模式，请在模式名称字段中指定一个模式名并单击添加。
To create a new pattern, on the Configure pattern Components page (figure 3), specify a pattern name in pattern name field and click Add.
此中介流组件（图4）执行请求者数据模型与提供者数据模型间的映射，并且还可以针对诊断或审计的目的进行进一步的日志记录。
The mediation flow component (Figure 4) performs a mapping of the requestor's data model to that of the provider, and perhaps performs some further logging for diagnostics or auditing purposes.
会显示错误输出组件(图49)。
我们在前面提供了使用多个原语的中介流组件实现的图。
Above, we showed a picture of a mediation flow component implementation using a number of primitives.
再次说明，请删除模拟器，以使测试能够流经sca组件(图37)。
Again, remove the emulators to enable the test to flow through the SCA components (Figure 37).
您可以实际看到流经组件的数据(图22)。
You can actually see the data as it flows through the components (Figure 22).
选择输出组件（图42）。
这个架构定义的系统的组件交互在图4 中展示。
The component interaction of the system defined by this architecture is illustrated in Figure 4.
在图4中，根据HLD关系图提供了安全服务的详细组件关系图。
In Figure 4, you provide a detailed component diagram for the security services based on your HLD diagram.
图1中组件的清单如下。
The components of the diagram shown in Figure 1 are listed below.
我们将首先创建OrderProcessing组件(请参阅图1)，以接收订单和开始处理订单。
We start by creating our OrderProcessing component (see Figure 1) to receive the order and begin working on it.
我们将首先创建OrderProcessing组件(请参阅图1)，以接收订单和开始处理订单。
We start by creating our OrderProcessing component (see Figure 1) to receive the order and begin working on it.
应用推荐