图5：用来寻找分析类的问题。
把行为指定给分析类(找出操作)。
Distribute Behavior to Analysis Classes (discover operations).
图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.
逆向工程在分析类之间的关系上是相当有效的。
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.
如果你觉得补充一些细节对于找出系统中的分析类有所帮助，那么就加上它。
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.
因为我们还没有任何类，所以我们的主要目标就是找出在汽车租借系统中的所有分析类。
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.
一旦我们确定了我们的类的职责，我们就可以设计一个分析类图，来描述类间关系的整体结构。
And once we identify our class responsibilities, we should construct an analysis class diagram to capture the structure of the relationships among our classes.
借助这些分析类及其已确定的关系，我又给每个分析类配上与其职责相一致的属性(数据成员)。
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.
图8中的类图上展示了汽车租借的分析类、它们之间的关系以及每个类所拥有的一些基本的属性。
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.
类库在编译程序的面向对象构造过程中起重要作用，词法分析类库是编译类库的重要组成部分。
Class library plays the vital role in the construction of compiler by object-oriented method and lexical analysis class library is an important part of object-oriented compiling class library.
因此，在这一步，我将会侧重于业务方面的，与技术无关的分析类。在讨论设计的时候再讨论涉及技术的部分。
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.
在分析阶段，我们的用例实现只包括分析类及分析对象，它们能组装成不同的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.
根据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.
不是通过分析类文件的形式或结构来确定程序的意图，而是通常使用Visitor模式(请参阅参考资料)。
Instead the form or structure of the class files are analyzed to determine the program's intent, often using the Visitor pattern (see Resources).
如果没有列出应用程序的依赖关系，那么FindBugs仍然会尽可能地分析类，但是在找不到一个缺少的类时，它会抱怨。
If you don't list your application's dependencies, FindBugs will still analyze your classes as well as it can, but it will complain when it is unable to find one of the missing classes.
可以通过特定脚本文件的名称或特定分析程序模块的类名称来调用这些分析程序。
These analyzers can be invoked with the name of specific script files or the class name of specific analyzer modules.
应用推荐