Also, if you've chosen to take a use case-driven approach, then you obviously need tools that support development of use cases.
此外，如果您已经选择使用用例驱动的方法，那么您显然需要支持用例开发的工具。
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.
有了用例驱动开发，每个测试水平使用工件的不同分组，从而有助于使测试保持在这个阶段适当的范围内。
But generally, this type of information, and thus the related test cases, should be generated later in the development process than is done with those tests driven by a use case.
但是一般说来，这种类型的信息，以及这样有关联的测试用例，开发过程中信息的生成应该晚于由那些测试用例驱动的生成的。
You can certainly gain incremental improvements by adopting use case driven development or by using visual models.
你可以采用用例驱动的开发或者采用可视化模型得到一些改善。
Static testing of the use case can be driven by a checklist, and levels of scrutiny should involve testers.
用例的静态测试可以由检查表驱动，安全的各种水平也应该包含测试人员。
As a process framework, RUP is iterative, architecture-centric, and use-case driven. This is incorporated into the six RUP principles.
作为过程框架，RUP是迭代的、以架构为中心的，并且是用例驱动的。
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.
如果你确实执行了用例驱动式开发，那么使用场景就是一个典型的完整用例情景的实例，或者用例情景的一部分。
In a typical use case, the flow of activity is driven by the interaction of a particular actor with the system toward the execution of a specific goal (for example, "managing a water-health sample").
在典型的用例中，活动流是由特定参与者与系统间以执行特定目标为目的而开展的交互驱动的(例如，“管理水健康状况样本”)。
In implementing the code for this tutorial, you see more extensive use of the model-driven approach than was the case in the earlier tutorials.
与前面的教程相比，在实现本教程的代码时，您将看到我们更多地使用了模型驱动的方法。
Now that it's time to begin iterating on the design, the book describes two different options — Use case or Feature-driven development — and discusses when one approach is better than the other.
因为是时候开始对设计进行迭代了，所以该书介绍了两种不同的选项——用例或特性驱动的开发——并讨论什么时候一个会比另一个更好。
The more black box, work-stream driven the test organization is, the more effectively primary use case documents can be applied to sizing.
如果测试组织被越多黑盒、工作流所驱动，主要的用例文档就越能有效地在估计中运用。
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.
作者应用最佳实践--用例驱动开发，关注架构、持续测试和迭代开发--来抵销一些项目风险。
Whether it is necessary to code responsibilities in other layers will be driven mainly by the system's architectural style and design decisions made during the use-case realization session.
是否有必要在其他层中对职责编码主要取决于在用例实现会议中做出的系统架构风格和设计的决策。
But does a value (significantly) less than 1 mean the developers didn't do a good job of adopting use-case-driven development?
但是一个值(特定的)小于1，就意味着这个开发人员没有很好地完成采取用例驱动开发的工作吗？
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.
有RUP做根基，它能提供迭代式、递增的、用例驱动、风险驱动和以架构为中心的过程，同时也支持敏捷项目的工作习惯。
Rhapsody is a round-trip model driven solution and supports capturing the project requirements using requirements diagrams, use-case diagrams, sequence diagrams, activity diagrams and state charts.
Rhapsody是个双向的模型驱动解决方案，可以通过需求图、用例图、序列图、活动图以及状态图捕获项目需求。
Eric Evans, author of "Domain Driven Design", once asked what the difference was between a scenario and a use case.
“领域驱动开发”的作者EricEvans有一次被问到，场景和用例之间有什么分别。
Please refer to Rational SOMA itself for information regarding the Use Case Driven Business Modeling practice.
请参考RationalSOMA本身关于用例驱动的业务建模实践方法的信息。
Introduced by Gustov Karner in 1992, the estimation is driven by the elements of a use case.
1992年Gustov Karner介绍过，这个评估是由用例的元素驱动的。
This paper discusses the Rational Unified Process driven by use case, and gives a solution for capturing the requirement of library management information system.
论述了用况驱动的统一软件过程，并给出了使用用况来捕捉图书管理系统需求的实例。
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.
其次，分析了用例驱动过程与软件基本架构的关系，并说明了从概念模型到可执行体之间的对应关系。
RUP development process is the mainstream of modern software development with characteristics of iteration and use case driven. UCP based on the use case is a software size estimation technique.
RUP的开发具有迭代、以用例为驱动的特点，是现代软件开发的主流，UCP是基于用例的软件规模估算技术。
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.
用例驱动方法是当前国际流行的软件开发过程之一，软件开发所有阶段的活动都是以用例为核心。
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.
用例驱动方法是当前国际流行的软件开发过程之一，软件开发所有阶段的活动都是以用例为核心。
应用推荐