Here we focus on use case points.
这里我们处理用例点。
Figure 1: Main concepts of the use case points method.
图1：用例点方法的主要概念。
At the moment, we prefer to use the use case points method.
现在，我们更加倾向于使用用例点方法。
According to the use case points method, the criteria to assign a weight to a use case are.
根据用户点方法，对用例分配权重的标准是。
After the size in use case points is determined, effort and schedule algorithms can then be applied.
在决定用例点的规模以后，就可以投入精力与日程安排的规则了。
The Use Case Points Method (UCPM) appears to offer the highest potential for effective test sizing.
这个用例点方法(UCPM)似乎为有效测试估计提供了最高的潜能。
The use case points method is a well-documented approach for estimating software development activities.
用例点方法是一种估算软件开发活动的广泛记载的方法。
This article assumes that a project team that wants to estimate with use case points writes their use cases at goal levels.
本文假设有一个项目团队想要使用用例点来估计，这些用例点书写了目标层次上的用例。
We start with a sketch of the use case points method, followed by a discussion on what definition of a use case transaction works best.
从用例点方法的概述开始，接着是在什么分辨率下用例事务工作状态最好。
The number and weight of the use cases identified is the most important component in the calculation of the so-called unadjusted use case points.
识别的用例的数量是所谓未调整用例点计算的最重要部分。
In order to apply the use case points method to the estimation of software effort estimation, it is important to have a good idea of its basic constituents.
为了对软件性能估算应用用力点方法，对它的基本组成有良好的了解是十分重要的。
The use case points method, which we 'l sketch below, is a promising estimation method that fits in nicely with the use case approach to describing requirements.
我们将会在下面介绍到的用例点方法，是一种十分有前途的估算成本方法，能够很好的配合用例方法以描述需求。
Finally, add the supplementary effort (SE) not accounted for in the use case points model (such as project management hours, integration testing) and the effort estimation is complete.
最后，现在用例点模型中添加未计算的补充的效果（SE）（例如项目管理时间，集成测试等），然后估算就完成了。
The size of a system is calculated from the unadjusted use case points by adjusting them with the technical complexity factor, obtained from a consideration of the system's technical properties.
系统的规模是通过根据技术复杂性因素进行调整，获取系统技术属性估算，来从未调整的用例点处计算得来的。
Each use case represents an average of 35 function points.
每一个用例都代表35个功能点的平均值。
After you know the total unadjusted points, it is easy to add the other factors to arrive at the unadjusted person hours, just as you did for the use case point analysis.
在您知道全部的未调整点之后，就很容易添加其他的因素以达到未经调整的私人时间，就像您对用例点分析所做的那样。
These points should be based on the personas involved in a use case and their contexts of use (see Figure 3).
这些点应该基于用例所涉及的角色和使用的上下文(参见图3)。
He states that a use case represents an average of roughly 35 function points, although it can vary between 15 and 75 function points.
他论述一个用例代表了大约35个功能点的平均值，35只是一个大概值，通常会在15及75个功能点之间进行变动。
Even if you never have a need to implement this particular use case, most of the points illustrated in this article can apply to many areas of P8 programming.
尽管您永远没有必要实现这个特殊的用例，但是本文描述的要点适用于许多P8编程领域。
Figure 3: test cases are derived from use case scenarios; evaluation points are derived from personas and included in the test cases.
图3：测试用例源于用例情境，评估点源于角色并包含于测试用例中。
Use Case 4 - Lifecycle management of business points of variability.
用例4—业务点可变性的生命周期管理。
Use Case 2 - Localized or Centralized policy and policy enforcement points.
用例2—本地或中央的策略和策略实施点。
E.g., models such as CoCoMo II, Coarse-grained Wide-band Delphi (i.e., consensus-based estimates), and function point analysis (including "use-case points").
例如，CoCoMoII模型，Coarse-grained Wide-bandDelphi （如协商一致的评估），以及功能点分析（包括“用例点”）。
In this case, you may want to use multiple points with the same coordinates so that you can have multiple normals at that point.
在这种情况下，你可以使用多个具有同样座标的点，这样在那点上你可以有多条法线。
Are all Web applications going to be modeled with use-case diagrams and UML use-case points?
是否所有的Web应用程序都要使用用例关系图和UML用例点进行建模？
Software requirement modeling and use case technology are hot points of research to the software engineering. Use case is the key technology for organic requirement in UML.
需求建模和用例技术是软件需求工程研究的热点，用例是UML中组织需求的重要技术。
Wolf's feminism by analyzing her use of "interior monologue" in her main works and points out that Wolf's androgyny is her ideal pursuit rather than the foreseen case as stated by some researchers.
通过对贯穿于弗吉尼亚·伍尔夫主要作品中的意识流写作手法——“内心独白”的分析，重新阐释伍尔夫的女性主义创作思想，认为“双性同体”只是作者的最高理想，并非已经看到或能预见的境界。
The crack reasons and repair measures for W4-60 excavator rear bridge case are analyzed, and the points for attention in manufacture and use are presented.
针对W4—60液压挖掘机后桥壳端部断裂的现象，分析了其产生断裂的原因，提出了修复工艺措施以及在制造和使用该机型时应注意的事项。
The crack reasons and repair measures for W4-60 excavator rear bridge case are analyzed, and the points for attention in manufacture and use are presented.
针对W4—60液压挖掘机后桥壳端部断裂的现象，分析了其产生断裂的原因，提出了修复工艺措施以及在制造和使用该机型时应注意的事项。
应用推荐