In one discussion among colleagues I have heard that function point analysis is not used nowadays since it can go wrong for various reasons.
在同事之间的一次讨论中,我听说现在没有使用功能点分析,因为它可能由于各种原因而出错。
So WBS (work breakdown structure) is used commonly.
因此通常使用WBS(工作分解结构)。
Is that true?
真的吗?
6 个解决方案
#1
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).
功能点和WBS是两个不同但相关的项目。功能点是可用于确定复杂性和工作量的度量单位,WBS(工作分解结构)是一种将子单元定义到项目(问题)的方法。因此,当启动具有给定范围和期望集的项目时,您使用WBS来定义项目的子单位(对您有用的程度),一旦您有明确定义的子单位,您就可以确定通过为每个功能点分配功能点和倍增速度(每天可以提供的功能点数#)作为工作量。
Here are some useful links:
以下是一些有用的链接:
- Function Points via Wikipedia
- Software Sizing During Requirements Analysis
- WBS via Wikipedia
- step by step WBS
通过*的功能点
需求分析期间的软件大小调整
WBS通过*
一步一步WBS
#2
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.
我刚刚参加了项目管理程序的入门课程,我们甚至没有看到“功能点分析”(我不确定那是什么),但我们花了很多时间看WBS。以下所有流程均返回WBS。
#3
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.
我只能谈谈我所看到的。我见过IBM在墨西哥使用功能点来确定产品规模并支付分包商费用。
Regards...
#4
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.
我在九十年代初期在大学里做过功能点分析,但是一旦我真正进入劳动大军,它就再也没有出现过。
#5
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.
功能点已经过时了,但它们确实很有效。我恳请你们进一步研究Capers Jones的工作,他们已经出版了一些很棒的书籍,有助于为软件项目带来测量和确定性。
#6
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).
FPA本身不是一种努力估计技术。 FPA用于确定软件需求的“功能大小”,以“功能点”(fp)表示,因此可以是更复杂的工作量估算模型(如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.
不要将“估计”误认为是“计划”。 WBS是一种规划技术,需要详细了解什么以及如何构建/开发。相反,估计是基于有限事实的预期努力/成本的预测。
So it's not about 'one-or-the-other' but rather 'when-what'.
所以这不是“一个或另一个”,而是“什么时候”。
#1
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).
功能点和WBS是两个不同但相关的项目。功能点是可用于确定复杂性和工作量的度量单位,WBS(工作分解结构)是一种将子单元定义到项目(问题)的方法。因此,当启动具有给定范围和期望集的项目时,您使用WBS来定义项目的子单位(对您有用的程度),一旦您有明确定义的子单位,您就可以确定通过为每个功能点分配功能点和倍增速度(每天可以提供的功能点数#)作为工作量。
Here are some useful links:
以下是一些有用的链接:
- Function Points via Wikipedia
- Software Sizing During Requirements Analysis
- WBS via Wikipedia
- step by step WBS
通过*的功能点
需求分析期间的软件大小调整
WBS通过*
一步一步WBS
#2
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.
我刚刚参加了项目管理程序的入门课程,我们甚至没有看到“功能点分析”(我不确定那是什么),但我们花了很多时间看WBS。以下所有流程均返回WBS。
#3
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.
我只能谈谈我所看到的。我见过IBM在墨西哥使用功能点来确定产品规模并支付分包商费用。
Regards...
#4
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.
我在九十年代初期在大学里做过功能点分析,但是一旦我真正进入劳动大军,它就再也没有出现过。
#5
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.
功能点已经过时了,但它们确实很有效。我恳请你们进一步研究Capers Jones的工作,他们已经出版了一些很棒的书籍,有助于为软件项目带来测量和确定性。
#6
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).
FPA本身不是一种努力估计技术。 FPA用于确定软件需求的“功能大小”,以“功能点”(fp)表示,因此可以是更复杂的工作量估算模型(如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.
不要将“估计”误认为是“计划”。 WBS是一种规划技术,需要详细了解什么以及如何构建/开发。相反,估计是基于有限事实的预期努力/成本的预测。
So it's not about 'one-or-the-other' but rather 'when-what'.
所以这不是“一个或另一个”,而是“什么时候”。