这篇文章提供了两个用户场景。
这就是为什么我要提倡使用用户场景。
我们将介绍下列用户场景。
分析用户场景识别工作流模式。
像用户场景一样记录需求。
在下面的示例用户场景中提供了示例用例和典型实现。
A sample use case and a typical implementation is illustrated in a sample user scenario, which follows.
通过重新组织和合并测试模块来构建更大的用户场景。
Build bigger user scenarios by reorganizing and combining test modules.
它的主要目的是通过聚合相关的定制绑定来支持特定的用户场景。
Its main purpose is to aggregate related custom binders to support particular user scenarios.
用户场景不再是纯粹的推测，而是源自于业务过程，并由用户团体验证。
User scenarios are no longer pure conjectures, but have been derived from the business process and validated with the user community.
因此，用户选择使用哪种压缩器主要取决于用户场景对这两个指标的要求。
Thus, the user selection of the compressor to use mainly depends on the requirements of the user's scenario in terms of these two metrics.
每个组件同其他组件一起提供很多方法(如下所示)来实现大多数用户场景。
Each component works with the others to provide a swathe of approaches, as shown below, to achieve most user scenarios.
使得快速更改用户场景变得更加容易，当问题产生时，定位系统的不同部分。
Make it easier to quickly change user scenarios, targeting different parts of the system when issues arise.
在第二部分中，作者将会描述每个服务的详细信息，并会提出实际的用户场景。
In the second half of this paper, the authors will describe the details of each service and present a real-life user scenario.
在本文中，我们将使用典型的用户场景，此场景将作为本系列其他部分的基础。
In this article, you will work with a typical user scenario that will be used as the basis for the rest of the series.
在本文中，我们说明了如何基于典型的用户场景构造业务流并在服务器上进行部署。
In this article, we showed you how to construct a business flow based on a typical user scenario and deploy this on a server.
我发现自己同一群群的用户和开发者一起工作，撰写用户场景，起草用户接口设计。
I find myself working with groups of users and developers to write user scenarios, and sketch user interface design.
以Web应用程序为例，需要验证用户场景的导航，另外还要验证场景的功能是正常的。
In the case of a Web application, you'll want to verify that the navigation of a user scenario and additionally verify that the functionality of the scenario pans out.
测试模块可以交互性地使用，以构筑更大或者更小的用户场景，这取决于测试的目的是什么。
The test modules can be used interchangeably to construct bigger or smaller user scenarios, depending on the test objectives.
真不错！我们已经使用TestNG - Abbot轻而易举地验证了三种不同的用户场景。
Not bad: I've easily tested three different user scenarios with TestNG-Abbot.
终端用户的满足因素——需求，正如用户场景中所陈述的那样，将有助于终端用户的工作。
End user satisfiers — Requirements, stated as user stories, which will help end users do their work.
利用硬件和软件更新带来平台、环境和性能改进，更加准确地反映用户场景，以及迁移到V7的帮助。
Platform, environment, and performance improvements that take advantage of hardware and software updates and more accurately reflect user scenarios, plus migration assistance to help you move to V7.
合伙人的满足因素P——需求，正如用户场景中所陈述的那样，将帮助合伙人在发布我们软件时获得成功。
Partner satisfiers — Requirements, stated as user stories, which will help partners succeed with this release of our software.
当该出报告时，需要一个适配器的活动，其将用户场景11匹配到他们的用例上，并基于这些用例进行报告。
When it comes time to report, there needs to be an adapter activity that will match the user stories 11 to their use cases and report based upon the use cases.
主要目标的满足因素——需求，正如用户场景中所陈述的那样，将满足购买或者发现我们软件人们的业务目标。
Principal goal satisfiers — Requirements, stated as user stories, which will meet the business goals of the people who buy or fund our software. 9.
注意涉众的目标要么像用户场景一样渺小，要么跟指令一样庞大，都可以在每次迭代开始的规划会议上进行适当的分解。
Note that stakeholder goals can be either as granular as user stories or as large as epics, and will be decomposed appropriately in the planning meeting that begins each iteration.
正如我们在下面的样本涉众目标文档中所看到的那样，目标满足因素并没有如建议的那样为用户场景清晰地进行了标注。
As can be seen in the sample stakeholder goals document below, goal satisfiers do not map as neatly to user stories as this suggests.
验证GUI中业务规则的过程变成了对用户场景进行验证；或者，换种说法，GUI测试包括验证可见状态的改变。
The process of validating business rules within GUIs becomes a process of validating user scenarios; or, to put it differently, GUI testing involves validating visual state changes.
应该围绕用户场景创建可视化的情节串连板，用户场景能够在业务建模被识别，并且他们是USBD方法的核心。
The visual storyboard should be created around the User scenarios that have been identified during the Business Modeling phase and that are the core of USBD.
用户场景还为客户提供自助服务，使用户可以管理他们的银行账户，查找支行和atm机，以及与银行雇员联系。
Consumer scenarios also provide customers with self-services where they can manage their banking accounts, find branch offices and ATMs, and initiate communications with banking staff.
优秀的设计具有足够的灵活性，以便能够处理，随着时间的流逝，将发生在硬件和软件技术，以及用户场景和需求上的自然的变化。
A good design is sufficiently flexible to be able to handle the natural drift that will occur over time in hardware and software technology, as well as in user scenarios and requirements.
应用推荐