这就是迭代的用例驱动方法。
所有测试脚本均由应用程序的业务用例驱动。
All of the test scripts are driven by business use cases for the application.
用例驱动测试过程，但是它们不直接处理各种类型的测试用例。
Use cases drive the testing process, but they cannot directly address many types of tests cases.
作为过程框架，RUP是迭代的、以架构为中心的，并且是用例驱动的。
As a process framework, RUP is iterative, architecture-centric, and use-case driven. This is incorporated into the six RUP principles.
此外，用例驱动了更清楚的沟通，加强了这些用户需求开发的理解。
Further, use cases drive clearer communication and enhance development's understanding of the users' needs.
单个的测试用例是由用例驱动的，而不是附加的，非功能性需求规格。
The individual test cases are driven by use cases, and not supplemental, non-functional requirements specifications.
一般来说，从一个用例驱动方法来创建测试用例包括以下四个基本步骤。
Generally, test case creation from a use case-driven method involves four basic steps.
用例驱动技术从行为者的角度建立用例，旨在减少软件开发的复杂度。
Research and Application of Use-Case Driven Analysis Method on Software Requirements Elicitation;
请参考RationalSOMA本身关于用例驱动的业务建模实践方法的信息。
Please refer to Rational SOMA itself for information regarding the Use Case Driven Business Modeling practice.
整个开发过程体现了RUP的用例驱动、构架为中心和增量与迭代的特点。
The whole development process incarnates the characteristics of RUP, such as case-driven, focus on architecture and increment-iteration.
此外，如果您已经选择使用用例驱动的方法，那么您显然需要支持用例开发的工具。
Also, if you've chosen to take a use case-driven approach, then you obviously need tools that support development of use cases.
本文归纳了RUP的主要核心思想为：用例驱动，以构架为中心的迭代和增量开发。
Key ideas of RUP are use case driving, iteration of architecture-centric and incremental development.
作者应用最佳实践--用例驱动开发，关注架构、持续测试和迭代开发--来抵销一些项目风险。
To their credit, the authors applied best practices -- use-case driven development, focusing on architecture, frequent testing, and iterative development -- to offset many of these project risks.
此外，用例驱动用户体验建模，为确保用户界面在整个解决方案过程中的一致性设置了相应的阶段。
Additionally, use cases drive user-experience modeling, which sets the stage for ensuring the user interface is consistent throughout the solution.
该方法由用例驱动整个研发过程，可以在进行系统分析的同时规划数据库，产生对应的数据库表。
The method drives whole process of design and development by the use-case, it can plan database and produce corresponding database table while analyzing the system.
用例驱动方法是当前国际流行的软件开发过程之一，软件开发所有阶段的活动都是以用例为核心。
This paper presents a use-case driven extension approach-UCD/Theme approach, which uses aspect-oriented technique to facilitate separation of concerns on requirement analysis phase.
其次，分析了用例驱动过程与软件基本架构的关系，并说明了从概念模型到可执行体之间的对应关系。
Secondly, we present the relations between use case driven process and software basic sketch, and also describe the corresponding relations between semantic models and executive entities.
有了用例驱动开发，每个测试水平使用工件的不同分组，从而有助于使测试保持在这个阶段适当的范围内。
With use case-driven development, each test level USES a different grouping of artifacts, which AIDS in keeping the test within the appropriate boundaries for the phase.
如果你确实执行了用例驱动式开发，那么使用场景就是一个典型的完整用例情景的实例，或者用例情景的一部分。
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.
有RUP做根基，它能提供迭代式、递增的、用例驱动、风险驱动和以架构为中心的过程，同时也支持敏捷项目的工作习惯。
Given its RUP roots, it provides a process that is iterative and incremental, use-case driven, risk-driven, and architecture-centric, which at the same time supports the work habits of agile projects.
MDM应用程序集成模式：这个类别中的所有模式都以 EAI 为中心，主要关注由 MDM用例驱动的过程。
MDM application integration patterns: All patterns in this category are EAI centric patterns focusing on processes motivated by MDM use cases.
通常，编写完业务需求后，团队成员会进行深入的探讨，建立起具体的用例，由这些用例驱动测试用例、单元测试和最终代码的实现。
Typically the Business requirement is written and the team will drill down to flesh out the use cases that will drive the tests cases, the unit tests and ultimately the implementation code.
就像Per Kroll和PhilippeKruchten提到的，1RUP定义了一种迭代、以架构为中心，及用例驱动的软件开发方法。
As noted by Per Kroll and Philippe Kruchten, 1 RUP defines a way of developing software that is iterative, architecture-centered, and driven by use cases.
用例技术是一种越来越流行的捕获需求和驱动系统开发的方法。
The use-case technique is an increasingly popular approach to capturing requirements and driving system development.
由于用例可以通过黑盒访问这个系统，所以它们成为单元测试人员的关键性驱动。
Since use cases take a black box approach to the system, they cannot be critical drivers for the unit testers.
用例的静态测试可以由检查表驱动，安全的各种水平也应该包含测试人员。
Static testing of the use case can be driven by a checklist, and levels of scrutiny should involve testers.
分析设计建模输出与驱动它的用例直接相连接。
Analysis and design modeling outputs are linked directly to the use cases driving it.
用例的标识是由与soa相一致的流程模型驱动。
The identification of the use cases is driven by process models that are in alignment to an SOA.
“领域驱动开发”的作者EricEvans有一次被问到，场景和用例之间有什么分别。
Eric Evans, author of "Domain Driven Design", once asked what the difference was between a scenario and a use case.
1992年Gustov Karner介绍过，这个评估是由用例的元素驱动的。
Introduced by Gustov Karner in 1992, the estimation is driven by the elements of a use case.
应用推荐