如何编写软件需求规格书(1)
2011-08-26 12:06
190 查看
原文地址:http://www.microtoolsinc.com/Howsrs.php
How to write a software requirements specification
如何编写软件需求规格书
by Robert Japenga
__________________________________________________________________________________________
What Makes a Great Software Requirements Specification?
什么造就了优秀的软件需求规格书?
There are many good definitions of System and Software Requirements Specifications that will provide us a good basis upon which we can both define a great specification and help us identify deficiencies in our past efforts. There is also a lot
of great stuff on the web about writing good specifications. The problem is not lack of knowledge about how to create a correctly formatted specification or even what should go into the specification. The problem is that we don't follow the definitions out
there.
有许多描述系统和软件需求规格书的定义,这给我们提供了良好的基础。基于此,我们既可以定义一个优秀的规格书,并且有助于我们识别过去的不足之处。同样,网上有很多人写了一些关于如何编写优秀规格书的文章。问题不在于缺乏如何定义规格书的模板和格式,也不在于规格书中应包含哪些内容,而在于我们没有按照本文罗列出的定义来编写规格书。
We have to keep in mind that the goal is not to create great specifications but to create great products and great software. Can you create a great product without a great specification? Absolutely! You can also make your first million through
the lottery but why take your chances? Systems and software these days are so complex that to embark on the design before knowing what you are going to build is foolish and risky.
有一点需要明确一下,我们的目标不是编写优秀的规格书,而是开发出优秀的产品和软件。没有优秀的规格书,是否能够开发出优秀的产品?当然可以!你甚至可以通过买彩票获得你的第一笔百万财富,但是你为何能抓住机会?目前的系统和软件都非常的复杂,在不清楚你将要做什么事情之前就匆匆忙忙进行设计,这是一件愚蠢并且具有风险的行为。
The IEEE (www.ieee.org) is an excellent source for definitions of System and Software Specifications. As designers of real-time, embedded system software, we use IEEE STD 830-1998 as the basis for all of our
Software Specifications unless specifically requested by our clients. Essential to having a great Software Specification is having a great System Specification. The equivalent IEEE standard for that is IEEE STD 1233-1998. However, for most purposes in smaller
systems, the same templates can be used for both.
IEEE(www.ieee.org) 提供了系统和软件规格书相关的一些信息。作为实时嵌入式系统软件的设计者,我们使用 IEEE STD 830-1998作为我们的软件规格书的基础,除非客户提出了特殊的需求。优秀的软件规格书的前提是优秀的系统规格书,相应的标准是IEEE STD 1233-1998。然而,对于小型的系统,系统规格书和软件规格书可以采用相同的模板。
如何编写软件需求规格书(1)
如何编写软件需求规格书(2)
如何编写软件需求规格书(3)
如何编写软件需求规格书(4)
如何编写软件需求规格书(5)
如何编写软件需求规格书(6)
如何编写软件需求规格书(7)
How to write a software requirements specification
如何编写软件需求规格书
by Robert Japenga
__________________________________________________________________________________________
What Makes a Great Software Requirements Specification?
什么造就了优秀的软件需求规格书?
There are many good definitions of System and Software Requirements Specifications that will provide us a good basis upon which we can both define a great specification and help us identify deficiencies in our past efforts. There is also a lot
of great stuff on the web about writing good specifications. The problem is not lack of knowledge about how to create a correctly formatted specification or even what should go into the specification. The problem is that we don't follow the definitions out
there.
有许多描述系统和软件需求规格书的定义,这给我们提供了良好的基础。基于此,我们既可以定义一个优秀的规格书,并且有助于我们识别过去的不足之处。同样,网上有很多人写了一些关于如何编写优秀规格书的文章。问题不在于缺乏如何定义规格书的模板和格式,也不在于规格书中应包含哪些内容,而在于我们没有按照本文罗列出的定义来编写规格书。
We have to keep in mind that the goal is not to create great specifications but to create great products and great software. Can you create a great product without a great specification? Absolutely! You can also make your first million through
the lottery but why take your chances? Systems and software these days are so complex that to embark on the design before knowing what you are going to build is foolish and risky.
有一点需要明确一下,我们的目标不是编写优秀的规格书,而是开发出优秀的产品和软件。没有优秀的规格书,是否能够开发出优秀的产品?当然可以!你甚至可以通过买彩票获得你的第一笔百万财富,但是你为何能抓住机会?目前的系统和软件都非常的复杂,在不清楚你将要做什么事情之前就匆匆忙忙进行设计,这是一件愚蠢并且具有风险的行为。
The IEEE (www.ieee.org) is an excellent source for definitions of System and Software Specifications. As designers of real-time, embedded system software, we use IEEE STD 830-1998 as the basis for all of our
Software Specifications unless specifically requested by our clients. Essential to having a great Software Specification is having a great System Specification. The equivalent IEEE standard for that is IEEE STD 1233-1998. However, for most purposes in smaller
systems, the same templates can be used for both.
IEEE(www.ieee.org) 提供了系统和软件规格书相关的一些信息。作为实时嵌入式系统软件的设计者,我们使用 IEEE STD 830-1998作为我们的软件规格书的基础,除非客户提出了特殊的需求。优秀的软件规格书的前提是优秀的系统规格书,相应的标准是IEEE STD 1233-1998。然而,对于小型的系统,系统规格书和软件规格书可以采用相同的模板。
如何编写软件需求规格书(1)
如何编写软件需求规格书(2)
如何编写软件需求规格书(3)
如何编写软件需求规格书(4)
如何编写软件需求规格书(5)
如何编写软件需求规格书(6)
如何编写软件需求规格书(7)
相关文章推荐
- 如何编写软件需求规格书(4)
- 如何编写软件需求规格书(3)
- 如何编写软件需求规格书(5)
- 如何编写软件需求规格书(6)
- 如何编写软件需求规格书(7)
- 如何编写软件需求规格书(2)
- 如何编写高质量“软件需求说明书 ”
- 软件需求规格说明书的编写指南
- 如何编写系统需求规格说明书(仅供参考)
- 如何撰写《软件需求规格说明书》
- OO系统分析员之路--用例分析系列(8)--如何编写一份完整的UML需求规格说明书[整理重发]
- 如何提升自己编写软件需求文档能力
- OO系统分析员之路--用例分析系列(8)--如何编写一份完整的UML需求规格说明书[整理重发]
- 软件需求规格说明书编写
- 软件需求分析规格说明书(转载)
- 需求工程系列(七)- 如何编写用例的前置条件
- 通过学习学生信息管理系统软件,C程序中,如何设计和编写一个应用系统
- 如何将自己编写的软件放在真机上运行 推荐
- 软件需求分析规格说明书格式
- 让你提前认识软件开发(35):如何修改SQL脚本以完成需求?