您的当前位置：首页 REP01T02-Software Requirements Specification (OO Method)

REP01T02-Software Requirements Specification (OO Method)

来源：五一七教育网

产品名称Product name 产品版本Product version 密级Confidentiality level Total 19pages 共19页 XX Software Requirements Specification (OO)

XX 软件需求规格说明书 (OO)

Prepared by

拟制

Reviewed by 评审人 Approved by

批准

Authorized by

签发

Name+ID 姓名+工号

Date 日期 Date 日期 Date 日期 Date 日期

yyyy-mm-dd yyyy-mm-dd yyyy-mm-dd yyyy-mm-dd

Huawei Technologies Co., Ltd.

华为技术有限公司

（REP01T01 V1.2/ IPD-CMM V3.0 / for internal use only）（REP01T01 V1.2/ IPD-CMM V3.0 / 仅供内部使用）

XX Software Requirements Specification (OO) XX 软件需求规格说明书 (OO)

Please input confidentiality level

请输入密级

Revision Record 修订记录

Date 日期 RevisioCR ID Sec Change Description n / No. 修改描述 Version Defec修改 t ID 修订章节 CR号版本 1.00 initial 初稿完成 Author 作者 2001-06-08 Name+ID 作者名+工号

Page 2 , Total 19 第2页，共19页

XX Software Requirements Specification (OO) XX 软件需求规格说明书 (OO)

Please input confidentiality level

请输入密级

Catalog 目录

1 Introduction 简介 ..................................................................................................................... 6 1.1 Objectives 目的 ................................................................................................................. 6 1.2 Scope 范围 ........................................................................................................................ 6 2 General description总体概述 ................................................................................................... 6 2.1 Software perspective 软件概述 .......................................................................................... 6 2.1.1 About the Project 项目介绍 .......................................................................................... 6 2.1.2 Environment of Product 产品环境介绍........................................................................ 6 2.2 Software function 软件功能 ................................................................................................ 7 2.3 Actors ................................................................................................................................. 8 2.4 Assumptions & Dependencies 假设和依赖关系 ................................................................ 8 3 Functional Requirements 功能需求 ......................................................................................... 8 3.1 Package Overview 包图 ..................................................................................................... 8 3.2 Package1 包1 ..................................................................................................................... 8 3.2.1 Use Case diagram 用例图 ............................................................................................ 9 3.2.2 Use Case 1 用例1 ........................................................................................................ 9 3.2.3 Use Case2 用例2 ....................................................................................................... 12 4 Performance Requirements 性能需求 ................................................................................... 12 4.1 Performance requirement1 性能需求1 ............................................................................ 12 5 Interface Requirements 接口需求 .......................................................................................... 13 5.1 User Interface 用户接口 ................................................................................................... 13 5.2 Software Interface 软件接口 ............................................................................................ 14 5.3 Hardware Interface 硬件接口 ........................................................................................... 14 5.4 Communication Interface 通讯接口 ................................................................................. 15 5.5 Other Interfaces 其他接口 ................................................................................................ 15 6 Overall Design Constraints 总体设计约束 ............................................................................. 15 6.1 Standards compliance 标准符合性 .................................................................................. 15 6.2 Hardware Limitations 硬件约束 ........................................................................................ 15 6.3 Technology Limitations 技术..................................................................................... 16 7 Software Quality Attributes 软件质量特性 ............................................................................. 16 7.1 Reliability 可靠性 .............................................................................................................. 16 7.2 Usability 易用性 ................................................................................................................ 16 8 Other Requirements其他需求 ................................................................................................ 17 8.1 Database数据库 ............................................................................................................... 17 8.2 Operations 操作 ............................................................................................................... 17 8.3 Localization 本地化 .......................................................................................................... 17 9 Requirements Classification 需求分级 .................................................................................. 17 10 Issues To Be Determined 待确定问题 ............................................................................. 18 11 Appendix 附录 .................................................................................................................. 18 11.1 Feasibility Study Results 可行性分析结果 ....................................................................... 18 11.2 Glossary词汇表 ................................................................................................................ 18

Page 3 , Total 19 第3页，共19页

Table List 表目录

Table1 **表 ................................................................................................ 错误！未定义书签。表1 **表 ...................................................................................................... 错误！未定义书签。

Figure List 图目录

Figure 1 **图 ................................................................................................ 错误！未定义书签。图 1 **图 ...................................................................................................... 错误！未定义书签。

XX Software Requirements Specification (OO) XX 软件需求规格说明书 (OO)

Please input confidentiality level

请输入密级

XX Software Requirements Specification (OO)

XX 软件需求规格说明书 (OO)

Keywords 关键词： Abstract 摘要：

List of abbreviations 缩略语清单：<对本文所用缩略语进行说明，要求提供每个缩略语的英文全名和中文解释。Describe abbreviations in this document, full spelling of the

abbreviation and Chinese explanation should be provided.>

Abbreviations缩略语 Full spelling 英文全名 Chinese explanation 中文解释

Page 5 , Total 19 第5页，共19页

XX Software Requirements Specification (OO) XX 软件需求规格说明书 (OO)

Please input confidentiality level

请输入密级

1 1.1

Introduction 简介 Objectives 目的

This section should state the purpose of the document. It could also specify the intended audience. Identify the product whose software requirements are specified in this document.

这部分要描述文档的目的。应该指明读者。说明本需求文档描述了哪个产品的软件需求。

1.2 Scope 范围

This section should address areas which this document includes and that are specifically excludes.

本节应描述文档所包括和不包括的内容。

2 General description总体概述

Describes the general elements that may affect the product and the requirements on the

product. It includes the following four parts. Note that this section should not describe the specific requirements, instead, it makes the specific requirements to be described more understandable.

本节描述影响产品和产品需求的一般因素。由以下4个部分构成。有一点需说明的是本节不描述具体的需求，只是使那些将要描述的具体需求更易于理解。 2.1

Software perspective 软件概述

2.1.1 About the Project 项目介绍

Describe the context and origin of the project being specified in this SRS. For example, state whether this project is a follow-on member of a project family, a replacement for certain existing systems, or a new, self-contained project.

描述本软件需求所描述的项目的背景。例如：本项目是一系列版本中的一个，或者是替代某个已经存在的系统，还是一个新的的项目。 2.1.2 Environment of Product 产品环境介绍

Describes the whole environment that is composed of this software and other products / projects.

1. If this software is independent or fully self-contained, state it here.

Page 6 , Total 19 第6页，共19页

XX Software Requirements Specification (OO) XX 软件需求规格说明书 (OO)

Please input confidentiality level

请输入密级

2. If the software defined by this SRS document is a component of a larger system/project (this always happens), then this section should:

A. describes the function of each component of that larger system/project, and identifies B. determine the main external interfaces of this software.（ Note: Do not describe the

the interfaces.

interfaces in detail; the detailed description will be provided in other part of the SRS document.）

C. describe related hardware of the product and peripheral equipment.（ Note: This is

only a general description, not in detail.）

It is very helpful to describe the main components, interconnection and external interfaces of the larger system/project by Block Diagram. This part should not provide a detailed design solution, or detailed design constraint for the solution (the detailed design constraint will be described in the section of specific requirement). This section is the basis of the design constraints.

描述的是本产品与其它产品或项目所组成的整体环境。

1.如果本产品是的并完全自我包含，在此说明这一点。

2.如果SRS定义的产品是更大的系统或项目的组件（此种情形经常发生），那么应：

A. 描述此大系统或项目每个组件的功能，并且标识接口。

B. 确定本软件产品主要外部接口。（注意：在此部分并不进行这些接口的详细描述；对这些接口的详细描述在SRS的其它部分提供。）

C. 描述相关产品硬件和所使用的外部设备。（注意：这只是概述性描述。）

通过方块图来描述大系统或项目的主要组件，互连性以及外部接口将是非常有帮助的。本部分不应提出一个具体的设计解决方案或对解决方案的具体设计约束（具体设计约束将在具体需求章节中描述）。本部分内容是产生设计约束的基础。 2.2

Software function 软件功能

Summarizes the major functions that must be implemented through the software, and the functions to be implemented through user operation. Details will be provided in the Specific Requirement, so only a summary (such as a directory list) is needed here. The functions should be organized to make them understandable to the readers, and be appropriate for subsequent design and tests. Diagrams like top-level data flow diagram or object class diagram are recommended to illustrate the relationships among the major requirement groups

Sometimes, this section can directly refer to the superior specification of the software that allocates the specific requirements to this software (if existed).

The specific requirements should not be described in this section. But this section is the basis of the specific requirements.

Page 7 , Total 19 第7页，共19页

XX Software Requirements Specification (OO) XX 软件需求规格说明书 (OO)

Please input confidentiality level

请输入密级

概述软件的必须实现的和通过用户操作实现的主要功能。这里只需要进行简要描述（例如目录列表），详细描述在详细需求部分描述。对需求功能进行组织，以便于读者理解，并能指导后续的设计和测试。可以用图表来表示主要需求群组之间的关系，例如：高层的数据流图，面向对象的分析等。

有时此部分所要求的功能概述可以从分配具体功能给此软件产品的更高层规格（如果存在的话）直接引用。

本节不应描述具体需求。但本节内容是具体需求章节的基础。

2.3 Actors

List down all actors of the system, describe the meaning and required characteristics。

列出系统的所有Actor，简要描述其含义和特征。 2.4

Assumptions & Dependencies 假设和依赖关系

List any assumed factors (as opposed to known facts) that could affect the requirements stated in the SRS. These could include third party or commercial components that you plan to use, issues around the development or operating environment, or constraints. The project could be affected if these assumptions are incorrect, are not shared, or change. Also identify any dependencies the project has on external factors, such as software components that you intend to reuse from another project, unless they are already documented elsewhere (for example, in the vision and scope document or the project plan).

列出可能影响SRS中需求的所有的假设因素（与已知事实相对而言），包括准备使用的第三方或商业组件，操作和开发环境的问题约束等。如果上述假设不正确、没有被告知或者改变了都将对项目产生影响。列出项目对外部条件的依赖，例如重用其他项目的模块等。如果在其他文档（例如项目计划或范围文档等）里已经描述了，在这里可以不用描述。

3.1

Functional Requirements 功能需求 Package Overview 包图

This section describes the package and relationship. This section isn't needed if there is no package。

描述包的划分和包之间的关系。（如果没有包的划分，此节不用描述）

3.2 Package1 包1

Don't really say \"Package1.\" State the package name。

Page 8 , Total 19 第8页，共19页

XX Software Requirements Specification (OO) XX 软件需求规格说明书 (OO)

Please input confidentiality level

请输入密级

写出包的名字，不要用“包1”作为标题。 3.2.1 Use Case diagram 用例图

List use case diagram, including all involved actors, use cases and relationships between them。

描述用例图，包括涉及到的所有Actor、用例及其关系。

The name should be described as a short active verb phrase to represent the goal of the use case.

用例的名字使用能够表达用例目标的动词短语，并采用主动语态。

The following sections must be repeated for each requirement。

在每一条需求描述中重复下列部分 3.2.2 Use Case 1 用例1

Please don't use \"Use Case 1\" as the title of the use-case. Name the use-case with a few simple words and a requirement ID. For example:

R.INTF.CALC.001 Calculating expression R.INTF.CALC.002 Print

Naming the requirement ID shall follow the Software Requirements Management Procedure (REP01)

用需求编号加上简短词汇做为用例名，不要用“用例1”作为用例名，例如：R.INTF.CALC.001 计算表达式

R.INTF.CALC.002 打印

需求编号规则按照软件需求管理规程(REP01)进行

<可选: 必要的话,可以在此增加本Use Case 到其相关User Interface的链接>

3.2.2.1 Goal in Context 简要说明

A longer statement of the goal in context if needed。

简要介绍该用例的目的、作用和背景 3.2.2.2 Preconditions 前置条件

State of the system must be to run this use case

用例的前置条件是执行用例之前系统必须存在的状态 3.2.2.3 End Condition 后置条件

Page 9 , Total 19 第9页，共19页

XX Software Requirements Specification (OO) XX 软件需求规格说明书 (OO)

Please input confidentiality level

请输入密级

Success End Condition 成功后置条件

The state of the world upon successful completion 用例成功执行完毕系统可能处于的一组状态

Failed End Condition 失败后置条件 The state of the world if goal abandoned 用例执行失败后系统可能处于的一组状态

3.2.2.4 Actors

A role name or description for the actor Actor的名称，或描述（可选）

3.2.2.5 Trigger 触发条件

the action upon the system that starts the use case, may be time event 。

启动use case的动作或事件，如时间事件。 3.2.2.6 Description 基本事件流描述

When actor acts, the use case begins. The use case is always bringed out by actor, and

should describe the action of the actor and the response of the system.

当Actor有所行动时，此用例随即开始。总是由Actor来带动用例。用例应说明Actor的行为及系统的响应。应按照Actor与系统进行对话的形式来逐步引入用例。

Use case should describe the internal events of the system, not the cause or reason. If

there is exchange of information, you should explain the information in detail. E.g. It's not enough to write \"Actor inputs information of customer\address of customer\".

用例应说明的是系统内发生的事件，而不是事件发生的方式和原因。如果进行了信息交换，则需指出来回传递的具体信息。例如，只表述Actor输入了客户信息就不够明确。最好明确地说Actor输入了客户姓名和地址。通常可以利用词汇表让用例的复杂性保持在可控范围内  您最好在词汇表中定义客户信息等内容，使用例不至于陷入过多的细节。

This section includes the basic event flow. If extensions are very simple, you can put

them here directly. If extensions are complex, you should list them at next section.

简单的备选流可以在用例文本中提供。如果只需几句话就可说明存在备选流时将发生的事件，则可以直接在事件流一节中说明。如果备选流较为复杂，则需要用另外一节来单独说明。例如，备选流小节解释如何说明较复杂的备选流。

Although plain texts can't be replaced here, a picture is more effective sometimes; you

can paste any picture in this document if it's useful to understand the use case. These pictures should be understood by the reader. Remember, your attention is to explain the problem, not to produce confusion.

XX Software Requirements Specification (OO) XX 软件需求规格说明书 (OO)

Please input confidentiality level

请输入密级

虽然清晰明了的叙述性文字是无可替代的，但有时一幅图要比千言短文更具说明性。只要表达得简洁明了，您就可以在用例中任意粘贴用户界面和流程的图形化显示方式，或是其他图形。如果流程图有助于描述复杂的决策流程，那么一定要充分利用它！同样，对于与状态相关的行为，状态转移图通常比数页文字更能清晰地描述系统的行为。根据问题来选用妥当的表示方法，但应慎用您的读者可能不太明了的术语、符号或图形。请切记，您的目的是要阐明问题，而不是混淆问题。

Step 步骤

1、put here the steps of the scenario from trigger to goal delivery, and any cleanup after

描述从触发到目标获得的场景或步骤 2、... 3、

3.2.2.7 Extensions 备选事件流

Extensions describe the exceptions of the basic description. After the extensions end, the basic event will go on, if there is no special note.

将备选流小节当作备选行为 在许多情况下，由于主事件流中发生异常事件，这时每个备选流都可代表备选行为。这些备选流的长度可以是说明与备选行为相关的事件所需的长度。当备选流结束时，除非另外说明，主事件流的事件将重新开始。

Step 步骤

推荐采用数字和字母间隔的方式描述备选事件流。

1a ... 1a1 ... 1a2 2a 2b

（对应于基本事件流第1步的一个扩展流）该扩展事件流的第1个步骤该扩展事件流的第2个步骤

3.2.2.8 Special Requirement 特殊需求

Special Requirements are nonfunctional requirement, they belong to this use case, but it's difficult to describe in the basic event flow of the use case. Special requirements include law、quality、restriction etc.

特殊需求通常是非功能性需求，它为一个用例所专有，但无法在用例的事件流文本中较容易或较自然地进行说明。特殊需求的示例包括法律或法规方面的需求、应用程序标准和质量属性（包括可用性、可靠性、性能或支持性需求）。

XX Software Requirements Specification (OO) XX 软件需求规格说明书 (OO)

Please input confidentiality level

请输入密级

1、

3.2.3 Use Case2 用例2

...

4 Performance Requirements 性能需求

If there are performance requirements, state them here and explain their rationale, to help

the developers understand the intent and make suitable design choices. Specify the timing relationships for real time systems. Make such requirements as specific as possible.

如果有性能方面的需求，在这里列出并解释他们的原理。以帮助开发者理解意图以做出正确的设计选择。在实时系统中的时序关系。保证需求尽可能的详细而精确。 4.1

Performance requirement1 性能需求1

Describes the statically and dynamically quantized requirements on the software (or the interaction between user and the software)

Static quantized requirement could include: A. Maximum number of terminal supported.

B. Maximum number of users that can use the software at the same time. C. Maximum number of files and records to be processed D. Maximum size of tables and files

Dynamically quantized requirements could include:

A. Specific duration of normal value and peak value of workload (e.g., one hour) B. Number of event and task and data volume to be processed

All these requirements should be described by measurable term, for example, saying \"95% of the events should be processed in 1 secondhe business to complete.\"

Note: The quantized constraint of a detailed requirement should be described in the subsection of the detailed requirement.

本子章节应从整体上描述静态和动态的量化的对软件（或人与软件交互）的需求。静态的量化需求可能包括：

A. 支持的终端数目。

B. 支持的同时使用的用户数目。 C.处理的文件和记录的数目。 D.表和文件的大小。

动态的量化需求可能包括:

A. 在正常和峰值工作量条件下特定时间段（如一小时）

XX Software Requirements Specification (OO) XX 软件需求规格说明书 (OO)

Please input confidentiality level

请输入密级

B. 处理的事务和任务的数目以及数据量。

所有的这些需求应以可测量的术语进行描述，例如所有的操作应在1秒内被处理完成，而不是描述成操作员不必等待操作的完成。

注意：用于一个具体功能的量化通常在该功能对应的Use Case的特殊需求子章节中描述。

5 5.1

Interface Requirements 接口需求 User Interface 用户接口

详细描述系统与用户之间的接口

This section should include:

A. Features that must be supported by the software for each man-machine interface. For example, if the user operates from a display terminal, then the following should be included:

Screen format required

Page layout and content of report and menu Timing sequence for input and output Usage of some functional key combinations

B. Every aspect about the use of the system's user interface. It could be a list that shows the user what should do and what should not do. For example, an option of overlong or overshot message. . And same as other requirements, these requirements should be easily verified. For example, saying \"A level 4 typist can finish function X in Z minutes after a one-hour training.\" instead of \"A typist can finish function X\"

这应描述下述内容：

A. 对每种人机界面，软件所必须支持的特性。例如，如果系统用户通过一个显示终端进行操作，那么应包含下述内容：

要求的屏幕格式

页面规划及报告或菜单的内容输入和输出的相关时序一些组合功能键的用法

B. 与系统用户接口使用相关的所有方面。这可能只是一个简单的关于系统怎样展示给用户而该做什么和不该做什么的列表。例如提供关于长或短错误消息选项。和所有其它需求一样，这些需求也应能被检验，例如，四级打字员经一小时的培训后能在Z分钟内完成功能X，而不是一个打字员能完成功能X。

XX Software Requirements Specification (OO) XX 软件需求规格说明书 (OO)

Please input confidentiality level

请输入密级

5.2 Software Interface 软件接口

详细描述与其他系统 /模块 /项目之间的接口

Describes how to use the other (required) software products. (Such as data management system, operation system, or algorithm tools package), and the interfaces to other application systems (such as interfaces between the protocol process system and the database management system)

For each required software product, following information should be provided: A. Name

B. Mnemonic symbol C. Version number D. Source

For each interface, this section should:

A. Discuss the objective of the required software.

B. Define the interfaces by content and format of message/function. If the interfaces have been clearly described in other documents, it is not necessary to describe in detail here. But the reference of those documents should be given.

在此应描述如何使用其它（必需的）软件产品（例如，数据管理系统，操作系统，或算法工具包），以及与其它应用系统的接口（例如，协议处理系统和数据库管理系统之间的接口）。

对每个必需的软件产品，应提供下列信息：

A. 名字 B. 助记符 C. 版本号 D. 来源

对每个接口，本部分应：

A . 讨论与本软件产品相关的接口软件的目的。

B. 按消息/函数内容和格式定义接口。如果接口已在其它文档中很清楚地描述，就没有必要在这儿进行详细描述，但需说明应参考的文档。

5.3 Hardware Interface 硬件接口

详细描述与硬件的接口

Describes the logical features of the interface between the software and hardware components, including the equipment supported and how the equipment and protocol is supported.

XX Software Requirements Specification (OO) XX 软件需求规格说明书 (OO)

Please input confidentiality level

请输入密级

Defines the interfaces according to the content and format of the software/hardware protocol. If the interfaces have been clearly described in other documents, it is not necessary to describe in detail here. But the reference of those documents should be given.

在此描述软件产品和系统硬件组件之间接口的逻辑特征，也包括支持哪些设备、怎样支持这些设备和协议等。

按软/硬件协议内容和格式定义接口。如果接口已在其它文档中很清楚地描述，就没有必要在这儿进行详细描述，但需说明应参考的文档。

5.4 Communication Interface 通讯接口

详细描述通讯接口，如本地网络协议等。

Defines the interfaces according to the content and format of the message/function. If the interfaces have been clearly described in other documents, it is not necessary to describe in detail here. But the reference of those documents should be given.

按消息/函数内容和格式定义接口。如果接口已在其它文档中很清楚地描述，就没有必要在这儿进行详细描述，但需说明应参考的文档。

5.5 Other Interfaces 其他接口

Some internal interfaces, which are critical to the project, could also be highlighted.

一些非常关键的内部接口 6

Overall Design Constraints 总体设计约束

Describe any items or issues that will limit the options available to the developers.

描述可能开发人员选择的事项。 6.1

Standards compliance 标准符合性

This subsection should specify the requirements derived from existing standards or regulations. In case, if the project refers any International standards, then the deviations from the standards could be specified along with the International standards reference.

本节详细说明需求所采用的标准或规范的来源。如果项目采用了国际标准，应该说明国际标准及项目与标准的偏离情况。 6.2

Hardware Limitations 硬件约束

XX Software Requirements Specification (OO) XX 软件需求规格说明书 (OO)

Please input confidentiality level

请输入密级

This subsection could include Requirements for the software to operate inside various hardware constraints, such as timing constraints, memory constraints etc.)

本节包括软件在不同的硬件平台运行的需求，如时间相关的约束，内存方面的约束等。 6.3

Technology Limitations 技术

This subsection could include limitations on the use of specific technologies, interfaces, databases, parallel operations; communications protocols; design conventions or programming standards.

本节包括对使用特定技术的，包括接口，数据库，并行操作，通讯协议，设计约定，编程规范等。 7

Software Quality Attributes 软件质量特性

Specify any additional quality characteristics for the project that will be important to either the customers or the developers. Some to consider are: adaptability, availability, correctness, flexibility, interoperability, maintainability, portability, reliability, reusability, robustness, testability, and usability. Write these to be specific, quantitative, and verifiable when possible. At the least, clarify the relative preferences for various attributes, such as ease of use over ease of learning.

详细说明项目任何其他的质量特性。该特性对客户和开发者都非常重要。考虑的方面包括：适应性，可用性，正确性，灵活性，交互工作能力，可维护性，可移植性，可靠性，可重用性，鲁棒性，可测试性和可用性等。定量的详细描述这些特性，尽可能的可验证。对不同属性之间的重要性加以阐述，如：易用性比易学性更重要。

Please use the below sub-section for each attributes separately. You can copy the section for additional attributes.

每一个属性单独使用一个小节描述，可根据需要进行增减，如增加可维护性小节等。 7.1

Reliability 可靠性

Fault Tolerance: Ability to maintain a specified level of performance in spite of software faults.

Recoverability: Capability to recover in case of a failure and reestablish its level of performance

容错性：在出现软件错误的时候仍然能够维持某种层次性能的能力。可恢复性：在出现故障时的恢复能力和重新建立某种层次性能的能力。

7.2 Usability 易用性

Understandability: User's effort for recognizing the logical concept and its applicability.

XX Software Requirements Specification (OO) XX 软件需求规格说明书 (OO)

Please input confidentiality level

请输入密级

Learn ability: User's effort for learning the application.

Operability: User's effort for operating the application and operational control.

易懂性：用户通晓逻辑概念花费的人力和软件的适用性。易学性：用户学习应用程序花费的人力。易操作性：用户操作应用程序所花费的人力。 8

Other Requirements其他需求

Any other requirement specified by the customer need to be listed below with appropriate section. This may include Database, Coding requirements, Error handling, Testing requirements etc., few sample requirements are listed below. Please note, you may remove or add if something is not applicable.

使用适当的章节，详细说明任何其他客户需求，包括数据库，编码需求，错误处理，测试需求等。下面仅列出了少量样例，你可以删除和增加项目。 8.1

Database数据库

This could specify the requirements for any database that is to be developed as part of the project.

详细说明项目相关的数据库方面的需求。 8.2

Operations 操作

This could specify the normal and special operations required by the user.

详细说明用户通常的和特殊的操作需求。 8.3

Localization 本地化

Any requirement on multi language operation could be described here.

描述支持多语种的需求。 9

Requirements Classification 需求分级

Requirement Name 需求名称 Classification 需求分级 Requirement ID 需求ID Importance of requirements is classified as following:

XX Software Requirements Specification (OO) XX 软件需求规格说明书 (OO)

Please input confidentiality level

请输入密级

A. Mandatory: absolutely essential features, without which the product development will be canceled.

B. Important: unessential features that may affect the viability of the product.

C. Nice to have: desired features, the absence of which will not affect the product viability.

重要性分类如下：

A. 必须的 B. 重要的 C. 最好有的

绝对基本的特性；如果不包含，产品就会被取消。不是基本的特性，但这些特性会影响产品的生存能力。

期望的特性；但省略一个或多个这样的特性不会影响产品的生存能力。

10 Issues To Be Determined 待确定问题

Requirement Description ID 问题描述需求ID Effect Risk 影响风险 (H/M/L) ResponsibilitResolving Date y 解决日期责任人 Status 状态(Open/Close) 11 Appendix 附录

11.1 Feasibility Study Results 可行性分析结果

Describe the feasibility study results for accepted requirements.

描述对接受需求的可行性分析结果。 11.2 Glossary词汇表

Glossary is optional, and use this template。

词汇表作为可选内容, 使用以下模板。

(建议词汇表作为单独的CI, 这里列出它的位置和文件名即可。）

XX Software Requirements Specification (OO) XX 软件需求规格说明书 (OO)

Please input confidentiality level

请输入密级

List of reference 参考资料清单：

Please list referred literature and related documents, format:

请罗列本文档所参考的有关参考文献和相关文档，格式如下：

Author + book name (or magazine, literature, document) + publishing company (or issue No., volume No., internal documentation ID) + publishing date + start and end page number,

作者＋书名（或杂志、文献、文档）＋出版社（或期号、卷号、公司文档编号）＋出版日期+起止页码

Examples:

例如：

[1] D. B. Leeson, “A Simple Model of Feedback Oscillator Noise Spectrum,” Proc. IEEE, pp329-330, February 1966 （英文文章格式）

[2] D. Wolaver, Phase-Locked Loop Circuit Design, Prentice Hall, New Jersey,1991 （英文书籍格式）

[3] 王阳元，奚雪梅等，“薄膜SOI/CMOS SPICE电路模拟”，电子学报，vol.22，No.5，1994

（中文文章格式）

[4] 郑筠，《MOS存储系统及技术》，科学出版社，1990 （中文书籍格式） [5] XXX，SDXXX用户手册 V1.1，基础部文档室，2001/4/26

因篇幅问题不能全部显示，请点此查看更多更全内容

查看全文