这里是投票步骤的注释图。
图5中的例子展示注释如何出现在文档分析器中。
Figure 5 shows an example of how annotations appear in the document analyzer.
在每一个包中，我们最初的类图都来自于我们的用例、业务对象模型、注释和访谈。
Within each package, our initial class diagrams were derived from our use cases, business object model, notes, and interviews.
我们也让一个工程团队的成员花费一些时间来记录任何支持图的注释。
We also had a member of our engineering team take minutes, recording any notes that supported the diagrams.
在图2中，转移是通过带有事件注释的弧线、可选的条件以及将要执行的动作来反映的。
In Figure 2, a transition is reflected by an arc with annotations for the event, an optional condition, and the action to be performed.
图2显示了用于查看草案模型和添加注释的小部件。
Figure 2 shows the widget for viewing a draft model and adding comments.
其中包含如何通过使用查询格式化、注释、报告和访问计划图来更好地理解问题查询。
It includes how to understand the problem query better by using the visual AIDS provided by query formatting, annotation, reports, and the access plan graph.
确认并命名一个用例实现保证了交互图和文本注释回到用例的可追踪性。
Identifying and naming a use case realization provides traceability from the interactions diagrams and textual commentary back to the use case.
图2中的用例相当简略，只是有名称和一些典型的注释来描述主要思想。
The use case in Figure 2 is rather slim, indicating its name and some point-form notes describing the main idea.
图19显示了包含椭圆与注释的连接器功能。
Figure 19 shows the connector functionality with an oval and a note.
图7显示了一个类中几个操作的注释过程。
Figure 7 shows the annotation process of a couple of operations in a class.
图3所示的注释有两个链接。
细节请参考完整的源代码(其中有很多注释)，并参照图1。
For details, please consult the complete source code, which is heavily commented, and compare it to Figure 1.
为关系图或关系图组，注释尽可能少。
Be a diagram or set of diagrams with as few notes as possible.
在图6中，Comments工具条中只有那些拥有注释的元素会强调显示出来。
In Figure 6, only those elements that have comments that show in the comments sidebar are highlighted.
可能您会注意到，转换会在生成的代码中，对元素应用@generated注释（图8）。
As you may notice, the transformation appends the @generated annotation to elements in the generated code (Figure 8).
本部分说明QueryTuner查询注释和访问路径图如何帮助您分析访问路径和SQL性能。
This section illustrates how the query Tuner query annotation and access path graph can help you analyze access paths and SQL performance.
到目前为止，您已经看到如何在OptimQueryTuner各项功能的帮助下分析和调优问题查询，这些功能包括查询注释、访问计划图等等。
So far, you've seen how you can analyze and tune a problem query with the assistance of Optim query Tuner capabilities, such as query annotation, access plan graph, and so on.
图6：由分配的有色的附着注释所指示的项目系统组件。
Figure 6: Project system components denoted by assigned colored sticky note.
屏幕图：Createdatabase向导，其中包含数据库名、默认路径、别名和注释字段。
Screen cap: Create database wizard, with fields for database name, default path, alias, and comment.
图5展示了BusinessIntegrationModeler中的策略注释的实例。
Figure 5 shows an example of a policy annotation in Business Integration Modeler.
图7显示了为afghanistan找到的第一个注释。
Figure 7 shows the first annotations that were found for Afghanistan.
图4显示了使用Annotation工具栏注释记录的一个范例。
Figure 4 shows an example of a recording that was annotated with comments using the Annotation toolbar.
图5：带有-type=block 的 pc_注释（注释源报告）
Figure 5: pc_annotate (annotated source report) with -type=block
图8：pc _ covdiff(注释差异报告)。
为图表添加可读的文本注释，这将比标准的饼图交付更多的信息。
Annotate the charts with readable text that delivers more information than the standard pie chart.
虽然有点笨拙，但这是一种非常简单的方法，能够使每条文本注释显示在与其相应饼图分区适当靠近的位置。
Although a bit clumsy, it's s simple way to have each of the text annotations appear in a reasonably close proximity to their appropriate pie slices.
现在可以向关系图添加可视说明以用于注释目的。
您现在可以在WS - bpel流程、业务状态机、中介流的编辑器以及SCA组装关系图编辑器中添加可视说明和注释。
You can now add visual notes and comments in the editors for WS-BPEL processes, business state machines, mediation flows, and the SCA assembly diagram editor.
图1说明了用户定义的带注释的方法接口、代码生成器和生成的实现类之间的关系。
Figure 1 illustrates the relationship between the user-defined data access interface, the code generator, and the generated implementation class.
应用推荐