组件图的主要目的是显示系统组件间的结构关系。
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.
组件图是比较容易理解的图之一，因此没有很多超越基础的内容。
The component diagram is one of the easier-to-understand diagrams, so there is not much to cover beyond the basics.
组件图允许一个架构师验证系统的必需功能是由组件实现的，这样确保了最终系统将会被接受。
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.
单击表格中不同的行，就会更新条形图，显示对应组件的数据。
Clicking on different rows on the table updates the bar chart to display data for the corresponding component.
选择输出组件（图42）。
会显示错误输出组件(图49)。
打开Gluecode管理控制台(稍后将看到)，可以看到Gluecode集成的各种组件(图2)。
When opening the Gluecode administration console (which we will look at shortly), one can see the variety of components that have been integrated by Gluecode (Figure 2).
通过Search组件（图6），您可以同时搜索很多不同的位置，节省了在不同的位置寻找答案的时间。
The Search component (Figure 6) enables you to search many different locations concurrently, saving you time looking for answers in different locations.
此中介流组件（图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.
许多系统是在三个主要层次上设计的：系统、子系统和组件，如图1 所示。
Many systems are designed at three primary levels: system, subsystem, and component, as shown in Figure 1.
要在配置模式组件页面(图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.
图1中组件的清单如下。
The components of the diagram shown in Figure 1 are listed below.
SuggestionBox组件（参见图3）提供一种方式来显示有效的选择，使用户不必面对那样极端的情况。
The Suggestion Box component (see Figure 3) offers a way to show valid selections without attempting that unworkable extreme.
我们将首先创建OrderProcessing组件(请参阅图1)，以接收订单和开始处理订单。
We start by creating our OrderProcessing component (see Figure 1) to receive the order and begin working on it.
图2显示连接好的组件。
返回到组装图，并将BPEL流程组件放在其中。
Return to the assembly diagram and drop the BPEL process component there.
这也是我们将中介流组件保留在图10 中的适配器旁边的原因。
This is the reason why we have retained mediation flow components next to each of the adapters in Figure 10.
按照以下方式来指定组件细节(同样见于图4)。
Specify the component details as follows (also see Figure 4).
右键单击CreditDAExport组件并选择 Test Component（图32）。
Right-click on the CreditDAExport component and select Test Component (Figure 32).
图2描述组件、接口和它们依赖的元模型。
Figure 2 Metamodel for components, interfaces, and their dependencies.
图1展示了软件组件如何分布和交互。
Figure 1 shows how the software components are distributed and interact.
图1说明了框架中组件的关系。
Figure 1 illustrates the relationships of components in the framework.
图1展示了WPTA的主要组件。
对于一个30度的角，指针组件应该类似于图3。
For an Angle of 30 degrees, the needle component looks like Figure 3.
应用推荐