在与客户交流、查阅业务资料等一系列需求获取和分析工作后，有必要及时整理用户需求，并建立需求文档。本文结合笔者的实践和相关资料给出了一个需求说明书的格式模板，希望能够起到抛砖引玉的作用，同大家作进一步探讨。

XXXX项目用户需求说明书XML:namespace prefix = o ns = "urn:schemas-microsoft-com:Office:office" />

文件状态：

[√] 草稿

[  ] 正式发布

[  ] 正在修改

文件标识：

Project No.XXX-RD-RF No.XXX

当前版本：

X.Y

作  者：

完成日期：

Year-Month-Day

关于文件的其他属性还可以根据需要添加诸如需求认可负责人、涉及的产品版本号、关联文档编号等内容。

版 本 历 史

版本/状态

作者

参与者

起止日期

备注

目录

0. 文档介绍 ······························································ 4
0.1 文档目的 ······························································4
0.2 文档范围 ······························································4
0.3 读者对象 ······························································4
0.4 参考文档 ······························································4
0.5 术语与缩写解释 ······························································4
1. 产品介绍 ······························································5
2. 产品面向的用户群体 ······························································5
3. 产品应当遵循的标准或规范 ······························································5
4.同类产品

5. 产品的功能性需求 ······························································5
5.0 功能性需求分类 ······························································5
5.n 功能（特征描叙） N ······························································6
5.n.x 功能 N.x ······························································6
6. 产品的非功能性需求 ······························································6
6.1 用户界面需求 ······························································6
6.2 软硬件环境需求 ······························································6
6.3 产品质量需求 ······························································6
6.N 其它需求 ······························································6 

附录A:

0. 文档介绍

0.1 文档目的

0.2 文档范围

0.3 读者对象

参考文档

提示：列出本文档的所有参考文献（包括非正式出版物），格式如下：

[序号标识符] 作者，文献名称，出版单位（或归属单位），日期

例如：

[P1-MF] Author，计量开发规范，机构名称，日期

术语与缩写解释

缩写、术语

解 释

…

 产品介绍

产品介绍主要说明产品特征、用途，项目背景等

2.产品用户群体

（1）描述本产品面向的用户（客户、最终用户）的特征，

（2）说明产品对他们的用处，带来的利益，用户可能的购买比例

3.同类产品情况

作为参考依据

产品应当遵循的标准或规范

阐述本产品应当遵循什么标准、规范或业务规则 

产品的功能性需求

功能性需求分类

提示：将功能性需求先粗分再细分，下表中的 Feature A, Function A.1等符号应当被替换成有含义的名称。

功能类别

子功能

Feature A

Function A.1

Function A.2

…

Feature B

Function B.1

Function B.2

…

…

5.n.m Function N.M

功能描述：

 ……

产品的非功能性需求

用户界面需求

需求名称

详细要求

…

 软硬件环境需求

需求名称

详细要求

…

主要质量属性

详细要求

正确性

健壮性

可靠性

运行效率

易用性

友好性

安全性

可扩展性

兼容性

可移植性

…

 ：