如何编写软件需求规格书(6)
2011-08-26 23:26
211 查看
原文地址:http://www.microtoolsinc.com/Howsrs.php
How to write a software requirements specification
如何编写软件需求规格书
by Robert Japenga
__________________________________________________________________________________________
What is the difference between a design requirement and software requirement?
设计需求和软件需求有何区别?
In short, the SRS should not include any design requirements. However, this is a difficult discipline. For example, because of the partitioning and the particular RTOS you are using, and the particular hardware you are using, you may require
that no task use more than 1 ms of processing prior to releasing control back to the RTOS. Although that may be a true requirement and it involves software and should be tested, it is truly a design requirement and should be included in the Software Design
Document or in the Source code.
简单来说,SRS不应该包含设计需求。然而,这个要求做起来比较难。例如,因为你使用了特殊的RTOS[译者注:实时操作系统],使用了特殊的硬件,你可能需要每个任务的调度时间不超过1ms。尽管这是真正的需求,其包括软件,并且应该被从测试,但这真的是一项设计需求,应该包含在软件设计文档中,或者在源代码中。
Consider the target audience for each specification to identify what goes into what documents.
通过考虑每个规格书的阅读对象来识别相应的文档中应该有些什么内容。
Marketing/Product Management
Creates a product specification and gives it to Systems. It should define everything Systems needs to specify the product
市场/产品管理
编写产品规格书,给出系统。应该定义规范产品所需要的所有系统。
Systems
Creates a System Specification and gives it to Systems/Software and Mechanical and Electrical Design.
系统
创建系统规格书,给出系统/软件和机械、电气设计。
Systems/Software
Creates a Software Specification and gives it to Software. It should define everything Software needs to develop the software.
系统/软件
常见软件规格书,给出软件。应定义开发软件所需要的所有软件内容。
Thus, the SRS should define everything explicitly or (preferably) by reference that software needs to develop the software. References should include the version number of the target document. Also, consider using master document tools which
allow you to include other documents and easily access the full requirements.
这样,SRS应定义所有显示或(可能)参考文献来开发软件所需的软件。参考文献应含有目标文档的版本号。此外,考虑使用文档管理工具,这样可以方便的查看全部需求。
如何编写软件需求规格书(1)
如何编写软件需求规格书(2)
如何编写软件需求规格书(3)
如何编写软件需求规格书(4)
如何编写软件需求规格书(5)
如何编写软件需求规格书(6)
如何编写软件需求规格书(7)
How to write a software requirements specification
如何编写软件需求规格书
by Robert Japenga
__________________________________________________________________________________________
What is the difference between a design requirement and software requirement?
设计需求和软件需求有何区别?
In short, the SRS should not include any design requirements. However, this is a difficult discipline. For example, because of the partitioning and the particular RTOS you are using, and the particular hardware you are using, you may require
that no task use more than 1 ms of processing prior to releasing control back to the RTOS. Although that may be a true requirement and it involves software and should be tested, it is truly a design requirement and should be included in the Software Design
Document or in the Source code.
简单来说,SRS不应该包含设计需求。然而,这个要求做起来比较难。例如,因为你使用了特殊的RTOS[译者注:实时操作系统],使用了特殊的硬件,你可能需要每个任务的调度时间不超过1ms。尽管这是真正的需求,其包括软件,并且应该被从测试,但这真的是一项设计需求,应该包含在软件设计文档中,或者在源代码中。
Consider the target audience for each specification to identify what goes into what documents.
通过考虑每个规格书的阅读对象来识别相应的文档中应该有些什么内容。
Marketing/Product Management
Creates a product specification and gives it to Systems. It should define everything Systems needs to specify the product
市场/产品管理
编写产品规格书,给出系统。应该定义规范产品所需要的所有系统。
Systems
Creates a System Specification and gives it to Systems/Software and Mechanical and Electrical Design.
系统
创建系统规格书,给出系统/软件和机械、电气设计。
Systems/Software
Creates a Software Specification and gives it to Software. It should define everything Software needs to develop the software.
系统/软件
常见软件规格书,给出软件。应定义开发软件所需要的所有软件内容。
Thus, the SRS should define everything explicitly or (preferably) by reference that software needs to develop the software. References should include the version number of the target document. Also, consider using master document tools which
allow you to include other documents and easily access the full requirements.
这样,SRS应定义所有显示或(可能)参考文献来开发软件所需的软件。参考文献应含有目标文档的版本号。此外,考虑使用文档管理工具,这样可以方便的查看全部需求。
如何编写软件需求规格书(1)
如何编写软件需求规格书(2)
如何编写软件需求规格书(3)
如何编写软件需求规格书(4)
如何编写软件需求规格书(5)
如何编写软件需求规格书(6)
如何编写软件需求规格书(7)
相关文章推荐
- 如何编写软件需求规格书(4)
- 如何编写软件需求规格书(3)
- 如何编写软件需求规格书(5)
- 如何编写软件需求规格书(1)
- 如何编写软件需求规格书(7)
- 如何编写软件需求规格书(2)
- 如何编写高质量“软件需求说明书 ”
- 软件需求规格说明书的编写指南
- 如何编写系统需求规格说明书(仅供参考)
- 如何撰写《软件需求规格说明书》
- OO系统分析员之路--用例分析系列(8)--如何编写一份完整的UML需求规格说明书[整理重发]
- 如何提升自己编写软件需求文档能力
- OO系统分析员之路--用例分析系列(8)--如何编写一份完整的UML需求规格说明书[整理重发]
- 软件需求规格说明书编写
- 软件需求分析规格说明书格式
- 如何快速编写一个汇编软件
- 如何编写优质的需求文档
- 软件需求分析规格说明书(转载)
- 需求工程系列(七)- 如何编写用例的前置条件
- 通过学习学生信息管理系统软件,C程序中,如何设计和编写一个应用系统