需求书模板

项目需求书第1页，共9页项目需求书文挡状态:□草稿当前版本:□正在修改负责单位:□正式发布作者:修改历史日期版本作者修改内容项目需求书第2页，共9页目录1引言.........................................................................................................................31.1编写目的································································································31.2项目背景································································································31.3术语定义································································································31.4参考资料································································································32综合描述.................................................................................................................32.1效目开发介绍·························································································32.2用户角色区分·························································································32.3项目的业务流程介绍················································································42.4项目应遵循的标准或规范··········································································43使用者需求（选用）.............................................................................................43.1总体需求································································································43.2内容需求································································································54功能需求.................................................................................................................54.1功能性需求总和······················································································54.1.1模块1（如会员注册）................................................................................................54.1.2模块2............................................................................................................................75非功能需求.............................................................................................................75.1用户界面需求（选用）·············································································75.2性能需求（选用）···················································································75.3压力需求（选用）···················································································75.4主流技术应用需求（选用）·······································································85.5安全需求（选用）···················································································85.6故障处理需求（选用）·············································································85.7环境需求（选用）···················································································85.8产品质量需求·························································································85.9其他需求（选用）···················································································96需求优先级.............................................................................................................97附加说明（选用）.................................................................................................9项目需求书第3页，共9页1引言1.1编写目的本节描述编写该用户需求说明书的目的，并指出预期的读者。1.2项目背景本节描述用户需求说明书中所定义的产品的背景和起源，以及同其他系统或其他机构的基本相互关系等。当在已有的系统上进行特性开发时，如果新特性与已有系统的特性之间存在关系，则应在本节说明其相互之间的关系。1.3术语定义本节可列出本文件中用到的专门术语的定义、外文首字母组词的原词组等。1.4参考资料本节列举编写用户需求说明书时所参考的资料或其他资源，这可能包括用户合同、公司规范、技术书籍等。在这里应该给出详细的信息，包括资料名称、版本号、作者、日期、出版单位或资料来源，以方便读者查阅这些文献，可用以下格式表示：2综合描述2.1产品介绍本节简要描述产品的特性。2.2目标范围本节简要描述产品的应用目标、作用范围等。资料名称版本号作者日期出版单位/资料来源备注项目需求书第4页，共9页2.3用户特性本节可能包括本产品各类最终用户的特点，如操作、维护等人员的知识水平和技术专长等，也可能包括用户组织关系结构图以及组织、部门、岗位的隶属关系与职能。这将是后续工作的重要依赖条件。2.4约定假设本节列举出在对软件用户需求说明书中影响需求陈述的假设因素（与已知因素相对立）。这可能包括将要使用的组件、特殊的用户界面设计约定、产品预期使用频度等。如果这些假设不正确、不一致或被更改，就会使项目受到影响。3用户需求（选用）每一项需求必须进行唯一标识，并给出该项需求的优先级。需求优先级的定义，一般需要根据用户意见结合商业价值、交付成本、交付日期、复杂程度、风险等因素来进行考虑。高优先级需求表示本系统产品中必须实现的需求，中优先级需求表示必须但是根据时间情况有可能会被推迟到下一版本的产品中去实现的需求，低优先级需求表示如果没有充足的时间或资源就可以被放弃的需求。需求编号方式可以根据项目实际情况进行自定义，也可以采用“项目代号”＋“-”＋“R”＋“需求类型”＋“序号”的形式。其中“R”表示Requirement，“需求类型”可用下表表示，“序号”以自然数表示，位数不限。需求类型英文名称中文名称FFunction功能PPerformance性能DData数据UUserInterface用户界面IInterface接口SSecurity安全MMalfunction故障处理OOther其他示例：OLTP-RI5表示为OLTP项目的第5项用户界面需求。3.1总体需求描述项目总体需求，简述项目特性等内容。项目需求书第5页，共9页3.2内容需求按照内容（如产品包、组件等）展开用户需求。4功能需求详细列出系统各模块/主题/子系统的功能需求。提示：将功能性需求先粗分再细分，下表中的FeatureA,FunctionA.1等符号应当被替换成有含义的名称（可考虑加上需求的优先级别）。在描述中要简要阐述该需求项将依赖于哪些需求项。功能类别标识符子功能名称描述FeatureAFunctionA.1…FeatureBFunctionB.1…FeatureCFunctionC.1…提示：针对本功能进行说明描述（包含其要做什么、什么流程、相关的财务、特殊要求、需要的数据等），可以采用相关的图表来更容易地表达信息。①功能描述：描述需求项的功能。②业务描述：描述该需求项的业务流程、相关的对象的状态、涉及到的业务角色等。③数据描述：描述需求项的数据项、数据精度、输出的格式等要求。④输入描述：描述该需求项的相关依赖（包括业务依赖和需求项的依赖）和输入条件。⑤输出描述：描述需求功能执行后，相应的输出产物、数据、对象状态等。4.1前台功能需求4.1.1模块1（如会员注册）4.1.1.1需求编号：此需求编号是：HICDMA-RF1项目需求书第6页，共9页4.1.1.2功能描述该模块实现网站用户的会员注册功能。网站用户通过该功能，填写用户名，密码，Email地址等信息，完成注册功能，成为网站的会员。4.1.1.3业务描述前台界面设计：图1会员注册前台页面及功能要求：会员注册页面分为三个页面，包括：会员注册信息填写页面，会员基本信息填写页面，注册成功页面。会员注册信息填写页面中还应包括验证码输入框、阅读并同意条款选择框、提交注册按钮等元素。用户填写完注册信息，并经系统验证通过后，成为网站会员，页面跳转到会员基本信息填写页面。会员基本信息填写页面包括会员基本信息选填项：姓名、固定电话、手机、性别、出生日期、现居住地、通信地址、邮编等。会员可根据情况选择性的填写，选填项信息中，姓名、现居住地、通信地址等信息不做格式上的判断；固定电话、手机信息要做格式有效性判断；性别、出生