自顶向下方法的缺点包括。
自顶向下方法，称为域分解。
现在，让我们从逻辑的角度来研究自顶向下方法。
Now, let's take a look at the top-down approach from a logical perspective.
[计算机网络自顶向下方法]。
自顶向下方法的优点包括。
使用自顶向下方法开发“Print”Web服务。
Developing the "Print" web service using the top-down approach.
业务架构模型和业务过程模型都是自顶向下方法的一部分。
The business architecture model and the business process model are both part of the top-down approach.
服务组件提供与业务保持一致的服务接口——自顶向下方法。
A service component provides the service interfaces that are aligned to the business-a top-down approach.
它与自顶向下方法的差别并不大——但起点差异很大。
It's not that much different from the top-down approach — but the starting point is very different.
Web服务开发的自底向上及自顶向下方法都有其各自的优点和缺点。
The bottom-up and the top-down approaches to Web services development both have advantages and disadvantages.
自顶向下方法考虑由企业SOA中间件应用程序组成的应用程序的目标。
The top-down approach considers the goal of an application that comprises the enterprise SOA middleware application.
在非直接公开场景中，重点在使用自顶向下方法标识与业务一致的服务。
In the indirect exposure scenario, the focus is mainly on identification of business-aligned services using a top-down approach.
使用自顶向下方法的主要目的是为了方便审计师选择他们希望控制测试。
The main purpose of using a top down approach is to make it easy for auditors to choose which controls they wish to test.
在自顶向下方法中，将首先从高级业务用例或组织中存在的业务流程流开始。
In a top-down approach, you begin with high-level business use cases or business-process flows that exist within your organization.
我们曾指出，有两种方式来构建应用程序，自顶向下方法和自底向上的方法。
As we have pointed out, there are two general ways to build an application, a top-down approach and a bottom-up approach.
在使用自顶向下方法的过程中，您通常要在业务任务中标识出各种服务操作。
During a top-down approach, you typically identify service operations from business tasks.
本系列的第3部分还介绍了如何使用自顶向下方法将遗留应用程序作为服务公开。
Part 3 of this series also showed how a legacy application can be surfaced using a top-down approach.
您也可以将自顶向下方法嵌入到第二个自顶向下方法，接着再嵌入到自底向上方法。
You could also embed the top-down approach within the second top-down approach and in turn, the bottom-up approach.
使用自顶向下方法创建Web服务的第一步就是创建我们的WSDL文档。
The first step in the top-down approach to Web service creation is to create our WSDL document.
自顶向下方法旨在分解业务元素（主要是业务流程和用例），然后将它们细化为适合服务的粒度。
The top-down approach is about decomposing business elements (mainly business processes and use cases) and refining them into a granularity that makes sense for services.
在自顶向下方法中，首先从顶级流程活动开始，此活动分组为三个或更多基本的流程活动。
In a top-down fashion, you start with the top-level process activity that is grouped into three or more levels of process activities.
例如，通过将旁路方法嵌入到自顶向下方法，接着嵌入到自底向上方法，您可以做到这一点。
You do this by embedding, for example, the sideway approach within the top-down approach and in turn, the bottom-up approach.
自顶向下方法是由业务进行驱动的：存在可作为参考信息来确定SOA服务的业务文档。
The top-down approach is business driven: Business documentation exists that can serve as references to identify your SOA services.
用于用例建模的方法可以视为SOA设计的自顶向下方法，服务操作基于所需的场合进行标识。
The approach to use case modeling can be considered a top-down approach for SOA design, where service operations are identified based on where they are needed.
自顶向下方法从Web服务或非web服务中间件应用程序金字塔(请参见图1)的顶端开始。
The top-down approach starts from the top of a pyramid (see Figure 1) with a middleware application of Web services or non-Web services.
多数情况下，您会使用自顶向下方法完成应用程序的某些部分，并使用自底向上方法完成其他部分。
Most likely, you will do some parts of an application with a top-down approach and others with a bottom-up approach.
支持自顶向下方法的工具通常要比支持自底向上方法的工具有更多的限制，但这种情况正在逐渐改进。
Tools support for the top-down approach has generally been more limited than the support for bottom-up, but that support is improving.
正如前面提到的，创建Web服务的最佳实践是自顶向下方法，即根据WSDL和模式创建Web服务。
As discussed, a best practice for creating a Web service is a top-down approach, starting from WSDLs and schemas.
首先，请遵循自顶向下方法中的步骤 1-3a，这主要是为了生成所谓的DTO（可能根据基于标准的XSD）。
First, Steps 1-3a of the top-down method are used, primarily to produce the so-called DTOs (possibly based on standards-based XSDs).
在这个嵌套、两级嵌入式方法示例中，您可以在自底向上方法中嵌入自顶向下方法(请参见图4)，或者反过来。
In the example of the nested, two-level embedding approach, you can embed the top-down approach within the bottom-up approach (see Figure 4) or the other way around.
应用推荐