1,265
社区成员
发帖
与我相关
我的任务
分享
...全文
请发表友善的回复…
发表回复
futuredreams 2003-10-27
- 打赏
- 举报
附录一 用户需求文档规范
1.0 概述
这部分提供了整个需求文档的整体介绍。这个文档描述了所有数据，功能和对软件的功能和行为的需求。
1.1 目标和对象
描述大体目标和软件对象。
1.2 概述说明
软件概述描述。主要的输入，功能过程和输出描述，不考虑实现细节。
1.3 软件背景
这个软件被定位在商务软件或者产品的背景。讨论相关的战略问题，其目的是让用户对“宏图”有所把握。
1.4 主要系统参数
任何商务软件或者产品线都包含软件规定、设计、实现和测试的说明和规范。
2.0 使用方案
这部分提供了软件的使用方案。它组织了在需求分析过程中从用户用例中抽取的信息。
2.1 用户档案资料
所有用户类别在这里被描述。
2.2 用例
软件的所有用例被描述。
2.3 特殊使用说明
软件的特殊需求说明。
3.0 数据模型和描述
描述了软件所在领域的信息。
3.1 数据描述
软件中设计和管理的数据对象的描述。
3.1.1 数据对象
描述数据对象和其属性。
3.1.2 关联关系
使用ERD- like表来描述数据对象的联系。不需要提供细节描述。
3.1.3 完整数据模型
为软件建立一个ERD。
3.1.4 数据字典
为数据字典建立一个索引。数据字典包含电子表格。
4.0 功能模型和描述
描述软件主要功能模块和数据流或者面相对象的类阶层。
4.1 功能描述
软件每个功能的详细描述。
4.1.1 功能的处理叙述(PSPEC)
描述功能的处理叙述。
4.1.2 功能流程图
描述功能和底层传输的信息描述图。
4.1.3 功能接口描述
功能入口、出口的详细描述。
4.1.4 功能变换
详细描述每个功能的变形（扩展子功能）。
4.1.4.1 变形功能处理叙述(PSPEC)
4.1.4.2 变形低层流程图
4.1.4.3变形接口描述
4.1.5 执行结果
对系统的特殊表现需求描述。
4.1.6 设计系统参数
任何会影响系统的参数设计。
4.2 软间接口描述
软件对外部的接口描述。
4.2.1 机器对外接口
与其他机器或者设备的接口描述。
4.2.2 系统对外接口
对其它系统、产品和网络的接口描述。
4.2.3 与人的接口
概述软件与任何人的界面。
4.3 控制流描述
系统的控制流，参考5.0部分。
5.0 行为模型和描述
软件的行为描述。
5.1 描述软件行为
详细描述主要事件和状态。
5.1.1 事件
系统中会导致行为发生变化的事件列表（控制，项）。
5.1.2 状态
事件后续引发结果状态列表（行为模式）。
5.2 状态转换表
描述系统所有行为。
5.3 控制规格(CSPEC)
描述软件控制的风格。
6.0 约束、限制和系统参数
会影响软件的规格说明、设计和实现的特殊事件。
7.0 测试标准
描述软件验证标准。
7.1 测试的类别
规定实施测试的类别，包括尽量详细的描述。这里是针对黑盒测试现象的描述。
7.2 期待软件反馈
测试期待的结果描述。
7.3 执行界线
特殊执行需要的说明。
8.0 附录
需求说明的补充说明信息。
8.1 系统可跟踪矩阵
一个定期回归系统规格跟踪软件需求的矩阵。
8.2 产品战略
如果规格说明书是为一个产品设计的，描述相关的产品战略。
8.3 使用分析算法
描述所有分析活动所使用到的分析算法。
8.4 补充信息 (如果有需要特别说明的)
这个是偶自己翻译的，如果有不妥的地方还希望各位大虾见凉啊~
1.0 概述
这部分提供了整个需求文档的整体介绍。这个文档描述了所有数据，功能和对软件的功能和行为的需求。
1.1 目标和对象
描述大体目标和软件对象。
1.2 概述说明
软件概述描述。主要的输入，功能过程和输出描述，不考虑实现细节。
1.3 软件背景
这个软件被定位在商务软件或者产品的背景。讨论相关的战略问题，其目的是让用户对“宏图”有所把握。
1.4 主要系统参数
任何商务软件或者产品线都包含软件规定、设计、实现和测试的说明和规范。
2.0 使用方案
这部分提供了软件的使用方案。它组织了在需求分析过程中从用户用例中抽取的信息。
2.1 用户档案资料
所有用户类别在这里被描述。
2.2 用例
软件的所有用例被描述。
2.3 特殊使用说明
软件的特殊需求说明。
3.0 数据模型和描述
描述了软件所在领域的信息。
3.1 数据描述
软件中设计和管理的数据对象的描述。
3.1.1 数据对象
描述数据对象和其属性。
3.1.2 关联关系
使用ERD- like表来描述数据对象的联系。不需要提供细节描述。
3.1.3 完整数据模型
为软件建立一个ERD。
3.1.4 数据字典
为数据字典建立一个索引。数据字典包含电子表格。
4.0 功能模型和描述
描述软件主要功能模块和数据流或者面相对象的类阶层。
4.1 功能描述
软件每个功能的详细描述。
4.1.1 功能的处理叙述(PSPEC)
描述功能的处理叙述。
4.1.2 功能流程图
描述功能和底层传输的信息描述图。
4.1.3 功能接口描述
功能入口、出口的详细描述。
4.1.4 功能变换
详细描述每个功能的变形（扩展子功能）。
4.1.4.1 变形功能处理叙述(PSPEC)
4.1.4.2 变形低层流程图
4.1.4.3变形接口描述
4.1.5 执行结果
对系统的特殊表现需求描述。
4.1.6 设计系统参数
任何会影响系统的参数设计。
4.2 软间接口描述
软件对外部的接口描述。
4.2.1 机器对外接口
与其他机器或者设备的接口描述。
4.2.2 系统对外接口
对其它系统、产品和网络的接口描述。
4.2.3 与人的接口
概述软件与任何人的界面。
4.3 控制流描述
系统的控制流，参考5.0部分。
5.0 行为模型和描述
软件的行为描述。
5.1 描述软件行为
详细描述主要事件和状态。
5.1.1 事件
系统中会导致行为发生变化的事件列表（控制，项）。
5.1.2 状态
事件后续引发结果状态列表（行为模式）。
5.2 状态转换表
描述系统所有行为。
5.3 控制规格(CSPEC)
描述软件控制的风格。
6.0 约束、限制和系统参数
会影响软件的规格说明、设计和实现的特殊事件。
7.0 测试标准
描述软件验证标准。
7.1 测试的类别
规定实施测试的类别，包括尽量详细的描述。这里是针对黑盒测试现象的描述。
7.2 期待软件反馈
测试期待的结果描述。
7.3 执行界线
特殊执行需要的说明。
8.0 附录
需求说明的补充说明信息。
8.1 系统可跟踪矩阵
一个定期回归系统规格跟踪软件需求的矩阵。
8.2 产品战略
如果规格说明书是为一个产品设计的，描述相关的产品战略。
8.3 使用分析算法
描述所有分析活动所使用到的分析算法。
8.4 补充信息 (如果有需要特别说明的)
这个是偶自己翻译的，如果有不妥的地方还希望各位大虾见凉啊~
zhangtina 2003-10-24
- 打赏
- 举报
楼上的谢谢你，不过你有中文的么？我没有qq，谢谢！
futuredreams 2003-10-24
- 打赏
- 举报
SOFTWARE DESIGN SPECIFICATION
1.0 Introduction
This section provides an overview of the entire design document. This document describes all data, architectural, interface and component-level design for the software.
1.1 Goals and objectives
Overall goals and software objectives are described.
1.2 Statement of scope
A description of the software is presented. Major inputs, processing functionality, and outputs are described without regard to implementation detail.
1.3 Software context
The software is placed in a business or product line context. Strategic issues relevant to context are discussed. The intent is for the reader to understand the 'big picture'.
1.4 Major constraints
Any business or product line constraints that will impact he manner in which the software is to be specified, designed, implemented or tested are noted here.
2.0 Data design
A description of all data structures including internal, global, and temporary data structures.
2.1 Internal software data structure
Data structures that are passed among components the software are described.
2.2 Global data structure
Data structured that are available to major portions of the architecture are described.
2.3 Temporary data structure
Files created for interim use are described.
2.4 Database descriptio
Database(s) created as part of the application is(are) described.
3.0 Architectural and component-level design
A description of the program architecture is presented.
3.1 Program Structure
A detailed description the program structure chosen for the application is presented.
3.1.1 Architecture diagram
A pictorial representation of the architecture is presented.
3.1.2 Alternatives
A discussion of other architectural styles considered is presented. Reasons for the selection of the style presented in Section3.1.1 are provided.
3.2 Description for Component n
A detailed description of each software component contained within the architecture is presented. Section 3.2 is repeated for each of n components.
3.2.1 Processing narrative (PSPEC) for component n
A processing narrative for component n is presented.
3.2.2 Component n interface description.
A detailed description of the input and output interfaces for the component is presented.
3.2.3 Component n processing detail
A detailed algorithmic description for each component is presented. Section 3.2.3 is repeated for each of n components.
3.2.3.1 Interface description
3.2.3.2 Algorithmic model (e.g., PDL)
3.2.3.3 Restrictions/limitations
]3.2.3.4 Local data structures
3.2.3.5 Performance issues3.2.3.6 Design constraints
3.3 Software Interface Description
The software's interface(s) to the outside world are described.
3.3.1 External machine interfaces
Interfaces to other machines (computers or devices) are described.
3.3.2 External system interfaces
Interfaces to other systems, products, or networks are described.
3.3.3 Human interface
An overview of any human interfaces to be designed for the software is presented. See Section 4.0 for additional detail.
4.0 User interface design
A description of the user interface design of the software is presented.
4.1 Description of the user interface
A detailed description of user interface including screen images or prototype is presented.
4.1.1 Screen images
Representation of the interface form the user's point of view.
4.1.2 Objects and actions
All screen objects and actions are identified.
4.2 Interface design rules
Conventions and standards used for designing/implementing the user interface are stated.
4.3 Components available
GUI components available for implementation are noted.
4.4 UIDS description
The user interface development system is described.
5.0 Restrictions, limitations, and constraints
Special design issues which impact the design or implementation of the software are noted here.
6.0 Testing Issues
Test strategy and preliminary test case specification are presented in this section.
6.1 Classes of tests
The types of tests to be conducted are specified, including as much detail as is possible at this stage. Emphasis here is on black-box and white-box testing.
6.2 Expected software response
The expected results from testing are specified.
6.3 Performance bounds
Special performance requirements are specified.
6.4 Identification of critical components
Those components that are critical and demand particular attention during testing are identified.
7.0 Appendices
Presents information that supplements the design specification.
7.1 Requirements traceability matrix
A matrix that traces stated components and data structures to software requirements is developed.
7.2 Packaging and installation issues
Special considerations for software packaging and installation are presented.
7.3 Design metrics to be used
A description of all design metrics to be used during the design activity is noted here.
7.4 Supplementary information (as required)
呵呵，还是一样，如果需要中文的请告诉偶。
1.0 Introduction
This section provides an overview of the entire design document. This document describes all data, architectural, interface and component-level design for the software.
1.1 Goals and objectives
Overall goals and software objectives are described.
1.2 Statement of scope
A description of the software is presented. Major inputs, processing functionality, and outputs are described without regard to implementation detail.
1.3 Software context
The software is placed in a business or product line context. Strategic issues relevant to context are discussed. The intent is for the reader to understand the 'big picture'.
1.4 Major constraints
Any business or product line constraints that will impact he manner in which the software is to be specified, designed, implemented or tested are noted here.
2.0 Data design
A description of all data structures including internal, global, and temporary data structures.
2.1 Internal software data structure
Data structures that are passed among components the software are described.
2.2 Global data structure
Data structured that are available to major portions of the architecture are described.
2.3 Temporary data structure
Files created for interim use are described.
2.4 Database descriptio
Database(s) created as part of the application is(are) described.
3.0 Architectural and component-level design
A description of the program architecture is presented.
3.1 Program Structure
A detailed description the program structure chosen for the application is presented.
3.1.1 Architecture diagram
A pictorial representation of the architecture is presented.
3.1.2 Alternatives
A discussion of other architectural styles considered is presented. Reasons for the selection of the style presented in Section3.1.1 are provided.
3.2 Description for Component n
A detailed description of each software component contained within the architecture is presented. Section 3.2 is repeated for each of n components.
3.2.1 Processing narrative (PSPEC) for component n
A processing narrative for component n is presented.
3.2.2 Component n interface description.
A detailed description of the input and output interfaces for the component is presented.
3.2.3 Component n processing detail
A detailed algorithmic description for each component is presented. Section 3.2.3 is repeated for each of n components.
3.2.3.1 Interface description
3.2.3.2 Algorithmic model (e.g., PDL)
3.2.3.3 Restrictions/limitations
]3.2.3.4 Local data structures
3.2.3.5 Performance issues3.2.3.6 Design constraints
3.3 Software Interface Description
The software's interface(s) to the outside world are described.
3.3.1 External machine interfaces
Interfaces to other machines (computers or devices) are described.
3.3.2 External system interfaces
Interfaces to other systems, products, or networks are described.
3.3.3 Human interface
An overview of any human interfaces to be designed for the software is presented. See Section 4.0 for additional detail.
4.0 User interface design
A description of the user interface design of the software is presented.
4.1 Description of the user interface
A detailed description of user interface including screen images or prototype is presented.
4.1.1 Screen images
Representation of the interface form the user's point of view.
4.1.2 Objects and actions
All screen objects and actions are identified.
4.2 Interface design rules
Conventions and standards used for designing/implementing the user interface are stated.
4.3 Components available
GUI components available for implementation are noted.
4.4 UIDS description
The user interface development system is described.
5.0 Restrictions, limitations, and constraints
Special design issues which impact the design or implementation of the software are noted here.
6.0 Testing Issues
Test strategy and preliminary test case specification are presented in this section.
6.1 Classes of tests
The types of tests to be conducted are specified, including as much detail as is possible at this stage. Emphasis here is on black-box and white-box testing.
6.2 Expected software response
The expected results from testing are specified.
6.3 Performance bounds
Special performance requirements are specified.
6.4 Identification of critical components
Those components that are critical and demand particular attention during testing are identified.
7.0 Appendices
Presents information that supplements the design specification.
7.1 Requirements traceability matrix
A matrix that traces stated components and data structures to software requirements is developed.
7.2 Packaging and installation issues
Special considerations for software packaging and installation are presented.
7.3 Design metrics to be used
A description of all design metrics to be used during the design activity is noted here.
7.4 Supplementary information (as required)
呵呵，还是一样，如果需要中文的请告诉偶。
gga7959 2003-10-23
- 打赏
- 举报
就是要按照模板去套啊。如果是实例，跟你要做的系统不一样，你怎么调来用啊。。
zhangtina 2003-10-23
- 打赏
- 举报
没有实际的例子啊，那是模版啊
felio 2003-10-23
- 打赏
- 举报
我的QQ:
832606
832606
zhangtina 2003-10-23
- 打赏
- 举报
大同小异啊！
termite 2003-10-17
- 打赏
- 举报
www.51cmm.com
