The content related to the scenario approach was introduced from the design requirements of "take the user as the center".
从产品设计中“以使用者为中心”的设计要求出发，引入情境故事法的相关内容。
Out of the many possible technical solutions available, you will choose a particular implementation approach that maximizes your potential to learn more from this scenario.
在众多的技术解决方案中，将选择一种特殊的实现方式，从而帮助您从这个场景获得尽可能多的收获。
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.
因此，随后的开发方法不是典型的“瀑布”方案，在瀑布方案中，收集需求之后进行分析和设计，并进行系统的实现。
For example, by focusing on data access or validation, you can prototype and test potential solutions to figure out the best approach for your scenario.
比方说，通过关注数据获取或有效性验证，你能为潜在的解决方案构建原型并进行测试，从而找出适合你的情景的最好的方法。
We will follow a top-down approach to this scenario, first executing the test, then analysing the processing that occurred, and then, finally, looking in detail at the specification of the test step.
我们将对此场景使用自顶向下的方法，即先执行测试，然后分析发生的处理，最后详细了解测试步骤的规范。
Not every possible approach, however, is good for every use case scenario.
然而，不是每种可能的方式对于每个用例场景都是可取的。
We continue with the approach adopted in Part 1, which involves the presentation of the bare minimum implementation scenario to illustrate our intended throttling capability.
我们将继续第1部分中采用的方法，它给出了最简单的实现场景来演示我们准备讨论的调节功能。
Let's replay the scenario just described to illustrate a wait reduction approach.
让我们重放刚描述的用来例举等待减少方法的场景。
In this series, you'll learn how to use the Model Driven Development approach to develop a business scenario.
在本系列中，可以学习如何用模型驱动开发方法来开发业务场景。
Because the model for this scenario is not complicated and does not involve a long modeling approach, this article just covers how to create the model from scratch.
由于此场景中的模型并不复杂，并且未涉及冗长的建模方法，因此本文仅讨论如何从重新开始创建模型。
Clearly, a purely top-down approach is not ideal in this scenario.
明显的是，纯粹的自顶向下的方法在此场景中也是不理想的。
In the indirect exposure scenario, the focus is mainly on identification of business-aligned services using a top-down approach.
在非直接公开场景中，重点在使用自顶向下方法标识与业务一致的服务。
This very rudimentary approach works for the shopping-cart scenario, but may not for others.
这个非常基本的方式可以用于购物车场景，但是可能不适合其他场景。
Even though this scenario isn't included in the sample code available for download with this article, the approach to executing such a query is the same as we discussed in previous examples.
即使该场景没有包含可供本文下载的样例代码，但是执行此类查询的方法与我们在前面例子中讨论的方法是相同的。
The following scenario is a more realistic one that provides insight into how to approach synchronization when you have both model changes and implementation changes, some of which may be in conflict.
接下来的场景更接近于现实情况，它深入探析如何在既有模型更改又有实现更改时实现同步，有些更改可能会有不一致。
We'll use the use-case template for this scenario because we intend to represent our system requirements with a use-case approach.
这个场景采用的是用例模板，因为打算使用用例的方式来表示系统需求。
This approach to incorporating desktop information can be useful outside the scenario given.
除了这里给出的场景外，这种合并桌面信息的方法在其他地方也非常有用。
In a simplified scenario, I'll offer the all-in-one approach and give you a hint on what to do for each checklist item.
在最简单的情况下，我将提供一体化方法，告诉您针对每个清单项都应该做什么。
This month, I walk you through a quality-centered approach to a Struts application testing scenario.
这个月，我要把以质量为核心的方法用于Struts应用程序的测试场景。
This section introduces the New Product Announcement (NPA) scenario from the IBM enterprise, and explains why a solution approach using BEP is needed.
本部分介绍来自IBM企业的新产品声明(New Product An nouncement,NPA)场景，并解释为什么需要某种使用CEP的解决方案方法。
With the db2cos with db2pd approach, you would only see the last statement executed by the lock owner's application - in this scenario the query on the EMPLOYEE table.
使用db 2 cos与db 2 pd相结合的方法，只能看到锁持有者的应用程序执行的最后一条语句—在这个场景中是对employee表的查询。
In this scenario, it's clear that adopting the WS-Encryption approach to encrypt the data isn't a good choice.
在此场景中，采用WS - Encryption方法加密数据显然不是一个好选择。
It's an approach that can help in an Ajax scenario as well.
这种方法在Ajax场景中也会有帮助。
However if the application does not require a distributed scenario, a simpler approach might be used and only the first pipeline will be suffice to accomplish the target execution.
然而如果应用不需要分布式的场景，可以仅使用第一种pipeline将满足【Target】的执行要求。
While I could model the notion of employment using a field in the Person type, that's a relational approach and doesn't fit well within the object-design scenario.
我会用Person类型中的一个字段来模拟雇佣的概念。这是一种关系方法，而且不太适合用于对象设计。
Remember also that you can use both techniques in the same app, choosing the approach that best fits each scenario.
同时，别忘了你可以在同一个应用中同时使用这两种技术，根据场景来选择最合适的方法。
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服务的互操作性进行了比较。
Whereas the EJB spec constraints the approach, Spring provides numerous technology interfaces, allowing you to choose the one that's best for your application scenario or create your own if need be.
虽然EJB规范限制了这种方式，但是Spring提供了大量技术接口，使您可以选择最适合应用程序要求的接口，或者在需要时创建自己的接口。
Based on the general expatiation, the principle and process of this approach were discussed, combined with an example for designing fire scenario of a certain shopping mall.
在总体阐述的基础上，结合某购物广场火灾场景设定的算例对该方法的原则和步骤进行分析。
An approach for multistage scenario generation based on clustering analysis is introduced in this paper.
提出一种基于聚类分析的多阶段情景生成方法，并给出了排除套利的线性规划模型。
应用推荐