FP analysis is inappropriate for integration projects of any sort as it presupposes that you can specify the application up-front. Most of the work in any integration project of non-trivial complexity is reverse-engineering the nuances of the environment. Typically the environment will not be exhaustively documented in the sort of cases you would expect to use an EAI system in.
By the time you have actually done this level of reverse engineering to the point of having a complete specification you have done most of the work in the project - the actual development is fairly short and sweet by comparison. Therefore the function point analysis is only providing an estimate for a small part of the system.
As an aside, much of the work I do is data warehouse systems in Commercial insurance companies, where extensive prototyping and reconciliation exercises to produce detailed specification documents are actually quite appropriate to the environment. Typically this takes longer than actually developing the production system as most of the data issues are resolved in the prototyping work. EAI systems have a similar class of implementation issues.
Well given that FP counting is based on storage and end user interface, not sure if its even meaningful for EAI (from what little I remember).
I would say you can't, at least not in a useful way. FP counting is generally viewed as a dubious practice of varying accuracy, doing it to an integration project would just add more fuzzyness.
发布评论
评论（2）
FP 分析不适用于任何类型的集成项目，因为它假定您可以预先指定应用程序。 任何具有非凡复杂性的集成项目中的大部分工作都是对环境的细微差别进行逆向工程。 通常，在您希望使用 EAI 系统的情况下，环境不会被详尽记录。
当您实际完成此级别的逆向工程以达到拥有完整规范的程度时，您已经完成了大部分工作在该项目中 - 相比之下，实际开发相当短暂且愉快。 因此，功能点分析仅提供系统一小部分的估计。
顺便说一句，我所做的大部分工作是商业保险公司的数据仓库系统，其中广泛的原型设计和协调练习以生成详细的规范文档实际上非常适合该环境。 通常，这比实际开发生产系统需要更长的时间，因为大多数数据问题都在原型设计工作中得到解决。 EAI 系统也有类似的实施问题。
FP analysis is inappropriate for integration projects of any sort as it presupposes that you can specify the application up-front. Most of the work in any integration project of non-trivial complexity is reverse-engineering the nuances of the environment. Typically the environment will not be exhaustively documented in the sort of cases you would expect to use an EAI system in.
By the time you have actually done this level of reverse engineering to the point of having a complete specification you have done most of the work in the project - the actual development is fairly short and sweet by comparison. Therefore the function point analysis is only providing an estimate for a small part of the system.
As an aside, much of the work I do is data warehouse systems in Commercial insurance companies, where extensive prototyping and reconciliation exercises to produce detailed specification documents are actually quite appropriate to the environment. Typically this takes longer than actually developing the production system as most of the data issues are resolved in the prototyping work. EAI systems have a similar class of implementation issues.
考虑到 FP 计数是基于存储和最终用户界面的，不确定它对 EAI 是否有意义（据我所知）。
我想说你不能，至少不能以一种有用的方式。 FP 计数通常被视为一种精度不同的可疑做法，在集成项目中这样做只会增加更多的模糊性。
Well given that FP counting is based on storage and end user interface, not sure if its even meaningful for EAI (from what little I remember).
I would say you can't, at least not in a useful way. FP counting is generally viewed as a dubious practice of varying accuracy, doing it to an integration project would just add more fuzzyness.