补充用例描述(如果需要的话)。
用户工作负荷模拟用例描述。
用例分析第二步：补充用例描述。
Use-case Analysis step 2: Supplement the use-case descriptions.
用例描述：用文字描述系统提供的主要功能。
Use case descriptions: Textual descriptions of the major services provided by the system under discussion.
对于使用者流程，人员活动用例描述用户和系统间的交互。
As with consumer processes, human activity use cases describe interactions between a user and the system.
此用例描述数据如何在使用点到点事务模型的系统间流动。
This use case describes how data flows between two systems that use a point-to-point transaction model.
业务用例描述商业流；它们决定谁是信息的来源，以及谁是目标。
Business use cases describe business flows; they determine who is the source of the information and who is the target.
用例描述的是对参与者来说有价值的一系列行动，而不是特性集。
A use case describes a series of actions that provide value to an actor; it doesn't describe a collection of features.
认识它的另一种途径是：用例描述实际参与者与系统交互的方式。
Another way to look at it is that a use case describes a way in which a real-world actor interacts with the system.
第二个SOA用例描述了由使用者调用整合过程的情况。
The second SOA use case illustrates a situation in which a consumer invokes the consolidation process.
UML规定了建立用例图表的标准，但并不是为了编写用例描述的。
UML dictates standards for diagramming use cases but not for writing use case descriptions.
图七：用例描述(未来情景)：“顾客登记”使用两栏格式。
Figure 7: Use-case description (to-be scenario) : "Check in Guest" using a two-column style.
这次讨论中，我更关心的是阐明用户接口、系统接口和用例描述之间的关系。
I'm most concerned in this discussion with clarifying the relationship between user interfaces, system interfaces, and use case descriptions.
用例描述用例流程的细节信息，包括简单介绍，步骤，选择的流程。
Use case description Details of the use case flow, including brief description, steps, alternate flows.
结果产生了许多编写用例描述的方法，这些方法有时是互相竞争的。
As a result, there are numerous, sometimes competing, methods for writing use case descriptions.
本质用例描述了用户与系统间抽象、轻量级和技术无关的对话过程。
Essential use cases are abstract, lightweight, technology-free dialogues between user and system.
它通过为你的用例描述提供具有精确含义的通用词汇术语，来连接你的各个用例。
It interconnects your use cases by providing a common vocabulary of terms with precise meanings for your use case descriptions.
相反，他把这一案例描述成“健康和安全措施的完全失效”的一个例子。
Instead he describes the case as an example of a "total failure in health and safety procedures".
找出预约汽车的用例描述中的这些名词(跳过代名词，如“他”)，如下。
Let's identify and underline the nouns (skipping pronouns such as "he") in our supplemented use case for Reserve a Vehicle, as follows.
请注意，只需要把用例描述细化到你可以很好的找出系统中的分析类的程度就可以了。
Bear in mind that you want to supplement the use-case descriptions only to the point that you can effectively determine the analysis classes in your system.
适当描述你的业务用例(原则5：用例描述：阐明“是什么”，而不是“如何做”)？
Describe your business use cases appropriately (Principle 5: use case descriptions: State what and not how)?
用例可以由用例描述来支持，包括关键属性，比如先决条件，和一系列的事件。
The use case may be supported by a use case description containing key properties, such as pre-conditions, post-conditions, and a flow of events.
与传统SRS支持的解决方案空间方法相比，用例描述了用户与系统交互时执行的动作序列。
In contrast to the solution space approach espoused by the traditional SRS, use cases describe the sequences of actions that users perform as they interact with a system.
一个关联reference主题的DITA主题图向相关的用例描述了这些页面。
A DITA topic map relating reference topics describes these pages to the related use cases.
通常，用例描述足够描述一个简单用例中的工作流（“执行A，然后执行B，然后执行C”）。
Often the use-case description is sufficient to describe the flow of work through a simple use case ("do A, then do B, then do C").
您可以通过检查并计算用例描述中涉及到的用例事务来检查并计算用例事务，来进行测试。
You can test for "sameness of size" by detecting and counting the use case transactions that are involved in your use case specifications.
为了能够依靠用例来测试，除了用例描述和用例图之外，还需要有关特定方面的额外信息。
In order to be able to test by means of use cases, besides the use case description and a use case diagram, additional information regarding specific aspects is required.
通常在我工作的同时，我会将问题陈述、所有相关用例描述、UML图和代码都放在我面前。
I typically have the problem statement, any relevant use-case descriptions, the UML diagrams, and the code all in front of me at the same time as I work.
为了真正理解为什么我们在用例描述中不包括UI逻辑，我想无论如何我们不得不采用亲身实践的方法。
To truly understand why we don't include UI logic in use case descriptions, however, I think we'll have to take the hands-on approach.
为了真正理解为什么我们在用例描述中不包括UI逻辑，我想无论如何我们不得不采用亲身实践的方法。
To truly understand why we don't include UI logic in use case descriptions, however, I think we'll have to take the hands-on approach.
应用推荐