uml模型(顺序图、用例、类图)。
在每一个包中，我们最初的类图都来自于我们的用例、业务对象模型、注释和访谈。
Within each package, our initial class diagrams were derived from our use cases, business object model, notes, and interviews.
当我们从用例图转入到序列图和类图时，马上就会注意到已知的参与者的影响。
As we move from use case diagrams into sequence and class diagrams, we will immediately notice the impact of known actors.
从用例到设计类的转化过程是缓慢的，需要进行多次的迭代。
The migration from use cases to design classes was slow, requiring a number of iterations.
在此例中，你将会在你的图表中为此前建模的每个工具类创建一个用例，以后它们就代表我们系统的主要功能。
In this example, you will create a use case in your diagram for each of the previously modeled utility classes, since they represent the main functionality of our system.
有什么方法比通过提供一个用例编码集来记录一个类效果更好呢？
What better way to document a class than to provide a coded set of use cases.
接下来的一步涉及到了从以上描述的各种模型(用例、类模型及显示信息流的交流图)中进行的计算。
The next steps involve computing from the different models described above - Use Case, Class model and Interaction diagram showing the flow of messages.
在分析阶段，我们的用例实现只包括分析类及分析对象，它们能组装成不同的UML图如类图和交互图。
In analysis, our use case realization contains only analysis classes and objects, which may populate various UML diagrams such as class diagrams and interaction diagrams.
用于类方法并返回函数的用例仅利用您的创造力进行限定。
The use cases for class methods that return functions is limited only by your creativity.
作为工作产品的输出，任务定义了一个用例实现和分析模型组成的一个分析类。
As output work products, the task defines a use-case realization as well as the analysis model comprising analysis classes.
从用例和分析类到设计和设计类的转化是不可避免的模糊的。
The transition from use cases and analysis classes to design and design classes was unavoidably blurry.
这个类将通过用例情节串连板(看下一点)中的主屏幕被典型地反映出来。
This class will typically be mirrored by a main screen in the use case storyboard (see next point).
另外，你可以从用例中产生序列图，协作图和类图。
In addition, you can produce sequence diagrams, collaboration diagrams, and class diagrams from use cases.
它也包括了可选择输入的一些其他工作产品，像用例实现，分析类，术语表等等。
It has several other work products as optional inputs, such as use-case realization, analysis class, glossary, and so on.
增强的大纲视图——序列图的“大纲视图”会显示出用例中的所有类和调用。
Enhanced Outline View - the sequence diagram's 'Outline View' shows all the classes and calls in the use case.
设想如果每个用例中有数十个类，哪一种模型更容易阅读呢？
Imagine if there were dozen of classes in each case — which one would be the most readable?
请注意，只需要把用例描述细化到你可以很好的找出系统中的分析类的程度就可以了。
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.
两个特殊的原型类被使用：业务角色和业务用例。
Two special stereotyped classes were used: business actors and business use cases.
他们也可以执行影响分析，从而找到所有会受到修改类或者数据库操作影响的用例。
They can also perform impact analysis to find out all the use cases that are impacted because of a change to a class or database table.
从用例和类表出发，我们从类里选择需要交互的对象，然后构造一张序列图表示这种交互。
Starting with our use case and list of classes, we choose objects from those classes to interact, and we construct a SQD to show that interaction.
在面向对象的编程用例中，这些模型清楚地展示了连接到用例地类和方法。
In the case of object-oriented programming, these models clearly lay out the classes and methods linked to a use case.
在两个用例下，它们都被分组在同一类别中，名字与原型相关属性集相同。
In either case they are grouped together under the category named the same as the stereotype contributing the properties.
这个用例控制类表示的是一个尚未进一步定义的类，它的职责是从用户那里接收事件和消息。
This Use Case Controller class represents a generic placeholder to receive events and messages from the human actor.
让我们用一个普通样例类(如清单3所示)来建模用户。
Let's take a sample trivial class for modeling users, as shown in Listing 3.
例子是用例、用例模型、业务规则、类、类图、序列图、数据模型和补充规约。
Examples are use cases, use case models, business rules, classes, class diagrams, sequence diagrams, the data model, and supplementary specifications.
它包括了描述用例模型中所确定的功能需求的逻辑实现的类和序列图。
It consists of class and sequence diagrams that describe the logical implementation of the functional requirements that you identified in the use case model.
根据RUP过程，这一步的目的是找出分析类的候选范围，这些类合作起来，可以完成用例的所有行为。
According to RUP, the purpose of this step is to identify a candidate set of analysis classes which will be capable of performing the behavior described in our use cases.
但是迄今为止，我们还没有任何对象和类，因此我们需要从用例中去发现这些对象和类。
But so far we don't have any classes or objects yet, so we have to discover the classes that we will need to carry out the process in our use cases.
那就是单元测试：一系列记录类所做工作的用例代码，提供输出控制。
That's what these unit tests are: a set of coded use cases that document what a class does, given a controlled set of inputs.
找出用例中的执行流程、事件的各个类。
To identify the classes that perform the various flows of events in a use case.
应用推荐