Figure 1 shows a typical Web-based application pattern that is very common in a Web development scenario.
图1显示了基于Web的典型应用程序模式，在Web开发场景中，它是一种非常普通的模式。
Understand how you can use these technologies, by exploring a sample development scenario that includes.
通过研究一个示例场景，理解如何使用这些技术，该示例场景包括？
The development scenario described in subsequent sections of this article makes use of the following software.
本文后面部分所述的开发场景使用了以下软件。
This three-part article series answers that question by walking you through an end-to-end development scenario.
这个分三部分的文章系列将带领您研究一个端到端开发场景，以此回答这个问题。
Note that this development scenario involves using Hibernate to present an object-based view of existing persistent data.
注意，这一开发场景需要使用Hibernate将已有持久性数据表示成基于对象的视图。
In the sections that follow, I'll show you some of the features of AJDT that come into play in a simple development scenario.
在下一小节中，我将介绍在简单开发场景中发挥作用的一些AJDT特性。
I'll explain the pros and cons of each and offer tips for deciding which one is best suited to your application development scenario.
我会解释每种技术各自的优劣，并提供一些技巧，来确定最适合您的应用开发场景。
Well, let's unpack the role of a typical it knowledge worker within a familiar system development scenario, then follow the action as work begins.
那好，让我们先看看在彼此熟知的系统开发场景中，典型IT知识工作者的角色，然后再观察当工作开始后，都发生了哪些活动。
The sections that follow illustrate in detail how to work with the integration by imitating a real-life parallel development scenario between two users.
接下来的部分具体演示了通过模拟两个用户之间真实的并发开发场景，来具体演示如何将不同人员的工作集成起来。
Under this model, developers can focus more on their particular development scenario, rather than too much on the underlying operating system processing.
在该模型下，开发人员能够将更多精力集中在其特定的开发情景中，而不用过多地关注操作系统底层的处理。
To illustrate another way that robust build management can help make developers -- and the entire team -- more efficient, let's envision another typical software development scenario.
为了说明健壮的构建管理可以令开发人员 ——以及整个团队 ——更高效的另一种方法，让我们来想象另一个典型的软件开发情景。
The UCM processes that impact the deployment activities are primarily in the build and deployment scenarios; the development scenario of UCM has minimal impact with regards to deployment.
UCM过程中影响部署活动的主要是构建和部署模式；UCM过程的开发模式对部署来说影响很小。
Also, gain an understanding of the basic capabilities of these technologies, consider the potential business benefits of deploying them together, and explore a sample development scenario.
我们将理解这两种技术的基本功能，考虑将它们部署在一起的潜在商业益处，并研究一个示例开发场景。
Customization for this scenario is only required in the application code, and does not require development of a new login module.
这个场景只需要在应用程序代码中进行自定义，而不需要开发一个新的登录模块。
Hence, the development approach that is followed is not the classic "waterfall" scenario, where requirements gathering is followed by analysis and design, leading to the implementation of the system.
因此，随后的开发方法不是典型的“瀑布”方案，在瀑布方案中，收集需求之后进行分析和设计，并进行系统的实现。
As a sample scenario to demonstrate the development and deployment of a portal application, you'll develop an application for purchasing tickets.
作为一个演示门户应用程序的开发及部署的样例场景，您将开发一个购票应用程序。
Even though only one application was used for application development and scenario execution, application development consumed a significant amount of time in an iteration.
即使只有一个应用程序用于应用程序开发和场景执行，应用程序开发还是耗费迭代中的大量时间。
The scenario includes configuring a test server and testing an EAB component in the development environment.
这种情形涉及了配置测试服务器以及在开发环境中测试EAB组件。
The most likely scenario for using the deployment descriptor username and password is during initial development testing.
使用部署描述符用户名和密码的最可能场景是在初始化开发测试过程中。
In this series, you'll learn how to use the Model Driven Development approach to develop a business scenario.
在本系列中，可以学习如何用模型驱动开发方法来开发业务场景。
Learn more about software installation and how a productive development environment should work in this kind of scenario.
了解软件安装以及高生产率的开发环境在这种场景中应该采用何种工作方式。
If you do use-case driven development, a usage scenario is typically an instance of a complete use case scenario, or a portion of the use case scenario.
如果你确实执行了用例驱动式开发，那么使用场景就是一个典型的完整用例情景的实例，或者用例情景的一部分。
This merge scenario is the reverse of the operation usually associated with the classic parallel development three-way merge pattern.
该合并方案是倒转通常与经典的平行开发三方合并模式相关联的操作。
Sequential development is the simplest scenario.
串行开发是最简单的方案。
Waiting until the very end of the development lifecycle to begin load testing is probably the worst performance testing scenario.
如果您等到开发周期快结束时才开始负载测试，那么您很可能遇到最坏的性能测试情景。
It also used a simple scenario to illustrate a TDD style of development.
此外还使用了一个简单的场景来演示TDD风格的开发。
OO development focuses on incremental development of applications, implementing one business scenario or use case at a time.
OO开发集中于应用程序的渐进式开发，每次实现一个业务场景或用况。
We'll use the familiar travel reservation scenario to illustrate how these new technologies ease the development of dynamic e-business systems.
我们将使用大家熟悉的旅程预订情景来说明这些新技术是如何简化动态电子商务系统的开发的。
This business scenario illustrates the software development process from inception through post-deployment management.
这个业务场景解释说明贯穿了整个软件开发过程。
In this scenario, a full software development lifecycle cost analysis is not required, but you should keep an eye on the capability-maturity models (CMM) of the process if you can.
这种情况下不需要完整的软件开发生命周期成本分析，但是如果可能的话应关注此过程中的能力成熟度模型(CMM)。
应用推荐