Function Points and WBS are two different, but related items. Function Points is a unit of measurement that can be used to determine complexity and work effort, WBS (work breakdown structure) is an approach to define sub units to a project (problem).
SO, when starting a project with a given scope and set of expectations, you use a WBS to define the sub units of the project (to a degree that is useful for you), once you have well defined sub units, you can determine the work effort by assigning function points to each and multiplying velocity (# of function points per day that can be delivered- as an example).
I just took the introductory course of a project management program, and we didn't even look at "function point analysis" (I'm not sure what that is), but we spent a lot of time looking at WBS. All the following processes referred back to the WBS.
功能点已经过时了，但它们确实非常有效。 我强烈建议您进一步研究 Capers Jones 的作品，他出版了一些很棒的书籍，有助于为软件项目带来衡量和确定性。
Function Points have gone out of fashion, but they do work very well. I urge you to look further at the work of Capers Jones who has published some terrific books that help bring measurement and certainty to software projects.
FPA is not an effort estimation technique itself. FPA is used to determine the 'functional size' of requirements to a software, expressed in 'function points' (fp), thus can be one of many input variables for a more complex effort estimation model (such as COCOMO).
Do not mistake 'estimation' for 'planning'. WBS is a planning technique, that requires detailed knowledge on what and how to build/develop. In contrast, estimation is a forecast of expected effort/costs based on limited facts.
So it's not about 'one-or-the-other' but rather 'when-what'.
发布评论
评论（6）
功能点和 WBS 是两个不同但相关的项目。 功能点是一种测量单位，可用于确定复杂性和工作量，WBS（工作分解结构）是一种定义项目（问题）子单元的方法。
因此，当开始具有给定范围和期望集的项目时，您可以使用 WBS 来定义项目的子单元（达到对您有用的程度），一旦您定义了良好的子单元，您就可以确定项目的子单元。通过为每个功能点分配功能点并倍增速度（每天可以交付的功能点数量 - 作为示例）来完成工作量。
以下是一些有用的链接：
Function Points and WBS are two different, but related items. Function Points is a unit of measurement that can be used to determine complexity and work effort, WBS (work breakdown structure) is an approach to define sub units to a project (problem).
SO, when starting a project with a given scope and set of expectations, you use a WBS to define the sub units of the project (to a degree that is useful for you), once you have well defined sub units, you can determine the work effort by assigning function points to each and multiplying velocity (# of function points per day that can be delivered- as an example).
Here are some useful links:
我刚刚上了项目管理程序的入门课程，我们甚至没有看“功能点分析”（我不确定那是什么），但我们花了很多时间看WBS。 以下所有流程均返回至 WBS。
I just took the introductory course of a project management program, and we didn't even look at "function point analysis" (I'm not sure what that is), but we spent a lot of time looking at WBS. All the following processes referred back to the WBS.
我只能谈谈我所看到的。 我在墨西哥看到 IBM 使用功能点来确定产品规模并支付分包商费用。
问候...
I can only talk about what I have seen. I have seen IBM use Function Points in Mexico to determine product size and pay subcontractors.
Regards...
九十年代初期，我在大学时就做过功能点分析，但当我真正进入职场后，它就再也没有出现过。
I did function point analysis back in university in the early nineties, but it never came up again once I actually entered the work force.
功能点已经过时了，但它们确实非常有效。 我强烈建议您进一步研究 Capers Jones 的作品，他出版了一些很棒的书籍，有助于为软件项目带来衡量和确定性。
Function Points have gone out of fashion, but they do work very well. I urge you to look further at the work of Capers Jones who has published some terrific books that help bring measurement and certainty to software projects.
FPA 本身不是一种工作量估算技术。 FPA 用于确定软件需求的“功能规模”，以“功能点”(fp) 表示，因此可以是更复杂的工作量估计模型（例如 COCOMO）的众多输入变量之一。
不要将“估计”误认为“计划”。 WBS 是一种规划技术，需要详细了解构建/开发内容以及如何构建/开发。 相反，估计是基于有限事实对预期工作/成本的预测。
因此，这不是“一个或另一个”的问题，而是“何时、什么”的问题。
FPA is not an effort estimation technique itself. FPA is used to determine the 'functional size' of requirements to a software, expressed in 'function points' (fp), thus can be one of many input variables for a more complex effort estimation model (such as COCOMO).
Do not mistake 'estimation' for 'planning'. WBS is a planning technique, that requires detailed knowledge on what and how to build/develop. In contrast, estimation is a forecast of expected effort/costs based on limited facts.
So it's not about 'one-or-the-other' but rather 'when-what'.