Also like the business process model, we build a class diagram to show the data that must be visible in each state to support the various choices.
还是和业务流程模型一样，我们构建一个类关系图来显示必须在每个状态中可见的数据以支持各种选择。
The next steps involve computing from the different models described above - Use Case, Class model and Interaction diagram showing the flow of messages.
接下来的一步涉及到了从以上描述的各种模型(用例、类模型及显示信息流的交流图)中进行的计算。
If you paste the harvested class into the same class diagram or into another class diagram that is outside of a blank model, the class attributes and functions are invisible.
如果您将总结的类粘贴到同一个类图，或本空白模型以外另一个类图中时，那么该类的属性和功能将丢失。
Now, let's look at another Class diagram (Figure 4) from the same model.
现在，让我们来看看来自同一个模型的另一个类图(图4)。
A UML diagram, such as a class diagram, is generally not precise enough to provide all relevant elements of a business model.
一个uml图，例如一个类图，通常不够精确来提供一个业务模型的所有相关元素。
This article will only focus on the class diagram and associated model elements (class, package, associations, attributes, and enumeration).
本文仅关注类图以及相关联的模型元素（类、包、关联、属性和枚举）。
As the Access class serves as the part of your system that interacts with the other pieces, you'll model that as an actor within your diagram.
因为访问类为你的系统提供与其它块交互的服务，所以在你的图表中，你要建模它为一个主角。
You started by turning existing code into a class diagram so that you had a picture of how your code looks as a model.
首先你把代码转化为类图，这样一来你的代码看起来就像是一个模型。
This is a UML class diagram where the input is an interface and class graph that represents the data model.
这是UM l类关系图，其中的输入为接口和表示数据模型的类图表。
Note that you cannot model a class's role on a plain class diagram, even though Figure 18 makes it appear that you can.
注意，你不能在纯粹类图中做类角色的建模，即使图18显示你可以这么做。
Figure 2 is a UML class diagram of the object model for the example.
图2是该示例对象模型的uml类图。
To generate a high-level class diagram, you need to create a blank model first.
为了得到一个高层的类图，您必须首先建立一个空白模型。
In the Model Explorer, use Visualize to add them to a new diagram or the current class diagram.
在模型搜索器中，使用Visualize来将它们添加到一个新图或当前的类图中。
Now that you have added this behaviour in the use case model, you should also revisit our class diagram and add the Netstat class in UML, as shown in Figure 11.
既然你已经把行为加到用例模型中了，你就应当再次访问类图并且把Netstat 类加到UML中去，如图11所示。
The Class model and the Interaction diagram trace back to the use case described here previously, as Figures 2 and 3 illustrate.
Class模型及Interaction图回溯至前面描述的用例，如图2和图3所示。
Figure 8 shows a class diagram with the abstractions used to model multiple versions of the Account EJB.
图8显示了一个类结构图，其中包含形成Accountejb不同版本的抽象。
Figure 4: Another Class diagram for the CheeseGrater model.
图4：cheesegrater模型的另一个类图。
Figure 3: Class diagram for the model "CheeseGrater".
图3：模型“CheeseGrater”的类图。
Once you have done that, leave the defaults as they are (template type Blank Model, with a diagram type of Class Diagram, since we will be viewing our imported classes in the UML class diagram).
一旦你进行了上面的操作，余下的就是默认的内容了(模板类型BlankModel，与一个图表类型Class Diagram，我们会一直能看见我们在UML图中输入的类 )。
To model inheritance on a class diagram, a solid line is drawn from the child class (the class inheriting the behavior) with a closed, unfilled arrowhead (or triangle) pointing to the super class.
为了在一个类图上建模继承，从子类(要继承行为的类)拉出一条闭合的，单键头(或三角形)的实线指向超类。
Object diagrams allow you to model the instances of your classes (as objects) in a class diagram in order to describe the behaviour of a system.
对象图允许我们为类图中的类实例（也就是对象）建模，用来描述系统活动。
Figure 7: Complete Class diagram for CheeseGrater model, showing new name for the cover element.
图7：cheesegrater模型的完全的类图，显示出cover元素的新名称。
In this paper, we give out a testing model, namely branch block diagram, to test services of class.
本文介绍了一种基于服务的类测试模型，即服务的块分支图。
A analytical model was established for automatic solid warehouse management system, included user diagram, class diagram and interaction diagram.
建立了自动化立体仓库管理系统的分析模型，并给出部分用例图、类图以及交互图。
The activity diagram, use case diagram, sequence diagram, collaboration diagram and the class diagram are used for building the analysis and design model of the sedimentary facies modeling system.
系统中采用了活动图、 用例图、顺序图、交互图和类图建立沉积相建模系统的分析和设计模型。
Getting the system requirement model by using use case model in UML, and making further system analysis by using class diagram and package diagram in UML.
以uml中的用例模型得出了系统的需求模型；以uml中的类图和包图对系统作进一步的分析。
Beehive Customer Management System used UML class diagram to build static model, used use case diagram to analyze requirement and used sequence diagram to build dynamic model.
蜂窝客户管理系统利用UM L类图建立了系统静态模型，并对蜂窝定义与划分模块使用用例图进行需求分析和用时序图来完成动态模型的建立。
Model is through the use case diagram, class diagram, sequence diagram, collaboration diagram, state diagram, activity diagram, component diagram and deployment diagrams to describe.
模型是通过用例图、类图、序列图、协作图、状态图、活动图，组件图和部署图来描述。
Model is through the use case diagram, class diagram, sequence diagram, collaboration diagram, state diagram, activity diagram, component diagram and deployment diagrams to describe.
模型是通过用例图、类图、序列图、协作图、状态图、活动图，组件图和部署图来描述。
应用推荐