How to compile software requirement specifications (2)

Address: http://www.microtoolsinc.com/Howsrs.php

How to Write a software requirements specification

How to compile software requirement specifications

By Robert japenga

__________________________________________________________________________________________

What are the benefits of a great SRS?

What are the benefits of excellent SRS?

The IEEE 830 standard defines the benefits of a good SrS:

Benefits of the IEEE 830 standard definition of good SrS:

Establish the basis for agreement between the MERs and the suppliers on what the software product is to do.The complete description of the functions to be saved med 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].

Establish a consistent understanding of the service that the software product can provide between the customer and the supplier.SRS's complete description of software functions helps potential users know whether the software can meet their needs and how to modify it to meet their needs. [Note: We always use SRS as the contract between us and our customers]

Reduce the development effort.The preparation of the SRS forces the varous concerned groups in the customer organization to consider rigorously all of the requirements before design begins and CES 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.

Reduce development workload.Prior to the design, relevant personnel prepare SRS at the customer's company and consider various possible requirements, thus reducing subsequent re-design, re-coding, re-testing and other work. By carefully reviewing each requirement in SRS, you can discover omissions, misunderstandings, and inconsistencies early in the development cycle, making it easier to correct these problems.

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]

Provides the basis for evaluating costs and time points.The description of the product to be developed in SRS is the basis for evaluating the project cost and can be used for bidding or price evaluation. [Note: We use SRS again as the basis for fixed price evaluation]

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].

Provides verification and validation baselines.Excellent SRS facilitate validation and validation plans. As part of the development contract, SRS provides measurable baselines. [Note: We use SRS to create a test plan]

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
Transfer it to new MERs.

Conducive to delivery. SRS makes it easy for software products to be delivered to new users or devices. Customers can easily deliver software to other departments in the company, and suppliers can easily deliver it to new customers.

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]

As the basis for improvement.Because SRS is concerned with the product itself, rather than the project for developing the product, SRS can be used as the basis for improvement after the product is developed. SRS may need to be modified, but SRS is not the basis for subsequent product evaluation. [Note: This method is incorrect if SRS is not updated with subsequent changes]

How to compile software requirement specifications (1)

How to compile software requirement specifications (2)

How to compile software requirement specifications (3)

How to compile software requirement specifications (4)

How to compile software requirement specifications (5)

How to compile software requirement specifications (6)

How to compile software requirement specifications (7)