自底向上方法的显著优点包括。
然后，请遵循自底向上方法中的步骤 2-4。
自底向上方法的缺点包括。
本章介绍一种使用自底向上方法的分析技术。
This chapter describes a technique for parsing using the bottom - up method.
使用自底向上方法开发echo消息Web服务。
Developing the echo message Web service using the bottom-up approach.
您也可以在自顶向下或自底向上方法中嵌入旁路方法。
You could also embed the sideway approach within the top-down or bottom-up approach.
实现对面向服务的体系结构中企业信息系统的访问：自底向上方法。
Implementation of Enterprise Information Systems access in Service-Oriented Architecture: a bottom-up approach.
基本上，如果主要的目标在于集成，自底向上方法是一个不错的出发点。
The opinions gathered on the post agree: the bottom-up is a good approach to start, basically when the main objective is to integrate.
其集成测试中采用自底向上方法，先把低层模块组织成实现某个子功能的模块。
Its integrated testing are carried out from down to up and use lower level module organization to realize the sub-function module at first.
您也可以将自顶向下方法嵌入到第二个自顶向下方法，接着再嵌入到自底向上方法。
You could also embed the top-down approach within the second top-down approach and in turn, the bottom-up approach.
自底向上方法更多是由IT驱动的；业务缺乏关于其策略、功能和核心能力的文档。
The bottom-up approach appears to be more it driven; the business lacks documentation of its strategy, functions, and core competencies.
例如，自底向上方法将分析现有的信息管理系统(IMS)事务或COBOL程序。
For example, the bottom-up approach analyzes existing Information Management System (IMS) transactions or COBOL programs.
分析级别技术(也称为自底向上方法)可用于发现对特定SOA项目有意义的资产。
Analysis level techniques exist, also referred to as bottom-up, to surface the assets that would make sense for a particular SOA project.
从物理的角度来说，自底向上方法将基本的Web服务组件定义为最小的基础部分。
Taking a physical perspective, the bottom-up approach defines a basic Web service component as the smallest part of the foundation.
将现有的应用程序和厂商软件包分解成表示相关操作组的离散服务集(自底向上方法)。
Existing applications and vendor packages are factored into sets of discrete services that represent groups of related operations (bottom-up approach).
例如，通过将旁路方法嵌入到自顶向下方法，接着嵌入到自底向上方法，您可以做到这一点。
You do this by embedding, for example, the sideway approach within the top-down approach and in turn, the bottom-up approach.
多数情况下，您会使用自顶向下方法完成应用程序的某些部分，并使用自底向上方法完成其他部分。
Most likely, you will do some parts of an application with a top-down approach and others with a bottom-up approach.
除了支持自顶向下的模型驱动方法之外，此解决方案方法还允许采用自底向上方法来开发新的服务。
In addition to supporting a top-down model-driven approach, the solution approach enables a bottom-up approach for the development of new services.
支持自顶向下方法的工具通常要比支持自底向上方法的工具有更多的限制，但这种情况正在逐渐改进。
Tools support for the top-down approach has generally been more limited than the support for bottom-up, but that support is improving.
从逻辑的角度来说，自底向上方法从作为SOA企业目标的基础构件的子目标(例如服务组件)开始。
From a logical perspective, the bottom-up approach starts with subgoals (service components, for example) as the building blocks of the foundation for an enterprise goal of an SOA.
使用自底向上方法创建的echo消息Web服务不是可互操作的，因为它的WSDL文档不够完整。
The echo message Web service created using the bottom-up approach is not interoperable as it has an incomplete WSDL document.
从逻辑的角度来说，旁路方法使您能够从在自顶向下或自底向上方法的旁路添加逻辑Web服务的子目标开始。
From a logical perspective, the sideway approach allows you to start by adding a subgoal to the logical Web services at the sideway of either the top-down or bottom-up approach.
在这个嵌套、两级嵌入式方法示例中，您可以在自底向上方法中嵌入自顶向下方法(请参见图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.
从物理的角度来说，旁路方法(如图3所示)允许您在自顶向下或自底向上方法的旁路添加或删除Web服务组件。
From a physical perspective, the sideway approach (shown in Figure 3) allows you to add or delete Web service components sideway to the top-down or bottom-up approach.
自底向上方法旨在分析现有的IT资产(如遗留的应用程序和系统)，找出可以作为服务公开的功能，以便重用它们。
The bottom-up approach is about analyzing existing it assets (such as legacy applications and systems) and finding functionality that could be exposed as services, to be reused by many.
如果从现在你已有的东西去构建服务——使用自底向上方法的话——最终很可能以你有什么而告终，而不是你的用户需要的。
If you start constructing service from what you have - bottom-up - you have a very high risk to end up with what you have, not with what your consumers need.
这个用况场景对采用自底向上方法开发的地址簿web服务与采用自顶向下方法开发的同一个Web服务的互操作性进行了比较。
This use case scenario compares the interoperability of an address book Web service developed using the bottom-up approach to that of the same Web service developed using the top-down approach.
这个用况场景对采用自底向上方法开发的地址簿web服务与采用自顶向下方法开发的同一个Web服务的互操作性进行了比较。
This use case scenario compares the interoperability of an address book Web service developed using the bottom-up approach to that of the same Web service developed using the top-down approach.
应用推荐