如何编写软件需求规格书（2）
How to write a software requirements specification
如何编写软件需求规格书
by Robert Japenga
__________________________________________________________________________________________
What are the benefits of a Great SRS?
优秀的SRS能带来什么好处？
The IEEE 830 standard defines the benefits of a good SRS:
IEEE 830标准定义优秀的SRS所带来的好处：
Establish the basis for agreement between the customers and the suppliers on what the software product is to do.The complete description of the functions to be performed by the software specified in the SRS will assist the potential users to determine if the software specified meets their needs or how the software must be modified to meet their needs. [NOTE: We use it as the basis of our contract with our clients all the time].
在客户和供应商之间建立一种对软件产品能提供何种服务的一致性理解。SRS对软件功能所进行的完整的描述，有助于潜在的用户知道该软件是否能够满足其需求，以及如何修改才能满足其需求。[注：我们一直都以SRS作为我们和客户之间的契约]
Reduce the development effort. The preparation of the SRS forces the various concerned groups in the customer抯 organization to consider rigorously all of the requirements before design begins and reduces later redesign, recoding, and retesting. Careful review of the requirements in the SRS can reveal omissions, misunderstandings, and inconsistencies early in the development cycle when these problems are easier to correct.
减少开发工作量。开始进行设计之前，相关的人员在客户公司准备SRS，并考虑各种可能的需求，因此减少了后续的重新设计、重新编码、重新测试等工作。仔细评审SRS中的每项需求，可以在开发周期的早期发现遗漏、误解、不一致，这时更容易更正这些问题。
Provide a basis for estimating costs and schedules. The description of the product to be developed as given in the SRS is a realistic basis for estimating project costs and can be used to obtain approval for bids or price estimates. [NOTE: Again, we use the SRS as the basis for our fixed price estimates]
提供评估成本和时间点的依据。SRS中对要开发的产品的描述是评估项目成本的基础，并且可以用于竞标或价格评估。[注：我们再次使用SRS作为固定价格评估的基础]
Provide a baseline for validation and verification. Organizations can develop their validation and Verification plans much more productively from a good SRS. As a part of the development contract, the SRS provides a baseline against which compliance can be measured. [NOTE: We use the SRS to create the Test Plan].
提供验证和确认基线。优秀的SRS利于制定验证和确认计划。作为开发契约中的一部分，SRS提供了可以度量的基线。[注：我们使用SRS来创建测试计划]
Facilitate transfer. The SRS makes it easier to transfer the software product to new users or new machines. Customers thus find it easier to transfer the software to other parts of their organization, and suppliers find it easier to transfer it to new customers.
利于交付。SRS使得软件产品可以很容易的交付给新用户或新设备。客户可以很容易的将软件交付给公司中的其他部门，供应商也会很容易的将其交付给新客户。
Serve as a basis for enhancement. Because the SRS discusses the product but not the project that developed it, the SRS serves as a basis for later enhancement of the finished product. The SRS may need to be altered, but it does provide a foundation for continued production evaluation. [NOTE: This is often a major pitfall when the SRS is not continually updated with changes]
作为改进的依据。因为SRS关心的是产品本身，而不是开发该产品的项目，所以SRS可以作为产品开发完成之后改进的依据。可能需要对SRS进行修改，但是SRS不是提供后续产品评估的依据。[注：如果SRS不随着后续的改变而进行更新的话，这种做法是错误的]
如何编写软件需求规格书（1）
如何编写软件需求规格书（2）
如何编写软件需求规格书（3）
如何编写软件需求规格书（4）
如何编写软件需求规格书（5）
如何编写软件需求规格书（6）
如何编写软件需求规格书（7）