NESMA功能点分析及应用指南

　　本指南是持续改进的NESMA方法中的新版本，阐释与ISO/IEC14143-1：2007保持一致的功能规模度量方法。NESMA功能规模度量方法也被称为功能点分析，功能规模单元也被称为功能点。 此版本是对现在已过时的一个版本（ISO/ IEC24570：2005）进行更新和阐明。

　　作者序 Nesma is very proud to present the Chinese version of the Nesma counting guidelines. In a world where standards are becoming more and more important， I am very pleased to see that in China people acknowledge this and are willing to study how to measure the functional size of software. Sizing the software in a standardized， objective， repeatable， verifiable and therefore defensible way opens up your world to software metrics！ Metrics based on Nesma function points， such as Productivity （hours per FP）， Cost efficiency （Cost per FP）， Velocity （FP per month） and Project Quality （Defects per 1000 FP） can now be measured over time and compared between teams， departments， and organizations！ Software becomes measurable and the output of software development teams can be measured objectively. By measuring functional size you can improve all kinds of processes： estimation accuracy can increase up to 60%！ Performance measurement of external suppliers can bring you millions of dollars of benefits every year. Measuring functional size is really the basis for any software development improvement program， either in traditional teams and in agile or DevOps teams. Especially if this is combined with the software project data of the International Software Benchmarking Standards Group （ISBSG）. Please use these counting guidelines， that contain dozens of years of practical experience， to measure the functional size of software development so that it becomes possible to demonstrate business value to your customers based on facts and data…not on opinions. Kind regards， Harold van Heeringen Board member

目 录

第1部分：Nesma计数指南

功能点分析定义和计数指南

第2部分：应用指南

一、合同度量指标指南
二、管理迷你指南
三、招标书问题迷你指南
四、技术质量迷你指南
五、供应商绩效评估迷你指南

第3部分：行业数据分析报告

一、中国软件行业基准数据报告（SSMBK201706）
二、技术与工具使用：项目影响分析
三、从雷夫“敏捷方法的定量分析”研究中所得的十大成果
四、软件项目成本
五、网络项目有何不同
六、程序包定制化服务
七、政府与非政府软件项目的表现
八、比较外包项目、离岸项目、组织内项目
九、制定项目计划：各角色投入比例
十、影响研发效率的项目属性
十一、利用规模和工作量分析项目工期
十二、软件行业绩效报告
十三、软件缺陷密度分析报告
十四、团队规模和软件规模对项目交付率的影响