Original use case specification after merge.
合并之后的原始用例规约。
Figure 1: Example of a business use case specification.
图1：一个业务用例规格的例子。
Figure 2: An initial high-level use case specification.
图2：初始的高层用例说明。
Here is the first draft of the use case specification.
这里是用例配置的第一个草稿。
Since a use case specification has at least a basic flow, it also has at least one transaction.
因为一个用例配置至少有一个基本流程，它也至少应该有一个事务。
Select the appropriate document type (use case specification in this case), and click OK (see Figure 8. Branching - Import document 3).
选择合适的文件类型(在本例中，是用例规约)并点击OK(参见图8，“分支—导入文件3”)。
To illustrate, we usually find that transforming a use case specification document into an analysis model is generally not practical.
我们常常发现，将用例规范文档转换成分析模型通常是不实际的。
The use case specification itself is abstract or generic, in the sense that you don't expect different flows for different search terms.
用例配置本身是抽象的或者通用的，在这个意义上您不要对不同的搜索项期待不同的流程。
The whole process focus on software requirement capture, use case analysis and model building, and provides a use case specification of software requirement.
整个过程侧重于需求的获取、用例分析和建模的实现，并提供了一个简单的用于描述软件需求的用例规约。
This gives us an indication of the minimum amount of use case transactions in any use case specification: there are at least as many transactions as there are flows. 8.
它给了您一个任何用例配置中用例事务最小数量的指示：流程中至少应该有以下数量的事务。
Conveniently, use case specifications share many characteristics with service specifications; the use case specifications can be seen as an early version of the service specification. Both have.
非常方便的是，用例规范和服务规范有很多相同的特征，可以将用例规范视为服务规范的早期版本。
In this case, we use an abstract class to define the service specification, as shown in Figure 5.
在这种情况下，我们使用一个抽象类来定义服务规范，如图5所示。
It is defined by the XML signature specification that the receiving application should be able to identify which object to use in this case.
XML签名规范将其定义为接收方应用程序应当能够识别在这种情况下应当使用的对象。
Realization is a formal term in use case modeling that indicates the relationship between a specification of something and its various implementations.
所谓的实现是用例建模中的一个规范化术语，它指示了规格与各种执行之间的关系。
Instead of a subjective evaluation of the defect, the tester can rely directly on the declared value the sponsor placed on that specific use case at the time of requirements specification.
测试人员可以直接依赖发起者在制定需求规范时赋予这个具体用例的值，而不是对缺陷进行主观地评估。
Transforming an LDM specification to a UML model is an equally valid and supported use case.
将一个LDM规范转换为一个uml模型也是一个同等有效和受支持的用例。
That doesn't mean that every use-case specification needs a full set of appendices; include only those that will promote understanding.
这不意味着每个用例规格说明都需要一个完全的附加描述集；只包括那些会促进理解的附加描述。
Will I need different use-case specification templates to create different artifacts?
我需要不同的用例规格说明模版来创建不同的工件吗？
Notice that this service specification also implements the Invoicing use case.
请注意该服务规范也执行了Invoicing用例。
The WS-Polling specification addresses an interesting use case that is worth mentioning — the mailbox scenario.
WS - Polling规范涉及到一个值得一提的有趣用例——邮箱方案。
This use case model is stored as a reusable asset specification (RAS) asset on the dW RAS repository and can be accessed from the recipe.
此用例模型作为可重用资产规范(ReusableAsset Specification,RAS)资产存储在dW RAS存储库中，可以从该菜谱进行访问。
Switch to the SSL TAB view, and specify a cipher specification (in this case, use RC4_MD5_US).
切换到SSL选项卡视图，然后指定一个密码规范(在这个例子中使用RC4_MD5_US)。
A Rational RequisitePro requirement management file, for the non-functional requirements for the inventory use case, is available as a Reusable asset Specification (RAS) asset.
对于库存系统用例的非功能需求，RationalRequisitePro需求管理文件是以可重用资产规范(ReusableAsset Specification, RAS)资产的形式提供的。
The UML specification provides specific text values for diagram types (e.g., sd = Sequence Diagram, activity = Activity Diagram, and use case = Use Case Diagram).
UML规范给图类型提供特定的文本值。 （举例来说，sd代表序列图，activity代表活动图，use case代表用例图）。
In other words, if the directions in the SAD together with the actual Use-Case Specification are sufficient for the developer to build the code of the use case, the Use-Case Realization is empty.
换句话说，如果SAD中的指示，连同实际的用例规格说明对开发人员来说足够构建用例的代码，那么用例实现就是空的。
We now feel that the use-case specification document is an important step that we shouldn't have skipped.
我们现在觉得用例规格文档是我们不应该跳过的重要步骤。
A use case is neither a class specification nor a data specification.
用例既不是类规范，也不是数据规范。
RUP recommends three categories: a vision document, use-case documents, and a supplementary specification document describing requirements that do not warrant use cases.
RUP推荐分为三类文档：一个前景文档，多个用例文档和一个补充规约文档，最后一种描述了不能根据用例描述的需求。
For example the business modeling set includes a business use-case model, business rules, a business architecture document, and a business supplementary specification.
比如，业务建模集包含业务用况模型、业务规则、业务架构文档以及业务辅助说明书。
For example the business modeling set includes a business use-case model, business rules, a business architecture document, and a business supplementary specification.
比如，业务建模集包含业务用况模型、业务规则、业务架构文档以及业务辅助说明书。
应用推荐