Distribute Behavior to Analysis classes.
把行为指定到具体的分析类。
Figure 5: Questions for discovering analysis classes.
图5：用来寻找分析类的问题。
Describe Event Dependencies between Analysis classes.
分析类间事件与事件之间的相关性。
Distribute Behavior to Analysis Classes (discover operations).
把行为指定给分析类(找出操作)。
Figure 20: Map of the analysis classes to the implementation classes.
图20：分析类到实现类的映射。
Use-case analysis step 3: Find analysis classes from use-case behavior.
用例分析第三步：为用例行为找出分析类。
There are three basic approaches for "fleshing out" our analysis classes
有三种基本的方法来充实我们的分析类
Establish Associations between analysis Classes (analysis class diagram).
在分析类图上，建立分析类间的联系。
Use-Case analysis step 5: Establish associations between analysis classes.
用例分析第五步：建立分析类之间的关系。
Identify which of these analysis classes have some kind of relationship with each other.
确定哪些分析类具有与其它类之间的关系。
RUP's entity classes are roughly equivalent to the business-level analysis classes above.
RUP过程中的实体类大致上相当于前面提到的，业务级别的分析类。
The design classes (i.e., analysis classes plus technology classes) needed in our system.
系统需要的设计类(也就是分析类加技术类)。
Wow! That's only eight analysis classes versus the thirty nine candidates we started with.
啊哈！在总共得30多个候选中，现在我们只需要面对选出的8个分析类。
From our list of class responsibilities we can deduce certain attributes for our analysis classes.
从类的职责列表中，我们可以确定分析类的一些属性。
The transition from use cases and analysis classes to design and design classes was unavoidably blurry.
从用例和分析类到设计和设计类的转化是不可避免的模糊的。
As output work products, the task defines a use-case realization as well as the analysis model comprising analysis classes.
作为工作产品的输出，任务定义了一个用例实现和分析模型组成的一个分析类。
From this list we extract those candidates that we have designated "yes." this yields the following list of analysis classes.
从这个列表中，我们列出了通过了问题检查的词，也就是下面列出的分析类。
So far we don't have any classes, so our main goal will be to identify the analysis classes we need in our Auto Rental system.
因为我们还没有任何类，所以我们的主要目标就是找出在汽车租借系统中的所有分析类。
If your first cut at a use case description is a bit thin in helping you identify some analysis classes, then do the supplemented use-case.
如果你觉得补充一些细节对于找出系统中的分析类有所帮助，那么就加上它。
This was strictly constrained to be an analysis-level diagram containing only analysis classes, and no design or implementation classes.
它被严格约束于分析级别，只包含分析类，不包含设计类或实现类。
In our first approach to addressing persistence, we put DBMS knowledge in the object representing our business abstractions (i.e., analysis classes).
在我们解决持续性的第一个方法中，我们把DBMS的信息放在表示业务抽象(即分析类)的对象里。
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.
请注意，只需要把用例描述细化到你可以很好的找出系统中的分析类的程度就可以了。
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.
在分析阶段，我们的用例实现只包括分析类及分析对象，它们能组装成不同的UML图如类图和交互图。
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.
根据RUP过程，这一步的目的是找出分析类的候选范围，这些类合作起来，可以完成用例的所有行为。
So, in this article I am going to concentrate on the business-level, technology-agnostic analysis classes, and leave alone almost all technology issues until we discuss design.
因此，在这一步，我将会侧重于业务方面的，与技术无关的分析类。在讨论设计的时候再讨论涉及技术的部分。
The class diagram shown in Figure 8 shows our vehicle rental analysis classes, the relationships between them, and an initial start on the attributes appropriate to be owned in each class.
图8中的类图上展示了汽车租借的分析类、它们之间的关系以及每个类所拥有的一些基本的属性。
With the analysis classes and their relationships identified, I then populated each analysis class with attributes (data members) that were in accord with the responsibilities of each class.
借助这些分析类及其已确定的关系，我又给每个分析类配上与其职责相一致的属性(数据成员)。
And once we identify our class responsibilities, we should construct an analysis class diagram to capture the structure of the relationships among our classes.
一旦我们确定了我们的类的职责，我们就可以设计一个分析类图，来描述类间关系的整体结构。
Both have helped me understand patterns, and I use examples and excerpts from them in my object-oriented analysis and design classes.
这两本书都曾帮助我理解模式，并且在我面向对象的分析与设计课程上，我使用了从中摘录的例子。
Data flow analysis can examine problems that span multiple classes.
数据流分析可以检查跨越多个类的问题。
应用推荐