图5：用来寻找分析类的问题。
把行为指定给分析类(找出操作)。
Distribute Behavior to Analysis Classes (discover operations).
分析类间事件与事件之间的相关性。
有三种基本的方法来充实我们的分析类
There are three basic approaches for "fleshing out" our analysis classes
把行为指定到具体的分析类。
在这里，我们要对每个分析类进行处理。
This step is done for each analysis class we have identified.
确定哪些分析类具有与其它类之间的关系。
Identify which of these analysis classes have some kind of relationship with each other.
图20：分析类到实现类的映射。
Figure 20: Map of the analysis classes to the implementation classes.
在分析类图上，建立分析类间的联系。
Establish Associations between analysis Classes (analysis class diagram).
用例分析第五步：建立分析类之间的关系。
Use-Case analysis step 5: Establish associations between analysis classes.
用例分析第三步：为用例行为找出分析类。
Use-case analysis step 3: Find analysis classes from use-case behavior.
从类的职责列表中，我们可以确定分析类的一些属性。
From our list of class responsibilities we can deduce certain attributes for our analysis classes.
这就引出了一个有趣而又重要的问题：什么是分析类？
But this raises a very interesting and important question: Just what is an analysis class?
逆向工程在分析类之间的关系上是相当有效的。
The reverse engineering was fairly effective at parsing out relationships between classes.
系统需要的设计类(也就是分析类加技术类)。
The design classes (i.e., analysis classes plus technology classes) needed in our system.
从用例和分析类到设计和设计类的转化是不可避免的模糊的。
The transition from use cases and analysis classes to design and design classes was unavoidably blurry.
首先，一个业务级别的分析类是业务领域中的一个要素，与实现技术无关。
First, a business-level analysis class is one that is essential to the business domain, without reference to implementation or technology constraints.
啊哈！在总共得30多个候选中，现在我们只需要面对选出的8个分析类。
Wow! That's only eight analysis classes versus the thirty nine candidates we started with.
如果你觉得补充一些细节对于找出系统中的分析类有所帮助，那么就加上它。
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.
从这个列表中，我们列出了通过了问题检查的词，也就是下面列出的分析类。
From this list we extract those candidates that we have designated "yes." this yields the following list of analysis classes.
RUP过程中的实体类大致上相当于前面提到的，业务级别的分析类。
RUP's entity classes are roughly equivalent to the business-level analysis classes above.
它也包括了可选择输入的一些其他工作产品，像用例实现，分析类，术语表等等。
It has several other work products as optional inputs, such as use-case realization, analysis class, glossary, and so on.
喜欢看动作片的人可能更注重事实，这是从事分析类工作的重要特质。
Someone opting for an action flick may be more fact-focused, an important trait for analytical jobs.
请注意，只需要把用例描述细化到你可以很好的找出系统中的分析类的程度就可以了。
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.
作为工作产品的输出，任务定义了一个用例实现和分析模型组成的一个分析类。
As output work products, the task defines a use-case realization as well as the analysis model comprising analysis classes.
分析类的数据流，说明数据的定义-使用对；给出构造类的控制流图的一种算法。
The data flow testing of class is analysed, and the data definition-use pair is explanated.
因为我们还没有任何类，所以我们的主要目标就是找出在汽车租借系统中的所有分析类。
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.
在我们解决持续性的第一个方法中，我们把DBMS的信息放在表示业务抽象(即分析类)的对象里。
In our first approach to addressing persistence, we put DBMS knowledge in the object representing our business abstractions (i.e., analysis classes).
在FindBugs分析类时，它会在分析方法内容时调用visit (Code)方法。
As FindBugs analyzes a class, it will call the visit (Code) method when the contents of a method are walked.
应用推荐