Q 2. What is SRS ? Or
Explain SRS document contents in brief.
==>
1) A Software requirements specification (SRS), a requirements specification for a software system, is a description of the behavior of a system to be developed and may include a set of use cases that describe interactions the users will have with the software.
2) To derive the requirements we need to have clear and thorough understanding of the products to be developed or being developed
3) This is achieved and refined with detailed and continuous communications with the project team and customer till the completion of the software.
* The importance of SRS documents are:
1) Establish the basis for agreement:
SRS helps in establishing agreement between the customers and the suppliers on what the software product is to do.
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.
Reduce the development effort.
2) 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.
3) 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.
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.
5) 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.
No comments:
Post a Comment